March 2023 - Koha-bugs - lists.koha-community.org

[Bug 32781] New: CreateEHoldingsFromBiblios not dealing with non-existent package correcly
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '23

14 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32781 Bug ID: 32781 Summary: CreateEHoldingsFromBiblios not dealing with non-existent package correcly Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 30943] New: Make background job classes use helpers
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '23

14 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30943 Bug ID: 30943 Summary: Make background job classes use helpers 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 30360 introduced helper methods for dealing with starting, marking as finished and also handling progress. Our tasks should use them. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 42

[Bug 33212] New: Max length should be set to the size of the DB column when mapped
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '23

13 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33212 Bug ID: 33212 Summary: Max length should be set to the size of the DB column when mapped Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If a marc field is mapped to a koha field, such as 952 t, in the framework the max length can be set much higher than the koha field's max length. The max length in the framework should be set to the max length of the Koha field when mapped. Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 33219] New: Course reserves changes item's permanent location if location is CART when item is added to CR
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '23

13 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33219 Bug ID: 33219 Summary: Course reserves changes item's permanent location if location is CART when item is added to CR Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This may be covered by other CR/location bugs, but I'm not sure from reading them. I can copy this elsewhere if it is. If an item has a location of CART when it is added to course reserves, and adding it to CR includes changing its shelving location, its location and permanent location change to the CR location instead of retaining the true permanent location. To replicate, starting with an item with the shelving location JUVENILE: 1. Turn on cart to shelf 2. Check the item out, and then back in. Note that location is CART and permanent_location is JUVENILE. 3. Add the item to a course in course reserves with the shelving location DISPLAY. The location and permanent_location now show as DISPLAY. 4. Remove the item from the course. It has retained DISPLAY as its location and permanent_location. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 24462] New: Adjust K::A::Invoice API mapping to voted RFC
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '23

13 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24462 Bug ID: 24462 Summary: Adjust K::A::Invoice API mapping to voted RFC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com Now it has been voted, it needs to be adjusted. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 30744] New: Non-public note is visible in OPAC in Title Notes tab
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '23

13 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30744 Bug ID: 30744 Summary: Non-public note is visible in OPAC in Title Notes tab Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org To reproduce: 1. Go to Koha Administration -> Koha bibliographic frameworks 2. View the MARC structure for your BKS framework (or something else) 3. Search for tag 583, edit subfields 4. Go to subfield 'x' - nonpublic note. Confirm the OPAC visibility checkbox is UNCHECKED. 5. Edit or create a record using the BKS framework. Put a note in the 583$x. 6. View this record in the OPAC 7. Go to the Title notes tab. Confirm the non-public note is showing, even though the framework says it should not be visible via the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 59

[Bug 33215] New: 'Patron not notified' when checking in a recalled item
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '23

13 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33215 Bug ID: 33215 Summary: 'Patron not notified' when checking in a recalled item Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When a recalled item is checked-in, it always says the 'Patron is not notified', even if there is an email queued in the message_queue or, with bug 23781, the messaging preference is checked. To reproduce: 1. Enable UseRecalls 2. Set up recalls in the circulation rules 3. Check out an item to a patron (patron A) 4. Add an email in the account of another patron (patron B) 5. In the OPAC, log in as a patron (patron B) 6. Place a recall on the item 7. Check in the item --> Notice the pop up says 'Patron is not notified' 8. Click 'Confirm recall' 9. Check the message_queue in the database, or the patron's notifications tab --> The message is queued -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 33213] New: debian package - add fix for node_modules
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '23

13 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33213 Bug ID: 33213 Summary: debian package - add fix for node_modules Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com this patch fixes a bug where debian packages fail to build, as 'node_modules' dir is not handled to test: - build package on master/main branch, note failure - apply patch - build package on master/main branch, note success -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 21009] New: Item URIs longer than 255 bytes are silently truncated
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '23

13 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21009 Bug ID: 21009 Summary: Item URIs longer than 255 bytes are silently truncated Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul(a)flo.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When creating an item in the staff client Koha does not complain if I paste in (or type) a URI that is longer than 255 bytes. When I save the item, the URI is silently truncated to 255 bytes. Here's a sample URI, 500 bytes long, that you can use to reproduce the bug: http://example.com/harumvelitiustovelitofficiaquisnihilconsecteturisteeumau… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 33209] New: There should be a notice for "revert hold waiting status"
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '23

13 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33209 Bug ID: 33209 Summary: There should be a notice for "revert hold waiting status" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Currently, if a hold's waiting status is reverted, customers are not notified. This causes confusion (and often frustration) if they previously received a "hold waiting" notice and come in to pick it up, only to find that the item is not in fact ready for them. We should add an automatic notice template to notify patrons when their hold's waiting status is reverted in order to avoid this confusion and allow customers to avoid making a wasted trip. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1