https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33159
--- Comment #33 from Janusz Kaczmarek <[email protected]> --- (In reply to Nick Clemens from comment #29) > I filed bug 33277 - I think we can require that one before pushing, but > still work on a new bug, expanding the tests and code there, but agreeing on > this base as it solves the problem for some cases. Nick, OK, I understand. But we have still remember about two other classes of problems: 1. 6XX _7 $a NNN $2 <thesaurus_code> but no 040 $f in auth rec. This is common and perfectly legal when is planed to have only one thesaurus in the system - like in data from NLPol, e.g.: http://data.bn.org.pl/api/institutions/authorities.marcxml?id=a0000001003606 -- the auth record is to be used in 6XX (note 008/15='a') with 2nd ind. = 7 (note 008/11 = 'z') and the use example: http://data.bn.org.pl/api/networks/bibs.marcxml?id=b0000003061976: <datafield ind1=" " ind2="7" tag="655"> <subfield code="a">Literatura angielska</subfield> <subfield code="2">DBN</subfield> </datafield> 2. 6XX _4 -- we should look for an auth rec. with 008/11 = '|', non 'n' ('n' means it is not, roughly speaking, 'it is not for 6XX', and more precisely: "is not appropriate for use as a subject added entry in bibliographic records"). You can have a look at the code proposed in Bug 32916 (where all the problems have been solved) and adapt it. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
