2 OverviewWhat is OAI?“The Open Archives Initiative (OAI) represents a "low-barrier interoperability framework" for archives with digital materials. It allows people (Service Providers) to harvest metadata (from Data Providers). This metadata is used to provide "value-added services", often by combining different data sets.“
3 IntroductionThe Information retrieval service definition describes an activity between two applications:1. an initiating application, the client, and a responding application, the server.2. The server/provider is associated with one or more databases.
4 IntroductionCommunication between the client and the server is carried out by OAI standard operators utilizing the http protocol (Web).DigiTool offers both OAI harvesting (client) and OAI provider (server) functionality.
5 DigiTool and OAI GetRecord Retrieves a specified record in a specified format from the Silo.IdentifyRetrieves information about the SiloListIdentifiersRetrieves identifiers of records in the Silo.ListMetadataFormatsRetrieves available metadata formats from the Silo.ListRecordsRetrieves records from the Silo.ListSetsRetrieves the list of sets from the Silo.
6 DigiTool and OAI - provider The OAI provider/server:Allows remote clients to interrogate the DigiTool institution’s database for content:
7 DigiTool and OAI – Provider Configuration$dtle_tab/oai/oaiconf.xml
8 DigiTool and OAI – Supported Support for:sets (collection harvest)oai_dc and marc21deleted records (transient)
9 DigiTool and OAI - Harvesting The OAI client/harvester:Handles the translation between the DigiTool system and OAI servers/providers outside the system.This allows DigiTool staff users to interrogate remote OAI compliant databases and receive content.
10 DigiTool and OAI - Harvesting Meditor service – p-media-25
11 OAI Harvest - Parameters Output File NameInput should be text with no spaces that will become the name of a directory and filewithin the directory to house the queried OAI data.Base URLInput should be the connection URL information that the OAI service provider has madeavailable.For example:Collection NameInput should be the setSpec collection name that the institution has defined (forQuerying Institutions that support sets).For example: tiscDate (From) – Date (To)Input here allows the harvest query to specify a date range to be set when querying theOAI service provider institution. Only records within the date range will be returned tothe harvester.
12 OAI Harvest - Parameters Create Ingest ActivityYes/NoY - The data harvested will automatically be defined for ingest into the repository.N - The harvested data will simply reside in an xml file on the server file system.Assign Ingest ActivityThis input is used in conjunction with Create Ingest Activity – Y.This dropdown menu allows the user running the service to assign a Staff user of hisAdministrative unit who will be responsible for ultimately defining and ingesting theharvested data.PrefixMetadata FormatsDublin Core - oai_dc (http://www.openarchives.org/OAI/2.0/oai_dc/oai_dc.xsd )MARC21 – marc21 (http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd )These are the two metadata formats that are supported for harvest into DigiTool.
13 OAI Harvest – Post Harvest Post OAI HarvestAfter running the OAI harvest service p-media-25, the harvested data should be availablefrom the Administrative unit’s import directory in a directory which was named asOutput file name.This data is normalized from OAI format to standard metadata XML (MARC or DC). If anew ingest activity was set as Y, a new ingest activity will await a staff user from thewebingest module for further definition and ultimate loading into DigiTool.