http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14217
--- Comment #8 from Tomás Cohen Arazi <[email protected]> --- (In reply to Marcel de Rooy from comment #6) > This is certainly an interesting development! > > But it might need some further (broader) discussion before getting in. > In the first place: Why do we really need it? Can you elaborate/illustrate? > If we add conditions, what kind of conditions do we want? Syntax? Etc. A > broader design may be easier to maintain.. > How do comparable systems implement this? There are some situations where you need to add conditions as Barton told you. Possible conditions (the ones I had in mind are conditions on the indicator values, as I stated on the commit message). As Barton wrote, if you want to send a field/subfield to a different index depending on the value of the indicators, you can do it with this. If you look at it, we already do it for authority records, but with a more complex syntax. Look at authority-koha-indexdefs.xml: <kohaidx:index_heading_conditional tag="450" test="substring(marc:subfield[@code='w']/text(), 2, 1)" subfields="abvxyz" subdivisions="vxyz"> <kohaidx:target_index>Previous-heading-see-from:p</kohaidx:target_index> </kohaidx:index_heading_conditional> the whole syntax is similar to the one i implement, but you need to add a new tag name if you want conditional indexing, while i just overload the current syntax, which is really convenient. > If we add this for Zebra, what about other search engines? Each search engine provides means to specify what/how to index. I guess stuff like ES are more flexible than Zebra, for sure. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
