Summary: | Use 001 (not biblionumber) as record identifier for OAI-PMH | ||
---|---|---|---|
Product: | Koha | Reporter: | Magnus Enger <magnus> |
Component: | Z39.50 / SRU / OpenSearch Servers | Assignee: | Galen Charlton <gmcharlt> |
Status: | CLOSED WONTFIX | QA Contact: | Bugs List <koha-bugs> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | f.demians, jwagner |
Version: | 3.6 | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Magnus Enger
2011-04-16 15:13:03 UTC
I don't think using 001 is necessarily a good idea. For many US libraries using OCLC, the 001 is where the OCLC number lives. That's a sufficiently large number of databases to have to take into account. If your setup will work with the OCLC number, it may not be a problem. But if it has to be a unique number to the system/record, it will be. What about another field? A lot of libraries also use the 035 for either OCLC or system-derived numbers (Unicorn especially), so that's probably not a good one either. In USMARC (not sure about UNIMARC), the biblionumber is being mapped into the 999c in the default biblioitems Koha to MARC mapping. Can this be used or adapted? You don't need to create a new syspref and change Koha code. You need to operate Koha OAI server in 'extended' mode. See the doc or 'perldoc oai.pl'. In extended mode, you have your own XSL to transform your MARC biblio record into any format, and so you can produce a Dublin Core format with what you want in identifier term. OAI-PMH in extended mode can fix this, so I'm marking this as resolved/wontfix. |