Designing a Bit Preservation System
Wallberg, Ben; Knies, Jennie Levine; Hamidzadeh, Babak (2014-06-10)
Tässä tietueessa ei ole tiedostoja, ainoastaan metadata.
Wallberg, Ben
Knies, Jennie Levine
Hamidzadeh, Babak
10.06.2014
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi-fe2014070432322
https://urn.fi/URN:NBN:fi-fe2014070432322
Kuvaus
Poster at Open Repositories 2014, Helsinki, Finland, June 9-13, 2014
Posters, Demos and Developer "How-To's"
Wallberg, Ben (University of Maryland Libraries, USA)
Knies, Jennie Levine (University of Maryland Libraries, USA)
Hamidzadeh, Babak (University of Maryland Libraries, USA)
Posters, Demos and Developer "How-To's"
Wallberg, Ben (University of Maryland Libraries, USA)
Knies, Jennie Levine (University of Maryland Libraries, USA)
Hamidzadeh, Babak (University of Maryland Libraries, USA)
Tiivistelmä
Despite successful operation of DSpace and Fedora repositories, much of the digital preservation work performed at the University of Maryland (UMD) Libraries is focused more on backup and restoration of files than on actual archiving and preservation. The Digital Systems and Stewardship (DSS) division has begun a project to examine gaps, risks, and inefficiencies in the current systems, as well as to build support for new functionalities, such as the curation of active research datasets that are used and can be updated over time. Our first phase of repository development narrows the scope to bit-level preservation and access services. We define bit-level preservation as preservation regardless of the semantics or intellectual content of what is included in a file (content, virus, encryption, intellectual content, etc.), the file format, and how files are semantically interrelated.
During high-level requirements development, it became clear that this bit-level preservation system, rather than representing just a back-end for our existing systems, can provide digital content management services in all phases of content’s lifecycle, including selection, creation, acquisition, and disposition. This paper will discuss the decision to design a bit-level preservation system, our high-level requirements, and our investigation and implementation plans.
During high-level requirements development, it became clear that this bit-level preservation system, rather than representing just a back-end for our existing systems, can provide digital content management services in all phases of content’s lifecycle, including selection, creation, acquisition, and disposition. This paper will discuss the decision to design a bit-level preservation system, our high-level requirements, and our investigation and implementation plans.
Kokoelmat
- Open Repositories 2014 [218]