| 1 | = OAI - Open Archives Initiative = |
| 2 | The open archive initiative deals with the dissemination of metadata |
| 3 | and connection of electronic repositories. An institution publishes |
| 4 | its catalogue via OAI-PMH so that others can search it. On the one |
| 5 | hand there are providers who provide the metadata of what they have in |
| 6 | their repository, on the other hand are the harvesters who provide a |
| 7 | search interface to metadata repositories. |
| 8 | |
| 9 | == Providers == |
| 10 | Although you can use several types of metadata, [http://www.openarchives.org/OAI/2.0/guidelines-repository.htm#MinimalImplementation-DC unqualified Dublin Core should be used first]. Moreover, the metadata does not have to be |
| 11 | stored in DC, but could be converted to it upon request by the |
| 12 | harvester. But we consider using DC anyway. |
| 13 | |
| 14 | eSciDoc and formerly eDoc are capable of providing OAI-metadata, how |
| 15 | to enable OAI-PMH for eSciDoc is described on the [https://www.escidoc.org/JSPWiki/en/OaiPmh escidoc-Wiki]. |
| 16 | |
| 17 | The Data Provider is a server that can process the 6 OAI-PMH requests. |
| 18 | PMH means Protocal for Metadata Harvesting. |
| 19 | |
| 20 | == Harvesters == |
| 21 | Harvesters are Service Providers. They can search an OAI-metadata |
| 22 | repository for you. Harvesting is not crawling: the metadata are |
| 23 | retained in their original form, which makes sense. To make oneself |
| 24 | known to harvesters, one should register the repository. |
| 25 | |
| 26 | == Search capabilities == |
| 27 | According to eSciDoc, you have advanced search capabilities via (in |
| 28 | the case of eSciDoc) CQL (Common Query Language): Boolean, String, |
| 29 | Phrase, Fuzzy and Near. |
| 30 | |
| 31 | === Register your repository === |
| 32 | The existence of the repository can be made known by registering the |
| 33 | repository on the [http://www.openarchives.org/data/registerasprovider.html OAI site]. It is required that the repository |
| 34 | conforms to some rules: |
| 35 | |
| 36 | The requests that the repository gives out are to be in XML and they |
| 37 | have to comply to an XML schema. And it is helpful if the metadata |
| 38 | output is in oai_dc, that is, dublin core. |
| 39 | |
| 40 | Every metadata record has to have a unique identifier. It is only |
| 41 | mandatory that the identifier is unique in the repository itself. |
| 42 | However, it is also possible to turn this into an OAI identifier in |
| 43 | the OAI namespace. |
| 44 | == More information == |
| 45 | - [http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm The Open Archives Initiative Protocol for Metadata Harvesting] |
| 46 | - [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines for the Open Archives Initiative Protocol for Metadata Harvesting] |
| 47 | - [http://www.openarchives.org/OAI/2.0/guidelines-repository.htm Guidelines for Repository Implementers] |
| 48 | - [http://www.openarchives.org/pmh/tools/ OAI-PMH Tools] |