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

[Bug 27652] New: Offer selections for preferences which ask for patron categories
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '24

01 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27652 Bug ID: 27652 Summary: Offer selections for preferences which ask for patron categories Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We have several system preferences where the user is supposed to enter a patron category, but it's a text input. These should offer selections of existing patron categories to prevent data errors. Ideally we'd have two ways to configure the preferences: As a single <select> ("choices" in the pref file) or multiple select ("multiple" in the pref file). PatronSelfRegistrationDefaultCategory - single GoogleOpenIDConnectDefaultCategory - single OPACHoldsIfAvailableAtPickup - multiple BatchCheckouts - multiple -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 35169] New: Make long overdue borrower category options configurable in interface
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '24

01 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35169 Bug ID: 35169 Summary: Make long overdue borrower category options configurable in interface Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Being able to set the borrower category options: 'category=s' => $borrower_category, 'skip-category=s' => $skip_borrower_category Via the staff interface would be really helpful for users being able to update their longoverdue settings without needing to edit the command line. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 50

[Bug 31748] New: Restore progress bar on record import
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '24

01 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31748 Bug ID: 31748 Summary: Restore progress bar on record import 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We've got the progress bar for staging back, we now want it for managing staged records. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 19590] New: doc of Clean Patron Records tool wrong about deletion scope + anonymization syspref
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '24

01 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19590 Bug ID: 19590 Summary: doc of Clean Patron Records tool wrong about deletion scope + anonymization syspref Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hi, I think I've found a documentation issue in the "Clean Patron Records" tool. Both the in-app + online doc [1] mention that: «patrons with outstanding fines or items checked out not saved» (the rest of the doc confirms that we are talking about removal) → wrong, see [2][3] «The anonymization will fail quietly if AnonymousPatron preference does not contain a valid value.» → wrong, according to the UI itself «The AnonymousPatron system preference is not defined. You can use this feature anyway but NULL will be used to update the checkout history.» Are these two findings correct? [1] https://koha-community.org/manual/17.05/html/03_tools.html#patrons-anonymiz… [2] excludes patrons with checked out item https://github.com/Koha-Community/Koha/blob/master/C4/Members.pm#L1040 [3] excludes patrons with unpaid fines https://github.com/Koha-Community/Koha/blob/master/tools/cleanborrowers.pl#… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 37015] New: Expose external_id in the ERM packages form and views
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '24

01 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37015 Bug ID: 37015 Summary: Expose external_id in the ERM packages form and views Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com While the ERM module was in development we had made a case for an external ID field for packages. This was added to the database, but the field cannot be added, edited or viewed from the GUI. We would like to use this to store the national identifiers for packages. They would then be used to match bibliographic records to their packages. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 17330] New: Initiate batch item edit of items from cart (new feature? )
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '24

01 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17330 Bug ID: 17330 Summary: Initiate batch item edit of items from cart (new feature?) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: viktor.sarge(a)regionhalland.se QA Contact: testopia(a)bugs.koha-community.org On 16.05.03 I can initiate batch record edit from the cart, but not items edit. I realize that it's the records that are saved and not items, but /cgi-bin/koha/tools/batchMod.pl already have a checkbox for choosing which items to modify. How about showing all items for all the records chosen and you could just chose which ones to work with? I do feel that there is a possibility of people messing things up from not thinking about the difference between the saved records and the items for that record that might live in different locations. But when someone puked on a whole shelf it's a quick way to search all records on a particular shelf and marking the items as damaged. What say ye? (To be really helpful it would be good if you could check/uncheck all items based on for example location etc. of course) -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 16898] New: Show patron restriction details on OPAC user page
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '24

01 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16898 Bug ID: 16898 Summary: Show patron restriction details on OPAC user page 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Right now if you have multiple restrictions on your account, the details of those restrictions are all string together in the message which displays in the OPAC. We should display details for each separate restriction. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 29554] New: No itemtype for neworderempty.pl
by bugzilla-daemon＠bugs.koha-community.org 30 Sep '24

30 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29554 Bug ID: 29554 Summary: No itemtype for neworderempty.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org neworderempty contains: # Get the item types list, but only if item_level_itype is YES. Otherwise, it will be in the item, no need to display it in the biblio my @itemtypes; @itemtypes = Koha::ItemTypes->search unless C4::Context->preference('item-level_itypes'); I would argue that we should always fetch the itemtypes here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 37717] New: Add ability to batch modify fund used in orders
by bugzilla-daemon＠bugs.koha-community.org 30 Sep '24

30 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37717 Bug ID: 37717 Summary: Add ability to batch modify fund used in orders Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org We need a way to batch modify the fund on existing orders. Our use case is that we have existing orders in our current fiscal year which we know will not fill either due to backorders or because the pub date was pushed into the future. We created a budget for the next fiscal year. So we now have two active budgets and want to start moving orders into the newly created budget so that we can better determine the amount of money we truly have available for the remainder of the current fiscal year. We use a report which includes items that we want to move. It then takes 12 steps to move each order from the current budget into the new budget. This is our process: 1. click on biblionumber for title from report 2. select View record 3. click on the Acquisitions details tab 4. click on the basket name 5. reopen the basket 6. find the order 7. click on the Modify button 8. scroll down the page until you find the fund dropdown 9. click on the fund dropdown 10. select the new fund from the next fiscal year 11. hit the Save button 12. close the basket And then do it all again for the next order. We could probably cut this down by a few steps if we modified our report to include the basket but we would still have to move each order one by one which takes a lot of time. For example this morning, I moved 24 orders to next fiscal year's budget. It took 12 steps to do each one so I performed 288 actions in order to complete this process. A batch operation where the user could select items to be moved into a different budget would be a huge time saver. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 35672] New: Update and Run SQL button should save changes even if report fails to run
by bugzilla-daemon＠bugs.koha-community.org 30 Sep '24

30 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35672 Bug ID: 35672 Summary: Update and Run SQL button should save changes even if report fails to run Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 23824 To recreate: - have a report that works, example "SELECT 1+1" - edit your report to have a SQL error, example "SELECT 1 plus 1" - click Update and Run SQL, get an error message due to SQL error - click to edit report again, confirm none of your changes were saved - re-edit your report to contain the SQL error - click Update, confirm your report saves with an error When using Update and Run, we should save the SQL even if it has an error, just as we do with the old Update button. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23824 [Bug 23824] Add a 'Save and run' button to reports -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9