https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19893
--- Comment #146 from Alex Arnaud <[email protected]> --- (In reply to David Gustafsson from comment #142) > (In reply to Ere Maijala from comment #130) > > Oh, I see the light now. This is useful also for indexing all subfields > > without having to list all of them. Looks good to me then. We should just > > make sure to document how the rules work. > > Yes, exactly. I was going to make this point but you made it for me :) > Besides being cumbersome it would also make the mappings.yaml quite huge and > difficult to read, and mappings slower to fetch from database. Also, the > mappings are already defined in a way that you need to make minimal changes > with this approach. If joing was the default it would have to be largely > rewritten. Indeed, this is useful for configuring mappings faster. I agree. syntax like 245(ab) seems good and "user friendly" to me. Agree too. But i'm wondering about updates. There's currently some libraries in production with Elasticseach. Will they need to change the rules themselves or will we provide an update script that will change the rules automatically ? -- 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/
