Download (PDF, 9MB, Not barrier-free file.) - Nestor

generating an Archival Information Package (AIP) which complies with the archive's dataformatting and documentation standards, extracting Descriptive Information from the AIPs forinclusion in the archive database, and coordinating updates to Archival Storage and DataManagement. (OAIS 2002, 4-1)Ingest relies upon rules established on the organizational side to determine the metadata thatmust be present, the formats that are acceptable, the means that may be used for transferringobjects, and the quality checks that must be performed […]. The ingest functions must be ableto determine that the files and their metadata are complete and correct as sent. Next themetadata must be generated to tie the objects into the structure of the archive by generating theArchival Information Package (AIP). Any text that will be used for searching or for display mustalso be created and associated with the objects – the Descriptive Information – and sent to DataManagement. After all the complex objects are created, they are moved to Archival Storage. 71During Ingest the repository will typically receive an Information Package from aproducer. 72 It is with Ingest that “the repository takes intellectual control of the [InformationPackage] and processes it for preservation” (Bodleian Library 2007, 55). In the following,the process in which an institutional or subject repository receives a digital object forinclusion in its digital collection will be described as Ingest, despite the fact that therepositories treated here are not the long-term archive. While it would be possible todesignate this process as a kind of pre-Ingest, it will become apparent in the following thatimportant data and information is collected at this stage, without which long-termpreservation would not be possible later, and that hence the repository Ingest can at leastconceptually be regarded as part of the “Ingest proper.”From the point of Ingest onward the repository has the responsibility for the ingestedInformation Package and the preservation of the content information according to thedefined storage or preservation goals. In order to fulfill its tasks, the repository must inparticular have physical and technical control over the digital objects it receives, a fact thatis reflected in all three criteria catalogs (see Appendix A). In particular, this means that theSIP must be free from any Digital Rights Management software or technical measureslimiting, for example, the possibilities to view, save, copy, or print the digital object. Thislatter aspect, which also is highly important in the context of user access to objects storedin a repository, is explicitly mentioned in the explanatory notes to the nestor criterion 9.3 73as well as in the DINI criteria (see DINI 2007, 2.8 74 ). In contrast, TRAC, while stating that71 http://www.icpsr.umich.edu/dpm/dpm-eng/foundation/oais/overview.html – 24.10.200972 However, the Ingest process may also be carried out for an existing AIP which has been changed orupdated in any way. Thus, the OAIS itself might act as producer, for example, when AIPs which underwenta migration are re-submitted to the repository as SIPs. See OAIS 2002, chapter 4.2 for a detailed definitionof its information model, including information packages in chapter 4.2.2.73 Hereafter, the criteria catalogs will be cited as short name (nestor, TRAC, and DINI respectively), year, andnumber of the criterion rather than page number.74 Note, however, that DINI is somewhat unclear in its remarks concerning technical measures for digitalrights management. Thus, the following minimum standard is described under 2.8 Langzeitverfügbarkeit(Long Term Accessibility): “Die gegebenenfalls zusätzlich zu den eingereichten Originaldateien des Autorserstellten Archivkopien sind frei von Schutzmaßnahmen (DRM), die eine Anwendung von Strategien zurLangzeitverfügbarkeit (Migration, Emulation) verhindern” (2007, 2.8; emphasis added). Hence DINI makesa distinction between the submitted files, which are not required to be free from DRM, and archival copies,which can but do not have to be created, and which would have to be free from DRM. Thus the creation ofDRM-free archival copies is currently not a requirement in the DINI criteria, a fact that is, from theperspective of long-term preservation, certainly problematic as a repository that will decide in the future toundertake long-term preservation activities may have a large amount of digital objects unfit forpreservation in its collection. In addition, the following is recommended (i.e. not required): “Nutzung vonoffenen Dateiformaten, die zur Langzeitarchivierung geeignet […] und frei von Schutzmaßnahmen (DRM)sind” (DINI 2007, 2.8). This statement is similarly unclear, in that DRM is something applied to files or26