http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734
--- Comment #2 from David Cook <[email protected]> --- (In reply to Katrin Fischer from comment #1) > Hi David, > > the publication date range search on the advanced search page I think is > based on 008 Date1 - so using 008 for the facet would make sense to me. Good point. I wonder how we should handle dates like uuuu or 190u or 19uu. Maybe it makes sense just to include definite completely numeric dates? Or maybe do a label for uuuu like "Unknown" and change the u to a question mark for other cases like 190? or 19??, perhaps? I wrote a little TT plugin a while ago to change codes into nice labels for the facets, which I think I mentioned to you, but the problem was that it had hardcoded strings :/. Is there a way of maybe using the "language_descriptions" table to use translated strings? We would run into the same problem with a record type facet. Actually...with record type...we could probably use authorized values like we have for item type and shelving location. I suppose that's not hardcoded but I suppose that probably still presents translation issues. Any ideas? -- 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/
