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

guarantee that documents are “archived” for a specified period of time depending amongothers on the content and technical quality of the digital objects (see DINI 2007, 2.2) andthat documents will be available (as outlined in DINI 2007, 2.5) for at least five years.These requirements therefore merely concern bitstream preservation measures: thedigital objects have to be available for five years, but it is not a requirement that theyremain accessible and interpretable over this period. This limitation to bitstreampreservation is understandable in that repositories seek (and should receive) certificationwhich do not aim at becoming a long term archive. 144 However, the DINI criteria shouldmake an attempt at defining more precisely what is meant by “archiving” (see DINI 2007,2.2 “Archivierungszeiträume”) and by “availability” (see DINI 2007, 2.8“Dokumentverfügbarkeit” and 4.8, which uses both “Langzeitverfügbarkeit” and“Langzeitarchivierung” without explaining the differences between these concepts).In addition to the policies mentioned so far, TRAC requires that the repositoryestablishes a mechanism for update and review of policies in answer to change 145 , as wellas “written policies that specify the nature of any legal permissions required to preservedigital content over time” (TRAC 2007, A3.3). The nestor criteria catalog, on the otherhand, contains an additional criterion that the repository must have specified selectioncriteria for the digital objects it accepts as submissions – an important aspect that is notcovered by TRAC (see, however, DINI 2007, 2.2, which requires that selection/publicationcriteria have to be specified in the repository's policy).As specified in the OAIS model, “[t]he Audit Submission function will verify thatsubmissions (SIP or AIP) meet the specifications of the Submission Agreement [...]. Theaudit process must verify that the quality of the data meets the requirements of the archive[…]” (2002, 4-11-4-12), and therefore complements the Quality Assurance procedurescarried out in the Ingest functional entity. The TRAC catalog in particular specifies theneed for repositories to establish the quality of a digital object submitted to be included inthe repository by evoking the concepts of integrity and authenticity. 146 In contrast, neithernestor nor DINI address this issue as explicitly. As discussed above, the nestor catalogrequires that integrity and authenticity of digital objects are secured at all times fromIngest onwards. This, one can assume, also implies that the completeness andcorrectness of submissions has to be audited – this requirement is, however, not madeexplicit. DINI, on the other hand, contains a criterion demanding that only documents arestored on the server which meet the selection and publication criteria of the repository144 On the other hand, for example in the light of the German Research Foundations recommendation thataccording to good scholarly practice data created and used in research projects should remain availablefor at least ten years, it seems questionable whether a guarantee that digital objects remain available for aminimum of only five years is enough to make these objects usable for scholarly purposes.145 Arguably, the review and update of policies is implied in the nestor requirement to engage in long-termplanning (nestor 2008, 4.4) – however, seeing how important it is to keep policies current and to adaptthem to technological, organizational or other changes, mentioning this point explicitly seems warranted.146 Note, however, that TRAC strictly speaking only requires the quality of the AIP (but not the SIP) to bechecked “at the point it is generated” (2007, B2.11). Although the SIP's completeness and correctness isthe prerequisite for the completeness and correctness of the AIP, this criterion should be modified toinclude SIPs.61