December 2021 - Koha-bugs - lists.koha-community.org

[Bug 29513] New: Accessibility: Staff Client - Convert remaining breadcrumbs sections from div to nav blocks
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29513 Bug ID: 29513 Summary: Accessibility: Staff Client - Convert remaining breadcrumbs sections from div to nav blocks Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: a.roussos(a)dataly.gr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 27846 and Bug 28101 dealt with making the Staff Client and OPAC breadcrumbs more accessible. It would appear, however, that some Staff Client template files were missed in the process: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/addorderiso2709.tt koha-tmpl/intranet-tmpl/prog/en/modules/admin/transfer_limits.tt koha-tmpl/intranet-tmpl/prog/en/modules/members/merge-patrons.tt -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 29514] New: ILL requests: Remove extraneous &rsaquo; HTML entity from breadcrumbs
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29514 Bug ID: 29514 Summary: ILL requests: Remove extraneous &rsaquo; HTML entity from breadcrumbs Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: a.roussos(a)dataly.gr QA Contact: testopia(a)bugs.koha-community.org Created attachment 127778 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=127778&action=e… ILL requests - extra > after 'Home' breadcrumb As per the attached screenshot, the template file for ILL requests has a small typo: there exists an extra &rsaquo; HTML entity after "Home". -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 14083] Make it possible to record the date the order was placed/sent to the vendor
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14083 Janet McGowan <janet.mcgowan(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |janet.mcgowan(a)ptfs-europe.c | |om -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 29753] New: Quickly Edit an Authority record
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29753 Bug ID: 29753 Summary: Quickly Edit an Authority record Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When editing a bibliographic record, there are several steps you need to perform in the basic editor before editing an authority you may notice is incorrect. 1. perform a search 2. click edit record 3. click the 1 tab 4. click the tab editor for the 100a 5. click search 6. click edit authority It would be great to either have an edit authority option in the results or allow the authority to be edited while editing the record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 29586] New: "Hold reminder" notice doesn't show in messaging preferences in new installation
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29586 Bug ID: 29586 Summary: "Hold reminder" notice doesn't show in messaging preferences in new installation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I am not sure why, but after a reset_all with current master (past 21.11 release), the 'Hold reminder' notice doesn't show in the messaging preferences table and is not in the message_attributes table. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 29748] New: Most Wanted/Lucky Day Items
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29748 Bug ID: 29748 Summary: Most Wanted/Lucky Day Items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some libraries have a Most Wanted or Lucky Day collections. These collections are not holdable and are for patrons physically in the building to discover and checkout. The idea is that patrons that rely more on browsing in the library rather than use the OPAC rarely see popular books that are never on the shelf. Another approach to this might be to have a Most Wanted / Lucky Day setting or status on an individual item, where, if active, would allow holds, but once the item is checked in, it will not trigger a hold for x amount of days. This would allow the item to go back on the shelf or on display for a while before going to the next hold, giving local browsers an opportunity to stumble upon the item. Any thoughts on this idea? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 29455] New: 505$t - change in line break/display
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29455 Bug ID: 29455 Summary: 505$t - change in line break/display Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In 20.05, multiple $t (or $t then $r) entries on the catalog detail page displayed on separate lines within the same 505 tag. On 21.05 they no longer do so - either ' -- ’ has to be added at the end of each $t to force a line break within the same 505, or they need to be separated into multiple 505s. This affects both the staff interface and the OPAC. Bug 19616 indicates that this is a correction rather than a new bug, but it’s an unexpected change in display/behavior nonetheless. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 12709] Send a custom email to some or all patrons
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12709 Ray Delahunty <r.delahunty(a)arts.ac.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |r.delahunty(a)arts.ac.uk --- Comment #5 from Ray Delahunty <r.delahunty(a)arts.ac.uk> --- Isn't this a duplicate of Bug 16149 which added the ability to combine report results with a custom notice to generate emails? I've been testing out the new feature that came in 19.05 but as it doesn't support html in the message we probably wont be able to use it. (Enhancement request being worked on right now.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 28279] New: mappings.yaml no longer in sync
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28279 Bug ID: 28279 Summary: mappings.yaml no longer in sync Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: System Administration Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 19482, 27316, 20589, 25325 We are missing some changes in the mappings.yaml file: * missing staff_client/opac (bug 25325 and bug 20589) * missing mandatory (bug 19482) * sort (bug 27316) became a boolean field Which means export_elasticsearch_mappings.pl generates a file that differs a lot from the one we have in our codebase. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19482 [Bug 19482] Elasticsearch - prevent removal / editing of required indexes https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20589 [Bug 20589] Add field boosting and use elastic query fields parameter instead of deprecated _all https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25325 [Bug 25325] ElasticSearch mapping export lacks staff_client/opac fields https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27316 [Bug 27316] In mappings use yes/no for sortable -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 19482] New: Elasticsearch - prevent removal / editing of required indexes
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19482 Bug ID: 19482 Summary: Elasticsearch - prevent removal / editing of required indexes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Sorting options are currently hardcoded, in view of future z39 support with ES and other interfaces it is probably best to provide a base set of fields that are indexed and sortable. Using the base set of sorting this patchset will prevent editing/removal of these fields by default -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 106