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

[Bug 26354] New: Prevent submission of patron modification request unless changes are actually made
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26354 Bug ID: 26354 Summary: Prevent submission of patron modification request unless changes are actually made Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I think there should be an preference to not be able to submit a request unless information has been changed. We frequently get modification requests with no changes made at all. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 25063] New: OPAC Renewal Option
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25063 Bug ID: 25063 Summary: OPAC Renewal Option Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I am seeing a strange thing with patron modification requests. I see requests come through asking for modification, but nothing has been changed. Looking closer at the accounts, I see that the accounts are up for renewal. I am thinking that people are checking their information and confirming that their information is up to date. I would like to propose two modifications to the modification requests. First, I think there should be an preference to not be able to submit a request unless information has been changed. Second, perhaps a preference tied in with the first suggestion, that allows the patron to select a check-box stating that they have reviewed all their information, and it is accurate and up to date. Perhaps this option only shows when their account is due for renewal. And perhaps the renewal reminder would include a link to the modification page, asking them to review their information and make any any necessary updates if necessary, but acknowledging that the information is up to date. I suggest this being an option, because some libraries might require fees or a view of a current ID before renewing. Third, even if all the patron is doing is renewing, we could have a preference set to notify or not in the modification requests of the acknowledgement and renewal. Fourth, if there are other steps necessary, like a patron category that requires a fee (that isn't automatically charged on renewal) or ID shown, another preference would give admin the ability to have the account self renew. If all they have done is checked the acknowledge box and submitted, the account renews. This option is tricky, since a person could do this, then go back and make changes. But, those changes, would of course, have to be reviewed. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 4373] Placing and processing items simultaneously causes multiple issues
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4373 Liz Rea <wizzyrea(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Liz Rea <wizzyrea(a)gmail.com> --- Haven't heard this in a good long while. Just... going to retire this. :) -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 19716] New: Add option to send header line for CSV output
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19716 Bug ID: 19716 Summary: Add option to send header line for CSV output Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, if outputting a CSV file using runreport.pl, you need to look at the report used to know what each column means. It would be nice if we could include column headers. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 23327] New: Optionally add column headings to emailed reports generated by the runreport.pl cronjob
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23327 Bug ID: 23327 Summary: Optionally add column headings to emailed reports generated by the runreport.pl cronjob Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It might be nice if we could optionally include the column headers on emailed reports using runreport.pl cronjob. maybe something like runreport.pl --with-columnheaders --etcetcetc 123 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 29053] New: ILSDI Internal Server errors seem not to log anywhere?
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29053 Bug ID: 29053 Summary: ILSDI Internal Server errors seem not to log anywhere? Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Had a situation where ILSDI was throwing an internal server error, but none of the logs (plack-intranet-error, plack-error, intranet-error, plack-opac-error, opac-error, or really anywhere in /var/log/koha/instance/) seemed to be logging the errors. I'd be happy to be wrong about this one lol. Liz -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 26927] New: Add the ability to advance search Authorities
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26927 Bug ID: 26927 Summary: Add the ability to advance search Authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently searching is quite limited in search authorities in Koha, it would be nice to have an 'advanced search' to broaden the current search that is available. One specific search would be to the ability to search by Authority number in this module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 34006] New: Keep the current option for budgets in receiving returns an error 500
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34006 Bug ID: 34006 Summary: Keep the current option for budgets in receiving returns an error 500 Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaut.colin(a)univ-rennes2.fr QA Contact: testopia(a)bugs.koha-community.org CC: arthur.suzuki(a)biblibre.com, chughesman(a)cclsny.org, katrin.fischer(a)bsz-bw.de, lucas(a)bywatersolutions.com, nick(a)bywatersolutions.com, wainuiwitikapark(a)catalyst.net.nz Depends on: 31459, 32694 On v22.11.04, the 'Keep current' option brings up the budget_period_id instead of the budget_id. Example: <option value="120" selected="selected" data-sort1-authcat="" data-sort2-authcat="NIV_PUBLIC"> Keep current (Arts 2023)</option> Good line in list: <option value="515" selected="selected" data-sort1-authcat="" data-sort2-authcat="NIV_PUBLIC"> Arts 2023 </option> Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31459 [Bug 31459] Make order receive page faster on systems with many budgets https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32694 [Bug 32694] Keep current option for budgets in receiving broken -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 34096] New: Patron registration fields revert back to last successful save if error occurs
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34096 Bug ID: 34096 Summary: Patron registration fields revert back to last successful save if error occurs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. Create a test patron with category "Teen" and add an address of 1010 Library Lane. Leave date of birth blank. 2. Save record. 3. Edit record to (a) change address to 1010 Book Street and (b) add DOB of 10/10/1980. 4. Save record. 5. Note error message ("The following fields are wrong. Please fix them. Patron's age is incorrect for their category. Ages allowed are 12-18.") and that the address has reverted to 1010 Library Lane. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 33508] New: Submitting patron update request from OPAC deletes any pending updates
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '23

22 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33508 Bug ID: 33508 Summary: Submitting patron update request from OPAC deletes any pending updates Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement 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 When a patron submits a request for update of their personal information, if they submit another request before the first one is approved, the info is deleted. To demonstrate: 1. In OPAC, submit a update changing street address (or any field) 2. View in staff interface and see that the submission shows. Do not take any action on it. 3. Go back to OPAC and submit an update for something else, such as phone number 4. In staff interface, view the new update request and see that only the last one (phone number) shows, the address request has been removed. This is a problem because patrons have no indication that their previous request is being deleted, and staff have no idea that other updates have been requested. For instance, a patron goes into their account and updates address, then realizes they also need to change phone number, and there is no way for them to know they are deleting the previous request. We need to either block patrons from being able to overwrite the previous request, or find a way to retain both requests. I think the second option would be the most customer friendly. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1