Import and Export Use Cases

Owned by Megan Forbes
Last updated: Apr 15, 2011 by Chris HoffmanVersion comment
3 min read

The Cleveland Museum of Art

CMS Demonstration Scenarios

7. Delivery Systems

Records should be available for export via email, PDF download, XML, etc. Records should be easily loaded from external systems in MARC, XML, Dublin Core and other formats.

System should have OAI compliant API with the ability to support extracts for federated searching through library systems.

University of California Berkeley

Unknown macro: {multi-excerpt-include}

Custom OAI Data Provision

Several collections at Berkeley provide data to other organizations via custom uses of OAI-PMH.

For example, the History of Art Visual Resources Collection and the College of Environmental Design Visual Resources Collection provide data to ARTstor  via the OAI protocol using a custom web application that supports the ARTstor Core metadata schema. In the current implementation, the provider application dynamically provides data from a custom Sybase database at Berkeley created for this purpose. (That database is populated from the collections' collection management systems using sql queries and stored procedures.)  New data is added to the  database as new images are harvested in the UC Berkeley media vault. The media vault provides the images for harvesting based on URLs stored in the harvested metadata.

The Berkeley Language Center provides data to the Open Language Archives Community (OLAC) as an OAI static repository (XML file) conforming to the OLAC schema. This static repository is created from the Berkeley Language Center's collection management sytem and downloaded to a web server for harvesting.

Research and system integration for biodiversity sciences

  • Data export to other what natural scientists call distributed databases.  Museums routinely ship data in certain formats to data aggregators to help provide data sets that cover larger regions or for the benefit of consortia.  Data formats and methods of accessing data are constantly in flux and vary from domain to domain and provider to provider.
  • Ability to import and host other data sets resulting from research or provided by other scientists.  E.g., the UC and Jepson Herbaria combines their collections data with other herbaria in California to create a searchable state-wide collection set.  This information is not hosted in SMaSCH (used the the UC and Jepson Herbaria) but in a separate set of tables that can be queried via a separate interface.
  • Related to this is the need to allow for metadata synchronization among systems that contain metadata for specific collected objects (e.g., between the collection management system, the digital asset management system, the data broker, GenBank, and so on).  This is a big challenge and is the subject of various major grant proposals.

SMK

We need the ability to export to standard formats (we don't need CS to build the templates).