The Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) is a low-barrier mechanism for developing and promoting interoperability standards that aim to facilitate the efficient dissemination of content across repositories. Data Providers are repositories that expose structured metadata through OAI-PMH. Service Providers then make OAI-PMH service requests to harvest that metadata. OAI-PMH uses six request types (“verbs”) that are invoked within HTTP. Using this functionality, Alma can publish metadata (as a Data Provider) which can then be harvested by external tools/repositories (Data Harvesters).
Configuring an OAI integration profile is the first step toward publishing through OAI. Once you have finished this, you can set up a publishing profile. When that is complete, your OAI setup should be complete and your database ready to load.
This section shows you how to configure an OAI integration profile. This allows Alma to expose the records as OAI types and harvest them accordingly. For information on setting up a publishing OAI profile, see Publishing and Inventory Enrichment.
If your institution already has an OAI integration profile, you cannot add a second one. However, you can edit the existing one.
To set up an OAI integration profile:
- On the Integration Profile List page (Administration > General Configuration > Configuration Menu > General > External Systems > Integration Profiles), click Add Integration Profile. The first step of the two-step integration wizard appears.
- From the Integration Type drop-down menu, select OAI Repository Definition. The page refreshes with relevant fields for the profile.
The Default check box is not functional for this integration type.Refreshed Page One of the Integration Profile for OAI
- Enter an optional Description for the integration profile, and click Next. Step 2 of the integration profile wizard appears.
If you have previously configured an OAI integration profile, you are prompted to edit the existing profile.Integration Profile Wizard Page 2 (Parameters)
- Enter OAI Repository Definitions as required:
- Active / Non Active (required) - Select Active.
- Repository Name - The repository when calling the OAI API.
- Repository Base URL - The fixed, auto-generated base URL for all OAI links, not editable.
- Protocol Version - The protocol version used. The version is automatically entered for this parameter and is not editable.
- Admin Email - The email address where you want communications related to the integration profile to be sent.
- Earliest Datestamp - The first date stamp of the repository records (which can be used, for example, when querying the repository by date).
- Deleted Record - This is automatically identified as transient and is not editable.
- Granularity - The data/timestamp granularity is automatically identified as YYYY-MM-DDThh:mm:ssZ and is not editable. See ISO 8601 for an explanation of this format.
- Metadata Prefixes - Select to enable prefixes. Currently, only MARC 21 is supported.
- Allowed IPs - IP information for users/locations who can access the repository, . For more information, see Mapping Tables. Click Customize when you have finished adding rows. For an IP range, use a hyphen with no spaces (-) between strings. (Syntax corrections will be noted in error messages.)
- OAI Schema - This is identified as oai and is not editable.
- Delimiter - The delimiter is identified as a colon (:) and is not editable.
- Repository Identifier - Enter a string that identifies the repository that is compliant with OAI-PMH requirements. The value should contain two strings with no special characters, separated by a period (for example, 01BC.INST).
- Max bulk size for ListIdentifiers request - A value from 100 to 900 may be specified.
- Max bulk size for ListRecords request - A value from 100 to 900 may be specified.
- Click Save to complete the profile.
Because Alma allows for only one OAI setting, if you want to change anything in the integration profile, you must select Edit from the Actions menu and edit the existing profile.