Summary: | BnF Authorities Z39.50 search and access | ||
---|---|---|---|
Product: | Koha | Reporter: | Oleg Vasylenko <synapse.ova> |
Component: | Z39.50 / SRU / OpenSearch Servers | Assignee: | Galen Charlton <gmcharlt> |
Status: | RESOLVED MOVED | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | claire.hernandez, dcook, fridolin.somers, gaetan.boisson, m.de.rooy |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19436 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Oleg Vasylenko
2017-02-10 15:33:48 UTC
I've been thinking about server profiles, but I don't understand this one. 2016 and 2017 aren't standard bib-1 attributes (http://www.loc.gov/z3950/agency/defns/bib1.html), so I'm guessing BnF have added them, but I don't see how you'd use these attributes in a query... (In reply to David Cook from comment #1) > I've been thinking about server profiles, but I don't understand this one. > 2016 and 2017 aren't standard bib-1 attributes > (http://www.loc.gov/z3950/agency/defns/bib1.html), so I'm guessing BnF have > added them, but I don't see how you'd use these attributes in a query... Indeed. We have looked for the same thing. Non standard attributes means not possible to use in Koha. I say its fair. One can ask the BNF to have a regular export in order to create a mirror. You may use this. Authority servers appear less standardized as bibliographic ones - we have also seen some problems there with our targets. It might be useful if one could configure the attribute mappings for z39.50 targets individually if they are different from default. (In reply to Katrin Fischer from comment #3) > Authority servers appear less standardized as bibliographic ones - we have > also seen some problems there with our targets. It might be useful if one > could configure the attribute mappings for z39.50 targets individually if > they are different from default. Agreed. That's what I was thinking in terms of "server profiles". I think it would be fairly straightforward to implement, but it's not something I'm planning on doing any time soon, although it would be useful for one of our clients as well... This could be solved by BZ 19436, since BNF is now providing authorities through SRU. I am not sure it is worth investing more time in z3950. (In reply to Gaetan Boisson from comment #5) > This could be solved by BZ 19436, since BNF is now providing authorities > through SRU. > > I am not sure it is worth investing more time in z3950. Closing this bug since 19436 (SRU for authorities) is now available and there is also bug 18202 for having configurable profiles. |