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.
{multi-excerpt-include:deploy:Data export|name=dataexport-ucb|nopanel=true} |
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
We need the ability to export to standard formats (we don't need CS to build the templates).