https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22972
Martin Renvoize (ashimema) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] | |o.uk --- Comment #32 from Martin Renvoize (ashimema) <[email protected]> --- There's also no output from the atomicupdate to say whether the update ran successfully or failed ;) The UNIMARC claim doesn't hold up either. I checked Koha's UNIMARC default frameworks directly: - UNIMARC authority format has no field 024 at all — that tag doesn't exist in authorities_normal_unimarc.yml. The test-plan's own example (024$1) is literally inapplicable to UNIMARC. - UNIMARC bibliographic 700 has no subfield 1 defined in the default framework at all. - Where UNIMARC does define subfield 1 (authority field 160), it means "Linking Data" — part of the 4XX/5XX cross-reference/tracing mechanism — a completely different, incompatible semantic from MARC21's "Real World Object URI". Reusing $1 for a Wikidata link in a UNIMARC record would collide with an already-reserved meaning. - Consistent with that, no UNIMARCslim2intranetDetail.xsl / UNIMARCslim2OPACDetail.xsl changes exist anywhere in this patchset. I think perhaps we should actually make this MARC21 only unless you're aware of people wanting it for UNIMARC and then it should really have it's own path for UNIMARC using the field appropriate for that scheme? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
