July 2024 - Koha-bugs - lists.koha-community.org

[Bug 14907] Item search: Call Numbers in Item search results are ordered alphabetically
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '24

01 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14907 Gretchen Maxeiner <maxeinergl(a)gcc.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maxeinergl(a)gcc.edu --- Comment #8 from Gretchen Maxeiner <maxeinergl(a)gcc.edu> --- We would very much like to see improvement to call number sorting for Library of Congress classification in Item Search. We are new to Koha and working in 24.05, and the sort is alphabetical instead of based on LC filing order. Examples are: D101.2.A8 1951 D1015.B4 1965 D102.D3 1930 and E129.D7 B47 2021 E13.M3 1968 E143.S76 2013 It's a little unclear if this was actually an issue in past releases from the comments above, but I wanted to document that the sort is definitely incorrect in the current release. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 5594] Option to configure default sort order for items on bib records
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '24

01 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5594 Gretchen Maxeiner <maxeinergl(a)gcc.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maxeinergl(a)gcc.edu --- Comment #15 from Gretchen Maxeiner <maxeinergl(a)gcc.edu> --- We too are interested in more logical presentation of multi-volume, multi-copy holdings in the OPAC. Like others who have commented we have large serials and monographic set runs. We are migrating to Koha in a few weeks off a system that allowed item record movement, so staff and patrons are used to items being presented in volume or copy number order. In testing our items did not migrate to Koha in a logical order (we're working on that for the actual migration), and it is an issue that we cannot adjust item order once in Koha. This is also impacting data harvest to our Discovery system. A sort option based on call number (including volumes and copies) would be a useful feature. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug. You are the assignee for the bug.

1 0

[Bug 28823] New: Set LDR position 7 correctly for serial analytics using ''Enhanced Analytics Workflow'
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '24

01 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28823 Bug ID: 28823 Summary: Set LDR position 7 correctly for serial analytics using ''Enhanced Analytics Workflow' Change sponsored?: --- Product: Koha Version: unspecified Hardware: All URL: https://wiki.koha-community.org/wiki/Multipart_Bibliog raphics OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl, testopia(a)bugs.koha-community.org Depends on: 21469 If 'UseControlNumber' is enabled we add a 'Add child record' option from the 'New' menu in bib records. When one clicks this button we are taken to a new bib entry with the 773 pre-populated and a default LDR position 7 of 'a' for 'Monographic component part'. We should not assume we are always adding Monographic analytics, for Serials we should set the indicator to 'b' for 'Serial component part' Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21469 [Bug 21469] Account for 'MarcOrgCode' preference in 'Enhanced Analytics Workflow' -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 18829] New: Elasticsearch - Add ability to view the ES indexed record
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '24

01 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18829 Bug ID: 18829 Summary: Elasticsearch - Add ability to view the ES indexed record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice for the end user (or developer) to have a way to view the record as it exists in the ES index - it will help in adjusting mappings, understanding results, and identifying is a record is not being index -- You are receiving this mail because: You are watching all bug changes.

1 48