https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30327
--- Comment #27 from Johanna Räisä <[email protected]> --- (In reply to Nick Clemens from comment #24) > (In reply to Johanna Räisä from comment #21) > > I tested this and there are some problems. Component parts don't have items > > so sorting with item related fields is quite useless. The items are in the > > host record and component parts are additional information about the host > > record. > > > > Date of publication is problematic also since in most cases component parts > > have the same value. Author and title are quite messy also. The author field > > usually has the same value or is added only to the host record. The > > component parts are wanted to be always in the same order and same order the > > album or note has it. > > > > As Martin mentioned the sorting order could be in 773$g but it is rarely > > used. So if there would be an option to sort by biblionumber it would be the > > most "correct" way to get what catalogers want. > > Hi Johanna, > > We often see analytics for 'bound' volumes of serials, which can have > differing copy dates. We also have libraries with individual articles in > serials cataloged, so the title and author can vary and these values are how > they have requested sorting. > > Biblionumber is a great addition, I simply cannot make it work in zebra > other than the default ascending search. > > I do think we want to handle the sorting in the search engine, rather than > our code, so I have moved the addition of biblionumber sorting to bug 30879. > I think we can move this one forward, and then continue the work there? > > -Nick The new bug is fine for me. -- You are receiving this mail because: 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/
