OAI-PMH Data Provider Support

There are two entry points: one for bibliographic records and one for authority records:

http://<your-domain>/opac/extras/oai/authority

http://<your-domain>/opac/extras/oai/biblio

An example of a working URL on a system with an authority record with ID 1:

http://<your-domain>/opac/extras/oai/authority?verb=GetRecord&identifier=oai:localhost:1&metadataPrefix=oai_dc

Sets for bib records are currently based on copy visibility, Located URI visibility, or bib source. Generally useful combinations are generated for item, Located URI, and transcendent bib sources.

Sets for authority records are based on the browse axis of the heading for the record.

All generated Sets for bib records currently test for effective search visibility on the three described components.

In order to retrieve item data from a specific branch of the org tree, a harvester must use a Set that contains COPIES:. The hierarchical shortnames of the org units follow the colon, so in a freshly installed system a Set with the setSpec of COPIES:CONS:SYS2:BR3 will retrieve all bib records that have visible copies at BR3, and include only the item data for that org unit.

To retrieve records with Located URIs, which behave in the hierarchical reverse of copies by limiting display to those org units "inside" the branch of the tree where the licensing "lives", a harvester should supply a setSpec with an org unit shortname that would display the Located URI. For example: LURIS:CONS:SYS2:BR3

Note: the LURI: org unit is also used to restrict any item data that may be available for LURI-filtered records.

To retrieve records that are in a transcendent bib source, a harvester can used a setSpec starting with SOURCES: followed by the source name.

To harvest all records, including deleted records, simply omit the setSpec from the request. All item data will be included.

To list available Sets, use the ListSets verb, for instance:

http://your-domain/opac/extras/oai/biblio?verb=ListSets

http://your-domain/opac/extras/oai/authority?verb=ListSets

Certain attributes asset are placed into 852 subfields so:

Thus the Concerto with record ID 1 will have its 852 subfields expressed as:

This mapping can be customized and extended with static subfields:

See comments in opensrf.xml (in the open-ils.supercat app_settings/oai element) for default configuration and customization instructions.

OAI support is not turned on by default. To enable it, edit the Apache configuration file eg_vhost.conf to uncomment the following section and restart Apache: