https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29897 --- Comment #107 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Tomás Cohen Arazi from comment #105)
(In reply to Katrin Fischer from comment #103)
(In reply to Tomás Cohen Arazi from comment #102)
Ok, I like where this is headed to. Questions, are there plans to:
- add valid values dropdowns to the cataloguing interface?
The list of valid MARC codes is very long and the list that will produce a link in the OPAC is still very short. I think we should leave things as is. Adding drop downs is dangerous if you don't know which values have been used already or might be used in incoming records. If the entry is not in the list, the data will be lost. And a full list of valid MARC codes would also be quite long. https://www.loc.gov/standards/sourcelist/standard-identifier.html
We could have an AV category in Koha, with (at least) the supported values. Just thinking how end users will use this.
We could, but we should not link it to the frameworks by default. If you import a record with a value not in the list, on saving the information in $2 will otherwise be lost and leave you with a $a you can't identify.
- add a way to retrieve those identifiers from the configured services?
Can you explain? Do you mean for enriching data?
I think that would not be easily done. If you have common names, the identifiers are added to allow to pick 'the right one'. If you try to match just on the name alone it's too risky.
The whole point in my opinion is to eventually have a '...' link opening a search on the desired identifiers provider (e.g. ORCID) so the link with the ID is automatically generated. JUST A THOUGHT.
We do link now... ? Not sure what the difference would be. Another idea: we could move the include file with the link construction to a YAML style pref. That way people could easily add more and their own. -- You are receiving this mail because: You are watching all bug changes.