Search results

Jump to navigation Jump to search
  • ...containing a set of rules or instructions that tell LOCKSS what content to harvest as well how and where to find it. Defining these rules is a function of the ...specific phrase in order for LOCKSS to accept it a granting permission to harvest
    1 KB (214 words) - 16:59, 15 January 2019
  • ...due to finite space, local staged content should probably be removed after harvest. ...node alleviates the need for additional hardware to stage the content for harvest ([[LOCKSS-in-a-BOX]]).
    759 bytes (114 words) - 10:28, 11 January 2019
  • ...a brief set of instructions that tell the [[LOCKSS daemon]] which files to harvest from the Web server. Here is a copy of Auburn University’s “generic” ...go to the [[AU]]'s [[base URL]], find the [[manifest page|manifest]], and harvest everything found in that folder (including sub-folders). You may be able to
    920 bytes (153 words) - 16:18, 15 January 2019
  • ...aining settings and rules which tell the [[LOCKSS daemon]] how to find and harvest all the content that you have collected into the [[Archival Unit]]. ...containing a set of rules or instructions that tell LOCKSS what content to harvest as well how and where to find it. Defining these rules is a function of the
    1 KB (205 words) - 16:57, 15 January 2019
  • # a permission statement that gives the [[LOCKSS daemon]] the right to harvest a collection of digital objects; and
    583 bytes (88 words) - 16:09, 15 January 2019
  • ...erve as an onramp for [[ADPNet Participant|Participant]] category members (harvest content, procure content, and/or provide assistance with technical issues).
    1 KB (138 words) - 10:04, 11 January 2019
  • ...erve as an onramp for [[ADPNet Participant|Participant]] category members (harvest content, procure content, and/or provide assistance with technical issues).
    2 KB (201 words) - 10:05, 11 January 2019
  • ...P/HTTPS web server to provide [[AU]]s for ADPNet [[preservation node]]s to harvest and preserve.
    2 KB (251 words) - 08:14, 4 March 2021
  • ...the folks at lockss-support@support.lockss.org when you have AUs ready for harvest. Include the following things in the e-mail: the AU title, the AU base URL,
    2 KB (289 words) - 16:15, 15 January 2019
  • ...e available to the public web. ''Staging content'' for ADPNet servers to [[harvest]] is the method by which content is ingested into the digital preservation
    3 KB (426 words) - 10:19, 12 April 2022
  • ...gs: the permission statement that gives the [[LOCKSS daemon]] the right to harvest the collection (at the foot of the document) and the base URL of the [[AU]]
    2 KB (420 words) - 16:30, 15 January 2019
  • ...stributed Archive''': your material is preserved in the network by being [[harvest]]ed, stored, and synchronized within a network of [[preservation node]]s ru
    3 KB (498 words) - 09:47, 10 March 2021
  • ...erve as an onramp for [[ADPNet Participant|Participant]] category members (harvest content, procure content, and/or provide assistance with technical issues).
    4 KB (515 words) - 13:36, 17 September 2021
  • ...chival Unit]], and how to get the [[AU]] staged on the [[drop server]] for harvest and consumption by LOCKSS. ..., and some boilerplate language that gives the LOCKSS daemon permission to harvest content. This is a bit of a pain in the neck and the format is under-docume
    8 KB (1,327 words) - 15:30, 19 May 2022
  • ...secure and convenient location for the ADPNet [[preservation node]]s to [[harvest]] a preservation copy of the content. In ''almost all'' cases, the staging
    4 KB (657 words) - 09:10, 10 March 2021
  • ...things: the permission statement that gives the LOCKSS daemon the right to harvest the collection (at the foot of the document) and the base URL of the AU for
    5 KB (920 words) - 09:38, 12 April 2022
  • and Harvest this means the object must be "swapped in" from disk if
    55 KB (7,553 words) - 10:15, 25 April 2016