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

[Bug 34576] New: wrong information about use of 942 in unimarc
by bugzilla-daemon＠bugs.koha-community.org 03 Aug '24

03 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34576 Bug ID: 34576 Summary: wrong information about use of 942 in unimarc Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In https://koha-community.org/manual/23.05/en/html/cataloging.html#added-entry… it is said that 942$2,$6 and $c is used in UNIMARC installation in the same way as MARC21 It is not the case in my (unimarc) library, and it is not what is written in the wiki https://wiki.koha-community.org/wiki/Holdings_data_fields_(9xx) Is it hardcoded somewhere in Koha ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 36802] New: Add 'status flow' configuration options to catalog concerns
by bugzilla-daemon＠bugs.koha-community.org 02 Aug '24

02 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36802 Bug ID: 36802 Summary: Add 'status flow' configuration options to catalog concerns 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 32435, 35628 Blocks: 34255 With the introduction of catalog concern statuses (bug 35628) and resolutions (bug 32435) we have the foundations for a workflow management solution. I'm envisaging something along similar lines to how Bugzilla manages which statuses are available to pick from at the various stages of the bug workflow. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32435 [Bug 32435] Add resolution types to catalog concerns https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34255 [Bug 34255] Add an enquiry/request/workflow management module https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35628 [Bug 35628] Add additional statuses to catalog concerns -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 32435] New: Add resolution types to catalog concerns
by bugzilla-daemon＠bugs.koha-community.org 02 Aug '24

02 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32435 Bug ID: 32435 Summary: Add resolution types to catalog concerns Change sponsored?: --- Product: Koha Version: master Hardware: All 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 Depends on: 31028 It would be nice to have a descriptive resolution text for different standard resolutions to catalog problems reported via the new catalog concerns feature. We're envisaging using the authorized values system to populate a drop down of resolutions available. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31028 [Bug 31028] Add 'Report a concern' feature for patrons to report concerns about catalog records -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 65

[Bug 36756] New: Fix default action on split update button when editing tickets/catalog concerns
by bugzilla-daemon＠bugs.koha-community.org 02 Aug '24

02 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36756 Bug ID: 36756 Summary: Fix default action on split update button when editing tickets/catalog concerns Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 35657 Just clicking on "update" with ticket resolution status defined does nothing right now, it should update and keep the currently assigned status. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35657 [Bug 35657] Add ability to assign tickets to librarians for catalog concerns -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 15854] New: Possible race condition for sending renewal notices
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15854 Bug ID: 15854 Summary: Possible race condition for sending renewal notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 Renewal notices are sent as digests - all renewed items are collected in one e-mail that is sent out with the process_messagequeue. We have a library, where sometimes this doesn't work. Instead of one single e-mail notice to the patron for one 'process_messagequeue' interval, multiple renewal notices are generated. The majority of e-mails is generated correctly. Looking at the code, this is about how it works: - AddRenewal is exectuted per item and calls - SendCirculationAlert which calls - C4::Message->find_last_message to help decide if a new notice has to be generated or an existing one can be amended In order to test this, you need: - EnhancedMessagingPreferences - Check-out notice checked for the patron you test with - RenewalSendNotice activated - A notice called RENEWAL As I see no problem in the logic so far, I think it could be a race condition where find_last_message doesn't find an existing notice (yet)? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 24007] New: Koha::Account::non_issues_charges is badly named
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24007 Bug ID: 24007 Summary: Koha::Account::non_issues_charges is badly named Change sponsored?: --- Product: Koha Version: master 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The non_issues_charges method name suggests you will be returned a set of charges (Account::Lines) which would block a patrons ability to check out items. In fact, it returns a 'balance' of such charges but includes outstanding credits in the calculation. We should either rename the method to clarify it's use or update the method to return the expectation given it's naming. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 24009] New: Koha::Account->outstanding_debits should support inline filtering
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24009 Bug ID: 24009 Summary: Koha::Account->outstanding_debits should support inline filtering Change sponsored?: --- Product: Koha Version: master 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We have a number of places where we want to get a specific list of outstanding debits for comparison.. at the moment one would have to construct a search directly by inspecting system preferences at the controller level. By addins a filter option to oustanding_debits we can move that back to the object level without having to add additional methods. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 30654] New: Even with RabbitMQ enabled, we should poll the database for jobs at worker startup
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30654 Bug ID: 30654 Summary: Even with RabbitMQ enabled, we should poll the database for jobs at worker startup Change sponsored?: --- Product: Koha Version: master 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 27344 Our worker currently starts up and immediately tries to listen for jobs being passed via STOMP. However, if rabbitMQ wasn't running when the tasks were enqueue, then the worker will never know about them. We should work through the outstanding queue before listening for new jobs. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27344 [Bug 27344] Implement Elastic's update_index_background using Koha::BackgroundJob -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 35299] New: Allow for items with specific not for loan values to appear in the holds queue
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '24

31 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35299 Bug ID: 35299 Summary: Allow for items with specific not for loan values to appear in the holds queue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: clemens.tubach(a)kit.edu, gmcharlt(a)gmail.com, michaela.sieber(a)kit.edu We’d like to be able to specify a list of not for loan values that will be considered eligible to fill holds and appear in the holds queue and ideally the pending holds list as well. These would usually be negative not for loan values, that can be placed on hold. It should be possible to still exempt some status, like -1 = on order. Use Case: In libraries with closed stacks there are often items that are not for loan, but can be requested for use in a reading room. Staff will then get the items and fill the holds, but they won't be checked out on self checks etc. An on-site checkout might be forced. (see Library of Congress: https://ask.loc.gov/law/faq/300644) In order for this process to work the library needs the information about the requested items in order to be able to pull the items in the closed stacks. We have tested a change in Holdsqueue.pm that works, but should be made properly configurable: https://git.koha-community.org/Koha-community/Koha/src/branch/master/C4/Hol… Change: $items_query .= " WHERE items.notforloan = 0 To: $items_query .= " WHERE items.notforloan in (-2, -3, 09) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 36717] New: Merge "Patrons (custom slip)" and "Patrons (custom message)" in Notices
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36717 Bug ID: 36717 Summary: Merge "Patrons (custom slip)" and "Patrons (custom message)" in Notices Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org With the introduction of custom email messages in Bug 29393, we discussed (https://chat.koha-community.org/koha-community/pl/ixoy58im47dhpr4gmwtn9sdbjw) the opportunity to merge the "Patrons (custom slip)" notice type introduced in Bug 32986 and the new "Patrons (custom message)" notice type. The "custom slips" would be notices with the print message transport type, and the "custom messages" (email messages) would be notices with the email message transport type. To get there: 1. Go to Tools > Notices and slips 2. Click New notice --> Notice there is a category "Patrons (custom slip)" and (after bug 29393) "Patrons (custom message)" Create and use a custom slip 3. Click "Patrons (custom slip)" 4. Enter a code and a name (e.g. TESTSLIP, Test slip) 5. Click the "Print" tab 6. Enter content in the "Message subject" and "Message body" fields 7. Click "Save" 8. Go to a patron's account 9. Click "Print" --> There should be an option to "Print test slip" (or whatever name you gave it) Create and use a custom message 10. Go back to Tools > Notices and slips > New notice 11. Click "Patrons (custom message)" 12. Enter a code and a name (e.g. TESTMESSAGE, Test message) 13. Click the "Email" tab 14. Enter content in the "Message subject" and "Message body" fields 15. Click "Save" 16. Go to a patron's account 17. Make sure the patron has an email address 18. Click "Add message" 19. In "Add message for" choose Email --> In "Patron notice" there should be "Test message" (or whatever name you gave it) The proposition was to merge the two notice types and only show the ones with the "Print" message transport type filled in the "Print" menu, and only show the ones with the "Email" message transport type filled in the "Add message" menu. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9