OAI-PMH marc21 to marc21 crosswalk
Allow for editing of the the marc21_marc21 crosswalk in order to define what fields are presented for harvesting by external agents. This crosswalk is currently hard coded and cannot be edited as you can with the DC crosswalk
-
Amanda Steen commented
Would really like to have our locations harvested via OAI-PMH to the Australian National Bibliographic Database so that ILL requests can go to our branch library instead of the long route. Save time and administration for all in the supply chain.
-
Leigh Duncan commented
Ideally: for our discovery service (EBSCO), we need to be able to point to the following information in the XML: location codes, material types, display/suppression codes. This allows for filtering and identifying catalog data within the discovery service. We would like these fields to be available in the XML.
-
Janet Wilkinson commented
- Sierra gives us the ability to use locally defined MARC fields. It is not appropriate to send these to the Australian National Bibliographic Database as they are only for our internal use. A crosswalk would make excluding these very easy.
- Not having the ability to define what fields are exposed and/or how these are mapped to other fields means that we are relying on a third party to do mapping and data removal for us. A crosswalk would give libraries this control and not require us to take on the risk of a third party managing our data. -
Leigh Duncan commented
Without being able to edit the crosswalk, we cannot use the OAI-PMH feature for our intended purpose of harvesting the catalog for our discovery service.
-
Adam Hornsey commented
This should be standard funtionality. Disappointing to see that this is not the case after years of requesting OAI-PMH functionality in Sierra
-
Janet Wilkinson commented
We would like to have control over which Marc fields can be harvested.