September 2022 - Koha-bugs - lists.koha-community.org

[Bug 27937] New: Date of birth entered without correct format causes internal server error
by bugzilla-daemon＠bugs.koha-community.org 12 Oct '24

12 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27937 Bug ID: 27937 Summary: Date of birth entered without correct format causes internal server error Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In 20.05 when a birthdate is entered in patron registration form (memberentry.pl) incorrectly, and save button is clicked, you receive an Internal Server Error and all the data is lost. To recreate: 1. Add new patron 2. Enter birthdate as 2/11/1986 3. Complete required fields 4. Save 5. Get ISE Yes, the text below the birthdate does specify MM/DD/YYYY but an incorrect entry should not cause all the data entered to be lost. Perhaps a warning instead that the birthdate format is incorrect? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 31330] New: Branchcode used for routing preview can be wrong
by bugzilla-daemon＠bugs.koha-community.org 11 Oct '24

11 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31330 Bug ID: 31330 Summary: Branchcode used for routing preview can be wrong 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Noticed when working on bug 31318, and discussed on IRC http://irc.koha-community.org/koha/2022-08-09#i_2443598 It seems that we adding/modifying the hold using the holdingbranch of the serial item published first. If no item is created (or no holdingbranch), we are using the subscription.branchcode Shouldn't we use the branchcode of the issue we previously created (if an item exist) instead of the first published one? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 26027] New: Add ability to let librarians know why higher priority holds were skipped
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26027 Bug ID: 26027 Summary: Add ability to let librarians know why higher priority holds were skipped Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com There are circumstances where higher priority holds are not trapped for a given item. These reasons range from requiring specific item or itemtype, to a hold being suspending, to a hold being given local holds priority. I think the best way to accomplish this would be to capture a list of the skipped holds and the reason for skipping them, then pass that to the template for display on the checkin screen when an item is trapped to fill a hold. This feedback would be especially useful if *none* of the holds were trapped for the given item. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 25809] New: Make claims returned claims visible in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25809 Bug ID: 25809 Summary: Make claims returned claims visible in the OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When an item is claimed returned, there isn't any place in the OPAC for the patron to see their claims. Could we add a claims tab to the patron account on the OPAC, mirroring what's on the staff side? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 30463] New: Authority records are indexed on the fly
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30463 Bug ID: 30463 Summary: Authority records are indexed on the fly 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 27344 C4::AuthoritiesMarc::AddAuthority is indexing the record on the fly, we should index in background. 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 6

[Bug 27552] New: Allow batch cleaning & deleting of files in Manage staged MARC records
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27552 Bug ID: 27552 Summary: Allow batch cleaning & deleting of files in Manage staged MARC records Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org In 'Manage staged MARC records' it is a two-step process to remove a .mrc file. It first must be cleaned and then it must be deleted. It would be nice if it was possible to select multiple .mrc files to clean and delete rather than having to perform the two-step process for every single file. We do have a cron job that batch deletes the oldest files on a regular basis. But recently we exported and then re-imported some digital files. The acquisitions staff would rather not all of those .mrc files jumbled in with the .mrc files they are importing for new materials. So it would be helpful to be able to select specific files all at once and get rid of them in a batch. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 25962] New: In Advanced Editor mandatory subfields are not enforced if tag is not mandatory
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25962 Bug ID: 25962 Summary: In Advanced Editor mandatory subfields are not enforced if tag is not mandatory Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: - set your framework so the 100$a is mandatory but the 100 as a whole is not - open a new record in the advanced editor - save the record without a 100$a - edit framework to make the 100 mandatory as well as the 100$a - open a new record - try to save without a 100$a, get an error It doesn't break anything to have to mark the tag required as well as the subfield, but it's more work and it's confusingly different from how we enforce these in the regular editor. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 28805] New: Batch checkout shoudl have on-site checkout option
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '24

09 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28805 Bug ID: 28805 Summary: Batch checkout shoudl have on-site checkout option Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The batch checkout is very useful, but currently doesn't support all advanced options of the normal search page. It's missing the "on-site checkout" functionality. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44

[Bug 30275] New: Checkout renewals should be stored in their own table
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '24

09 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30275 Bug ID: 30275 Summary: Checkout renewals should be stored in their own table 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 Bug 23838 highlighted the need to have a clear distinction between renewals and original issues. I propose the addition of a new table, issue_renewals, to store this data. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 263

[Bug 31002] New: Add ability to send notices over instant messaging services
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '24

09 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31002 Bug ID: 31002 Summary: Add ability to send notices over instant messaging services 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be great to add integration for sending notices via the various instant messaging services people use these days. * WhatsApp * Telegram * Signal * Teams * Slack I think we could work on the core infrastructure on one bug and then enable integrations via drivers or plugins similar to how SMS is dealt with. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8