https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36991
--- Comment #8 from Janusz Kaczmarek <janus...@gmail.com> --- (In reply to Marcel de Rooy from comment #3) > diff --git a/etc/zebradb/ccl.properties b/etc/zebradb/ccl.properties > index 985f7391bc..a71ea8f4c4 100644 > --- a/etc/zebradb/ccl.properties > +++ b/etc/zebradb/ccl.properties > @@ -1039,7 +1039,7 @@ stack 1=8018 > > -Local-classification 1=8022 > +#Local-classification 1=8022 > > What about bib1.att ? > att 20 Local-classification > att 8022 Local-classification > > No blocker This is a good question. The point is that this duplicate in ccl.properties: Local-classification 1=8022 Local-classification 1=20 together with: callnum Local-classification creates problems with scanning. The official id for Local-classification (from LoC) is 20, so I decided to leave 20 and remove 8022. Currently, in Zebra, we index 952 $o with Local-classification index (cf. biblio-zebra-indexdefs.xsl). This means, it is searchable with pqf queries like @attr 1=Local-classification, @attr 1=20 and @attr 1=8022. With the current mapping in ccl.properties search for callnum produces following PQF query (mind "callnum Local-classification" in ccl.properties): @or @attr 1=20 XXX @attr 1=8022 XXX After the removal of 8022 from ccl.properties we get just: @attr 1=20 XXX And this allows for scanning. So, it looks OK, IMO. Or maybe we should remove the 8022 line from bib1? It should not hurt nothing (we do not use 8022 directly). -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org 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/
