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

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