OAIS Usage

This page collects usage and positive comments about OAIS.

    • The OAIS-RM provides the lingua franca –finally we can all talk to one another!
    • The OAIS-RM provides a robust collection of archive functions –great for “gap analysis” and to help us all agree on what an Archive is and does
    • Adoption and conformance to the OAIS-RM is structuring the way the three NOAA Data Centers, other non-NOAA archives, CLASS, the DMC, the DMIT, and the Archive Architecture Team think, talk, and act…

  • Networked European Deposit Library (NEDLIB) - see http://www.dlib.org/dlib/september99/vanderwerf/09vanderwerf.html
  • Royal Library of the Netherlands
    • IBM is developing an ‘OAIS like’ mplementation
  • British National Library
    • Asking IBM to extend its ‘OAIS like’ implementation
  • Research Library Group and OnLine Computer Library Center
    • Developed an OAIS based approach to ‘trusted repositories’
  • Web page to track OAIS implementation efforts/issues
  • Library of Congress
    • Hosting METS XML data packaging approach
  • National Digital Information Infrastructure Preservation Program (NDIIPP)
  • InterPARES
    • Body of National Archives from many countries, adopted OAIS as a starting point for their modeling work
  • France set up a working group within ARISTOTE
    • interested in archive of digital information, including libraries and Dept of Justice.
  • System for Preservation and Access to Data and Information (SIPAD)
    • French space agency plasma physics archive used the OAIS as a basis for design
  • National Space Science Data Center (NSSDC)
    • Evolving our archive using OAIS as a basis for a new architecture
  • National Archives and Records Administration contracted preservation work with San Diego Super Computer Center
    • Both parties claimed use of the OAIS RM saved several weeks of effort in the specification of the task
  • Similar experiences between:
    • National Library of France and French space agency (CNES) representatives
    • National Center for Supercomputer Applications HDF format developers and DNA researchers
    • Life Sciences Archive developer and micro-gravity researchers
    • United States Department of Agriculture and digital preservation experts

The following is from http://www.ukoln.ac.uk/projects/grand-challenge/papers/oaisBriefing.pdf

  • aDORe
    • The aDORe digital repository system was developed by the Research Library of the Los Alamos National Laboratory (LANL) to store local, digital copies of scholarly publications, etc. It uses the MPEG-21 DIDL method of content packaging. LANL’s own implementation of aDORe held about eighty million packages in February 2005 [van de Sompel et al. 2005].
    • The DAITSS digital repository system (http://www.fcla.edu/digitalArchive) was developed by the Florida Center for Library Automation as a generic back-end for digital libraries or institutional repositories. It uses the METS method of content packaging, and uses the PREMIS metadata schema for internal preservation metadata. Its architecture is based on the OAIS ReferenceModel, although the Access functionality is minimal since it is intended to be a ‘dark archive’ [Caplan 2004].
  • DSpace
    • The DSpace digital repository system (http://dspace.org - A list of institutions using the software can be accessed at http://wiki.dspace.org/DspaceInstances) was developed by MIT Libraries and Hewlett-Packard Laboratories, initially to serve as an institutional repository for research output. It uses the METS method of content packaging. DSpace’s use of the OAIS ReferenceModel is patchy but increasing [Bass et al. 2002; Celeste & Branschofsky 2002; DSpace 2005].
  • Fedora
    • The Fedora digital repository system (http://fedora.info) was developed by Cornell University and the University of Virginia, initially to store multimedia digital library collections. It uses the custom Fedora Object XML (FOXML)method for content packaging, although it can ingest and disseminate packages in METS and MPEG-21 DIDL formats. Fedora’s claim to OAIS compliance mainly centres around its ingest and dissemination functions [Fedora Development Team 2005].
  • CDPP
    • The Centre deDonnées de la Physique des Plasmas (CDPP http://cdpp.cesr.fr/english) is a data centre that primarily archives information and data sets from French missions relating to space plasma physics. It has established strict standards for the metadata that producers supply in their SIPs, uses the EAST data description language [CCSDS 2000], and has a functional structure that maps easily onto the OAIS FunctionalModel [ERPANET; Sawyer et al. 2002].
  • MathArc
    • MathArc (http://www.library.cornell.edu/dlit/MathArc) is a collaborative project between Cornell University Library and Göttingen State and University Library to set up a long-term repository of electronic journal articles in the field of mathematics. The repository will be based on the OAIS ReferenceModel, and is investigating the use of the METS method of content packaging coupled with the PREMIS metadata schema.
    • The European Space Agency (ESA) Multi-Mission Facility Infrastructure (MMFI) is a system designed to handle the data from all ESA missions and thereby achieve an economy of scale. It has been designed to map transparently on to the OAIS ReferenceModel, and uses a specialised form of XFDU for content packaging. Its distinctive feature is that it is a distributed system, with only data management and consumer access being centralised [Pinna et al. 2005a;b].
    • The [American]NationalOceanic and Atmospheric Administration (NOAA) Comprehensive Large Array-data Stewardship System (CLASS http://www.class.noaa.gov) is a digital repository of NOAA and US Department of Defense satellite data, and will eventually hold all of NOAA’s datasets. The system itself was designed using the OAIS Reference Model, and the Model also underlies the data submission guidelines and agreements associated with CLASS [Rank &McDonald 2005].
    • The [American] National Space Science Data Center (NSSDC) used the OAIS Reference Model to structure its migration of legacy data sets from old magnetic tape onto digital linear tape (DLT). The legacy tapes (Archival Storage) were read and analysed (Access) to form DIPs; the metadata gleaned from analysis were supplemented by metadata from the NSSDC Information Management System, NIMS (Data Management). These metadata were passed to an Offline Transition to Online (OTTO) database, which informed the conversion of the data into canonical format (Administration), and the packaging of the data and metadata into SIPs. The SIPs were ingested by the Data Ingest and Online Access System (DIOnAS) and converted to AIPs (Archival Storage). The benefit of using the OAIS ReferenceModel was the focus it gave to preservation planning, especially the requirements for adequate metadata, enabling future migrations to be accomplished with greater ease [Sawyer et al. 2005].
    • The Long TermArchiving and Retrieval in the Aerospace Industry (LOTAR) project, (http://www.prostep.org/en/projektgruppen/lotar) undertaken by the ProSTEP iViP Association and AECMA-STAN, is an attempt to specify standards for the long term archiving of (3D) CAD models and PDM documents for Aerospace projects. In particular, the project hopes to specify standards for archiving, methods, scenarios, detailed process descriptions and process modules, suitable data schemata, a system architecture framework, and recommended practices. The LOTAR White Paper [2002] makes extensive use of the OAIS Reference Model. It uses the Functional Model as the foundation for a set of scenarios summarising the requirements for an industrial repository [§7], the OAIS high-level view of external interactions for data exchange guidelines [§8], and the OAIS perspective on digital migration motivators as the basis for a discussion of system architecture [§8.2.2]. When proposing a technical solution [§9], the White Paper uses the EnvironmentModel for recommended roles, the InformationModel for the LOTAR data concept, and the Functional Model for recommended processes; a combination of all three is used for a recommended system architecture. LOTAR will use STEP [ISO 10303] as its recommended platform-neutral archival format, in particular Application Protocol 214 [ISO 10303-214:2003].

-- DavidGiaretta - 27 Nov 2008
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 2009-12-02 - DavidGiaretta
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback