OAI in DigiTool DigiTool Version 3.0

Overview What 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.“

Introduction The 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.

Introduction Communication 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.

DigiTool and OAI GetRecord Retrieves a specified record in a specified format from the Silo. Identify Retrieves information about the Silo ListIdentifiers Retrieves identifiers of records in the Silo. ListMetadataFormats Retrieves available metadata formats from the Silo. ListRecords Retrieves records from the Silo. ListSets Retrieves the list of sets from the Silo.

DigiTool and OAI - provider The OAI provider/server: Allows remote clients to interrogate the DigiTool institution’s database for content:

DigiTool and OAI – Provider Configuration $dtle_tab/oai/oaiconf.xml

DigiTool and OAI – Supported Support for: sets (collection harvest) oai_dc and marc21 deleted records (transient)

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.

DigiTool and OAI - Harvesting Meditor service – p-media-25

OAI Harvest - Parameters Output File Name Input should be text with no spaces that will become the name of a directory and file within the directory to house the queried OAI data. Base URL Input should be the connection URL information that the OAI service provider has made available. For example: http://memory.loc.gov/cgi-bin/oai2_0 Collection Name Input should be the setSpec collection name that the institution has defined (for Querying Institutions that support sets). For example: tisc Date (From) – Date (To) Input here allows the harvest query to specify a date range to be set when querying the OAI service provider institution. Only records within the date range will be returned to the harvester.

OAI Harvest - Parameters Create Ingest Activity Yes/No Y - 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 Activity This 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 his Administrative unit who will be responsible for ultimately defining and ingesting the harvested data. Prefix Metadata Formats Dublin 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.

OAI Harvest – Post Harvest Post OAI Harvest After running the OAI harvest service p-media-25, the harvested data should be available from the Administrative unit’s import directory in a directory which was named as Output file name. This data is normalized from OAI format to standard metadata XML (MARC or DC). If a new ingest activity was set as Y, a new ingest activity will await a staff user from the webingest module for further definition and ultimate loading into DigiTool.

Thank you! www.exlibrisgroup.com