http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6590 Magnus Enger <magnus@enger.priv.no> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |In Discussion --- Comment #20 from Magnus Enger <magnus@enger.priv.no> --- (In reply to comment #12)
Alternate implementation idea: use Zebra indexing configs to index both the plaintext ISBN (as it's written in the MARC record) and the normalized ISBN. This way, we don't have to change any of the actual data in the records or how search works; we just add more access points to the data. Less chance of regression this way.
I think if we added isbn.chr file to etc/zebradb/etc, updated default.idx to include it, and modified record.abs to add ISBN and ISSN to those index types, we could pull this off.
This sounds promising, but we need to be careful how we do the normalization. We could extract {0-9xX} from 020$a, but then this would result in an incorrect ISBN being indexed: 020 $a0914378260 (pbk. : v. 1) :$c$5.00 (This example is taken from http://lists.indexdata.dk/pipermail/zebralist/2009-March/002136.html) So we need to do something like extract the first "word" from 020$a, and then extract {0-9xX} from it. Can we do that with a .chr file? Maybe it is easier with DOM indexing, as hinted at here? http://lists.indexdata.dk/pipermail/zebralist/2009-March/002137.html Or could we do some trickery before the indexing? Like add a Koha-specific, hidden subfield to 020 where we store a normalized ISBN when a record is saved/updated? Business::ISBN would be good for doing that, I think. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.