[Bug 10734] New: Add Publication Date Facet in Searching
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 Bug ID: 10734 Summary: Add Publication Date Facet in Searching Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt@gmail.com Reporter: dcook@prosentient.com.au QA Contact: testopia@bugs.koha-community.org I propose that we add another search facet for publication date. This is fairly common amongst other ILSes and it's been asked for by a few people now. However, I'm not certain about how to proceed. I suppose we could use the 260$c or 264$c...but maybe the 008 dates are the best to use for it. Mind you, Date1 and Date2 can get somewhat complicated depending on the type of date that is encoded... If we are to use controlfields we'll need to refactor how facets are generated...see bug 8026 -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.koha-community. | |org/bugzilla3/show_bug.cgi? | |id=8026 -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- 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. -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 --- Comment #2 from David Cook <dcook@prosentient.com.au> --- (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.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> ---
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 think the second would make a bit more sense to me.
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 :/.
Hm, not sure I remember. If the strings can be in an include or similar, we can translate them.
Is there a way of maybe using the "language_descriptions" table to use translated strings?
I think that would probably be the best option for a language facet.
We would run into the same problem with a record type facet.
I think it is solvable especially when the options and descriptions you want to have are somehow limited by the standard.
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.
I always prefer template translation over using authorised values because the latter are one language only currently. -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 mathieu saby <mathieu.saby@univ-rennes2.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mathieu.saby@univ-rennes2.f | |r --- Comment #4 from mathieu saby <mathieu.saby@univ-rennes2.fr> --- Koha facets are a nightmare. And Marc21 facets are not the same as Unimarc... What we need is either a syspref or a specific page for configuring them (what index, what order for displaying them, etc.), so each library could add or suppress useless/useful facets. I've thought of that for ages, but I will try to code it in the next days. M. Saby -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 --- Comment #5 from mathieu saby <mathieu.saby@univ-rennes2.fr> --- By the way, I think the most usefull missing facets are - date of publication - language of publication M. Saby -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 --- Comment #6 from mathieu saby <mathieu.saby@univ-rennes2.fr> --- I have a plan to improve facets. Could you please take a look and comment the bug if you have any remarks? http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10891 M. Saby -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org