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

More documents

Recommendations

Info

Like pedocs, the repository is not a “standalone” service but is integrated into a(preexisting) network of services and grown structures, including a database containingbibliographic records for publications by researchers employed at the Forschungszentrum(“Veröffentlichungsdatenbank” [VDB]) and a campus press (electronic and printpublications), both hosted at the Central Library. 54In line with the Open Access strategy mentioned above, the primary objective in theimplementation of JUWEL was to make the results of the research carried out at theForschungszentrum openly accessible in full text and thus, although one was aware of theimportance and relevance of digital preservation for JUWEL and its services, questionsand concerns of long-term preservation have not been a priority so far. 55 Thus, although ithas always been attempted to also address requirements of long-term preservation in thedevelopment of the repository's services, no comprehensive policies regarding digitalpreservation have been developed as of yet, nor are long-term preservation strategiesimplemented and applied. Instead it has become clear that most likely a cooperativesolution for long-term preservation will be sought. While this means that actual long-termpreservation measures such as migration or emulation will not be carried out in JUWEL,the repository and its staff will nonetheless have important responsibilities inAdministration, Data Management, and Preservation Planning among others, as it will betheir task to make sure that the long term archive receives digital objects and metadataadequate to long-term preservation.JUWEL currently contains about 3.500 titles and runs on the following system:• LINUX OS• DSpace 1.4.2 56• SQL Server: PostGreSQL 8.07• Webserver Tomcat 5.5.17• Backup: IBM Tivoli Storage Manager (see Hinz 2008)Although the question of long-term preservation capabilities did play a role in selectingDSpace 57 as a software for JUWEL according to Dr. Alexander Wagner, who is part of theteam responsible for managing JUWEL at the FZ's Central Library, this was not theprimary concern at the time the selection was made. Instead, the decision to use DSpacewas on the one hand governed by the fact that it has comparably well-written code and54 http://www.fz-juelich.de/zb/index.php?index=251 and http://www.fz-juelich.de/zb/verlag/ – 01.11.2009.55 JUWEL will, however, serve as a prototype for a (closed access) repository for (historical and partly rare)collections, which will be digitized by the Central Library of the Forschungszentrum for the purpose of longtermpreservation. Hence considerations of how long-term preservation can actually be achieved will gainin importance in the near future.56 The 1.4.2 release of DSpace was thoroughly tested by a National Library of Medicine working group duringthe implementation of plans to establish a digital repository. For these tests, requirements were formulatedon the basis of the OAIS model so that in the documentation of the test results, a matching of DSpacefunctions with OAIS functional entities is available. Based on these tests the use of Fedora as a basis forthe digital repository was recommended. For further information and details, see Marill and Luczak 2009as well as http://www.nlm.nih.gov/digitalrepository/ which contains links to the project documents (NLM2009), including the Policies and Functional Requirements Specification (NLM-DRWG 2008) as well as theRecommendations on NLM Digital Repository Software (NLM-DRESWG 2009), which also contains thetest results for DSpace in Appendix C.57 http://www.dspace.org/ – 03.11.200922
uses technology which the responsible IT-staff considered preferable (e.g. Java andJavaService Pages). On the other hand, the fact that DSpace has a wide internationaluser community, and that hence its ongoing development and support at this point seemfairly certain 58 , played a role in the decision as the availability and further development ofthe software is also an important consideration in the context of long-term preservation.There is, however, also a drawback to using DSpace for a German repository, as currentlyonly very few (if any) German developers contribute to the DSpace source code on aregular basis, which means that certain characteristics and aspects relevant only to theGerman repository landscape, such as the DNB's XMETADISS, are not implemented intoDSpace. 59 Contributions to DSpace source code follow very strict coding anddocumentation standards which are difficult to adhere to if one is not involved in DSpaceprogramming work full time. 60Like pedocs, JUWEL is currently preparing to apply for the DINI 2007 certificate.2.1.3 Qucosa (Quality Content of Saxony)Launched in July 2009, when it replaced a repository which had been in operationsince 1996, Qucosa 61 is a service hosted by the Sächsische Landesbibliothek – StaatsundUniversitätsbibliothek (SLUB) Dresden. It is co-funded by the European RegionalDevelopment Fund (ERDF). Further partners in this project are the academic andresearch libraries in Saxony.According to Dr. Andreas Kluge, head of the information technology department atthe SLUB Dresden and responsible for the management of Qucosa, a concern with issuesand questions of digital long-term preservation has existed at the SLUB Dresden for quitesome time, especially as in addition to Qucosa, the SLUB also operates a digitizationcenter. 62 The latter carries out mass digitization projects, among others, of manuscripts,maps and photographs.This awareness of long-term preservation and its concerns lead, for example, to aclose monitoring of the German kopal project 63 (see below) and to considerations toestablish a cooperative long-term preservation system for Qucosa drawing on servicesdeveloped by kopal. In order to pursue the possibilities offered by kopal further, an58 According to ROAR, on November 1 st , 2009 DSpace had 485 installations worldwide, thus making it therepository software with the biggest user community (see http://roar.eprints.org/).59 As the FZ does not have the right to award doctorate degrees (“Promotionsrecht”), the XMETADISSstandard is not relevant to JUWEL. In addition, German DSpace installations for university-basedrepositories exist, which must therefore have found a workaround for this problem. XMETADISS is,however, not part of the DSpace standard installation.60 See, for example, DSpace's Contribution Guidelines athttp://wiki.dspace.org/index.php/ContributionGuidelines – 31.10.2009. See also Salo (2007), whocomments on available repository software that “[...] the architectures of these software packages aredeeply innovation-unfriendly. DSpace and EPrints are heavily overengineered and written in Java and Perlrespectively, rather than one of the simpler Web-scripting languages such as PHP or Ruby. Even slightmodifications are out of reach of most members of 'the community' due to lack of specialized expertise andsteep learning curves” (no pag.).61 http://www.qucosa.de – 03.11.200962 http://digital.slub-dresden.de/digitalisierungszentrum/ – 03.11.200963 http://kopal.langzeitarchivierung.de/ – 03.11.200923
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 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 and 62: 2.4.2 JUWEL Data ManagementThe stru
Page 63 and 64: Before any SIPs are accepted, the r
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?