https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2646
--- Comment #14 from Jason Robb <[email protected]> --- (In reply to Esther Melander from comment #12) > How would Koha handle a series sort when there is more than one series > statement with different volume numbers? I am thinking of the Magic Tree > House series which was originally published with one series order and then > the publisher re-did the series with a new order. That would mean a title > could conceivably have two series statements and be sorted in two different > ways. This may be an edge example, but I'm sure there are others. It would be neat if you could click on a series facet and it sorts by that. So if your query contains "&limit=title-series:Magic%20Tree%20House" then it sorts the record by the Magic Tree House number, and if your query contains "&limit=title-series:Merlin%20Missions" it sorts the same record by the Merlin Mission number. With Elastic if a record has two 490s, an 800 and an 830 they all get made into individual title-series facets. Maybe the normalized $v from each field could get stored in a pair alongside the series entry so it could be leveraged for sorting by individual series entry? Otherwise it would make sense to prioritize duplicate fields by the order they appear in the record to give the cataloger control. If the "Magic Tree House" 490 comes first it should sort by that, but if you want the "Merlin Missions" 490 to sort first all you should have to do is reorder the two fields in the MARC editor. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug. _______________________________________________ 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/
