Navigation:
Documentation
Archive



Page Tree:

Child pages
  • Preserve materials in a digital storage facility

This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.

Skip to end of metadata
Go to start of metadata

Activity Definition Keywords

Table of contents


go back to Activity Definitions page


Preserve materials in a digital storage facility

Keywords:  Preserve


Activity Definition(s)

Once research or creative materials have been obtained or created, and possibly analyzed and considered, they often need to be preserved for future use by the original scholar/artist or others.  Typically the contents and metadata describing the contents are preserved together.

  • Receive digital object(s) to be preserved
  • Verify file format(s)
  • Receive metadata for each object and the overall package
  • Receive packaging / object relationship map
  • Receive or perhaps assign necessary license(s) to the package
  • Assign unique, possibly permanent identifier(s) to the package
  • Capture accessioning information (date/time, submitter, etc.)
  • Compute any appropriate checksums or other preservation information
  • Store the resultant package in the digital storage facility
  • Return the assigned identifier(s) and other status information
  • Etc. - see the OAIS Reference Model below for details.

For digital materials there are many technical options for storage and preservation.  (Examples include digital content management systems or repositories, relational database systems; Resource Description Framework stores; and distributed, column-oriented stores.)

Scholars' Stories (scenarios)



Tool name

What it does

Relevant links

Fedora Commons

digital repository system

http://www.fedora-commons.org

DSpace

digital repository system

http://www.dspace.org

ePrints

digital repository system

http://www.eprints.org

Nuxeo

digital content management system

http://www.nuxeo.org

(various)

relational database management system

http://en.wikipedia.org/wiki/Relational_database

 

Resource Description Framework store

http://www.w3.org/RDF/

Hadoop

distributed, column-oriented store

http://hadoop.apache.org

Omeka

lightweight digital collection management system

http://omeka.org/

ContentDM

digital collection management system

http://www.contentdm.com/

Greenstone

digital collection management system

http://www.greenstone.org/

DROID

Digital Record Object Identification

http://droid.sourceforge.net/wiki/index.php/Introduction

Pronom

File format registry for digital content review

http://www.nationalarchives.gov.uk/pronom/


Related Collections/Content (examples)

----Optional: examples of collections / digital content / digital resources that could be involved in part or all of the defined activity, with links to relevant repository or site where available

Collection/content name

Collection/content description

Relevant links

 

 

 

 

 

 

 

 

 

 

 

 


Applicable Standards or Standards Bodies


Standard name / body

What it governs/regulates/standardizes - What it's for

Relevant links

OAIS Reference Model

Specifies a set of functions needed for a digital repository

http://public.ccsds.org/publications/archive/650x0b1.pdf

PREMIS (PREservation Metadata Implementation Strategies)

Metadata standard for encoding preservation Information

http://www.loc.gov/standards/premis/

OAI-ORE

How to package/express the contents of compound information objects

http://www.openarchives.org/ore/

 

 

 

SWORD

A lightweight protocol for deposit into a repository

http://www.ukoln.ac.uk/repositories/digirep/index/SWORD

Dublin Core

commonly-used metadata standard for digital collections

http://www.dublincore.org/


Notes, comments, related activities, concerns

This replaces these four original Activity Names:

  • "Preserve materials in a digital content management system such as Fedora Commons or Nuxeo"
  • "Preserve materials in a relational database" 
  • "Preserve materials in an RDF store"
  • "Preserve materials in a distributed, column-oriented store (e.g., Hadoop)."


All "Theme Group: Preserve" activities share these qualities:

  • Address sustainability issues inherent in any preservation endeavor
  • Address the tension between reasonably sustainable storage resources and the desires of some/many to 'preserve everything'
  • Address copyright constraints
  • Address versioning (preserve versions of an artifact when appropriate)
  • Address methods for determining when a set of preserved materials should be deaccessioned
  • Provide for notification of appropriate, interested individuals and communities when a digital collection's sustainability or accessibility is threatened
  • Preserve materials in conformity with broadly accepted standards, such as ISO's OAIS (Open Archive Information System) standard
  • Preserve materials in such a way that they can be found when needed (cf. "Discover" and "Annotate" theme groups)
  • Preserve materials such that appropriate access controls are in-place
  • Preserve context, accommodating ambiguous (fuzzy) context
  • Avoid needless duplication of digital resources when preserving materials
  • Migrate digital materials from deprecated (or soon-to-be-deprecated) to supported formats, for which tools and practices will continue to exist that render the digital record for human comprehension
  • Migrate digital materials from deprecated (or soon-to-be-deprecated) to supported storage technologies (e.g., repositories, databases)


go back to Activity Definitions page

1 Comment

  1. Unknown User (pearce.judith@gmail.com)

    Hi Jim, I agree with treating the four original activities as a single activity. One could see this activity as just involving the act of deposit of archive copies of created or obtained or analysed or considered materials in a trusted repository;with an acknowledgement of receipt and return of an appropriate persistent identifier for future reference; or it could involve all the activities needed by the client application to package up the content and metadata for submission; and by the repository to process, acquit and ingest it on receipt. In practice, the deposit service does seem to be a single technical interface involving a Submisison Information Package and a deposit protocol like OAI-ORE or Sword; but it needs to be supported by a range of other technical services at either end.