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

More documents

Recommendations

Info

although these features have not yet been implemented, in the future DSpace might beable to provide information package descriptions.In the NLM's test results for the DSpace software it is recorded that “[d]ata integritychecks (checksum) [are carried out] for data transfer but not for version upgrades andformat migration (7.4.4.). Also no referential integrity checks (7.3.1.2)” (NLM-DRESWG2009, Appendix C, P2-2; emphasis added). This suggests that DSpace does not meetTRAC criteria B5.3 and B5.4.2.4.3 Qucosa Data ManagementSimilarly as the other repositories, Qucosa primarily maintains referential integrity bymeans of its technical architecture and, more specifically, the relational database. Asoutlined above, once koLibRI is implemented, it will create information packages all ofwhose elements are included in one container for submission to the long term archive.This, however, will not affect how information is stored in Qucosa.Additionally, one of the TU Dresden institutes submitting publications to Qucosa hasimplemented a routine similar to the one now used in pedocs, in the course of which theURNs assigned to the publications by Qucosa are included in the PDF files so that here,too, metadata and content object are permanently linked as the URN will always direct theuser who downloaded or printed a publication to the metadata record associated with it inQucosa (see, for example, http://nbn-resolving.de/urn:nbn:de:bsz:14-ds-1234432867166-41007 – 01.11.2009).2.5 AdministrationThis entity provides the services and functions for the overall operation of the archive system.Administration functions include soliciting and negotiating submission agreements withProducers, auditing submissions to ensure that they meet archive standards, and maintainingconfiguration management of system hardware and software. It also provides systemengineering functions to monitor and improve archive operations, and to inventory, report on,and migrate/update the contents of the archive. It is also responsible for establishing andmaintaining archive standards and policies, providing customer support, and activating storedrequests. (OAIS 2002, 4-2)In the Administration functional entity, “the organizational infrastructure meets thetechnological infrastructure,” 141 and while all functional entities of the OAIS model play acrucial role in the long-term preservation of an archive's holdings, it seems justified todescribe Administration as the entity at the core of these efforts in that among others itcoordinates the overall activity of the archive, negotiates submission agreements,develops strategies and policies, and initiates migration processes (Archival InformationUpdate function).141 http://www.icpsr.umich.edu/dpm/dpm-eng/foundation/oais/administration.html – 25.10.2009.58
Before any SIPs are accepted, the repository needs to negotiate and concludeagreements with the producers submitting their material for inclusion in the repository. Allthree criteria catalogs considered here contain criteria making the existence of a contractor agreement between producer and archive a requirement. Thus, according to therelevant nestor criterion, among others “the character and extent of the submission, thedigital repository's obligation to archive the submitted object, conditions of use, and – ifapplicable – cost” (2008, 3.1; my translation) have to be regulated in an agreement. Inaddition, the commentary to TRAC criterion A5.2 mentions the repository's “need to beable to work with and potentially modify digital objects to keep them accessible.” The DINIcatalog of criteria contains an extensive set of requirements and recommendationsconcerning legal (copyright) aspects of depositing material (especially if previouslypublished) in the repository. But while its treatment of copyright questions in connectionwith self-archiving or open access publishing via the repository is quite elaborate, thecatalog does not contain a criterion making it a requirement that the repository obtain allnecessary rights to carry out long-term preservation actions (regardless of whether thearchived document was previously published elsewhere or not). On the one hand thisreflects DINI's focus on all kinds of (open access) repositories, regardless of whether ornot they are concerned with questions of long-term preservation. It seems, however, thatthe inclusion of such a requirement would help repositories to prepare their collections forpotential long-term preservation measures at a later point so that the option to beginoffering long-term preservation services is not precluded from the outset merely becausethe repository has insufficient rights.The Archival Information Update function, which “provides a mechanism for updatingthe contents of the archive” (OAIS 2002, 4-11), is addressed by TRAC and the nestorcriteria catalog, both of which require the implementation of preservation strategies andpoint to migration and emulation as possibilities. As none of the repositories currently haslong-term preservation strategies implemented and will relegate related activities to along-term preservation service provider, this function will not be treated in the following.The aspect of Physical Access Control, an OAIS function “which providesmechanisms to restrict or allow physical access (doors, locks, guards) to elements of thearchive, as determined by archive policy” (OAIS 2002, 4-11) is covered by nestor and DINI(see nestor 2008, 6.2 and DINI 2007, 2.5.1), but not considered by TRAC. All of therepositories considered here have established sufficient barriers limiting physical accessto their servers; hence this function, too, will not be discussed again in the following.A central task of the Administration functional entity is the establishing of standardsand policies, and it is here (as well as in the Preservation Planning entity treated below)that a considerable gap between “traditional” repository tasks and long-term preservationrelatedrequirements becomes apparent. According to OAIS, the standards to beestablished in the Administration functional entity “include format standards,59
Page 6:
AbstractTaking its cue from the inc
Page 13: and benefit from the development an
Page 18 and 19: German repositories have already be
Page 20 and 21: [t]he Open Archival Information Sys
Page 22 and 23: Thus it seems highly recommendable
Page 24 and 25: actively pursuing the long-term pre
Page 26 and 27: Like pedocs, the repository is not
Page 28 and 29: application for a project grant was
Page 30 and 31: generating an Archival Information
Page 32 and 33: Integrity can be defined as “comp
Page 34 and 35: It is with this step that the metad
Page 36 and 37: documents submitted to the reposito
Page 38 and 39: [t]he majority of OCR software supp
Page 40 and 41: One of the shortcomings of the soft
Page 42 and 43: set of shared metadata which is the
Page 44 and 45: document, and that hence the docume
Page 46: Structural metadata: In DSpace it i
Page 49 and 50: dc.description.provenancedc.descrip
Page 51 and 52: Für die Langzeitverfügbarkeit der
Page 53 and 54: ecord for a title; although a workf
Page 55 and 56: Source (where applicable)Publicatio
Page 57 and 58: checksums. In particular, TRAC requ
Page 59 and 60: checksums are currently not checked
Page 61: 2.4.2 JUWEL Data ManagementThe stru
Page 65 and 66: guarantee that documents are “arc
Page 67 and 68: pedocs is a scholarly open access d
Page 69 and 70: formats. 151 Although the possible
Page 71 and 72: While the preferred file format is
Page 73 and 74: from nestor criterion 8, making it
Page 75 and 76: preserved for the long term, will h
Page 77 and 78: It seems that of all three reposito
Page 79 and 80: associated with them, or has define
Page 81 and 82: versioning functionality which allo
Page 83 and 84: communication channels, responsibil
Page 85 and 86: Works CitedAllinson, Julie (2006):
Page 87 and 88: DSpace Homepage. http://www.dspace.
Page 89 and 90: Lynch, Clifford A. (2000): Authenti
Page 91 and 92: in the EU. Amsterdam: Amsterdam Uni
Page 93 and 94: Ingestnestor TRAC DINIReceive Submi
Page 95 and 96: Archival Storagenestor TRAC DINIRec
Page 97 and 98: Archival Information Update10.4 Das
Page 99 and 100: Preservation PlanningnestorMonitor
show all

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

Create successful ePaper yourself

Delete template?

Save as template?