https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41668
David Cook <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |In Discussion --- Comment #6 from David Cook <[email protected]> --- What should we do here? Option 1: - Change mappings.yaml to set facet: 0 for publisher, local-classification, copydate - This will mean that mappings.yaml and the UI are more in sync. That is, people won't look at mappings.yaml and wonder why the UI says "facetable: no" when the YAML says "facet: 1". That said, they could do that to their custom YAML and be confused still. Option 2a: - Change mappings.pl to show facet: 1 for fields like publisher, local-classification, copydate even though they don't have facet_order set. - This will mean these fields are indexed into "*__facet" fields even though those facets won't be shown. That seems suboptimal Option 2b: - Do option 2a PLUS update the indexing so that "*__facet" fields are only created if there is a facet_order for that facet, so we don't create indexes that aren't used Option 3: - Something else I haven't thought of? -- You are receiving this mail because: You are the assignee for the bug. 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/
