January 2025 - Koha-bugs - lists.koha-community.org

[Bug 30979] New: Add ability for opac users to checkout to themselves
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30979 Bug ID: 30979 Summary: Add ability for opac users to checkout to themselves 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org In some trusted environments libraries would like their users to self-issue without having to use the SCO or SIP checkouts. i.e. once logged in a user should have the ability to check out to themselves much like they already have the option to renew and place holds etc. -- You are receiving this mail because: You are watching all bug changes.

1 187

[Bug 33711] New: Refine the token passing mechanisms introduced in bug 23336
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33711 Bug ID: 33711 Summary: Refine the token passing mechanisms introduced in bug 23336 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: koha-bugs(a)lists.koha-community.org, tomascohen(a)gmail.com Depends on: 23336 Bug 23336 introduces an API workflow for checkouts by adding two endpoints.. one for availability that creates a token for confirmations that can then be used by the checkouts endpoint to verify that availability has been checked. Whilst I think the availability endpoint is worthwhile in it's own right, I think we could also send back the token in the 409 pre-condition failed response of the checkouts endpoint so one could use that single endpoint for double duty in the right circumstances. I also think we could work on how the confirmation token is sent to the endpoint.. it's currently a simple query param but may lend itself to being part of the x-koha-overrides header or another header? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23336 [Bug 23336] Add an API endpoint for issuing an item to a patron -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. You are on the CC list for the bug.

1 3

[Bug 33709] New: Add override options to checkouts
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33709 Bug ID: 33709 Summary: Add override options to checkouts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: tomascohen(a)gmail.com Depends on: 23336 I stripped out the local overrides when creating a checkouts POST route.. we should add them back in using the accepted x-koha-overrides method. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23336 [Bug 23336] Add an API endpoint for issuing an item to a patron -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 37590] New: Allow requesting circulation rule sets using wildcards
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37590 Bug ID: 37590 Summary: Allow requesting circulation rule sets using wildcards Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com The API added for fetching circulation rules in bug 36641 allows for limiting which rules you wish to have returned by passing a comma delimited list of rules names in the ?rules= param. We could enhance this to allow for wildcards and open up the opportunity for returning sets of related rules based on a common prefix in the rule name. For example.. `?rules=recalls_*,overdue*` would return all recalls_ and overdue rules without having to specify each of them individually in the query. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 36641] New: Add an endpoint to list circulation rules for an itemtype, branchcode and patron category combination
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36641 Bug ID: 36641 Summary: Add an endpoint to list circulation rules for an itemtype, branchcode and patron category combination Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: tomascohen(a)gmail.com It would be helpful to have an API endpoint that allowed fetching the circulation rules for a given itemtype, branchcode and patron category combination. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 116

[Bug 38040] New: IndependentBranches doesn't prevent editing other libraries' holds
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38040 Bug ID: 38040 Summary: IndependentBranches doesn't prevent editing other libraries' holds Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 When IndependentBranches is set, any staff member from any library can see and edit the holds from patrons from other libraries. 1. Set IndependentBranches, IndependentBranchesPatronModifications, and IndependentBranchesTransfers to 'Yes' 2. Set canreservefromotherbranches to "Don't allow (with independent branches)" 3. Give limited permissions to a staff patron - circulate - catalogue - delete_borrowers - edit_borrowers - list_borrowers - send_messages_to_borrowers - reserveforothers - updatecharges 4. As the superlibrarian, place several holds on a record with items from various branches 5. Log in as the restricted staff 6. View the holds for the record --> Some will say "A patron from library XX" instead of the name -- OK 7. Click the trash bin icon to cancel a hold from another library --> Hold is cancelled -- NOT OK I feel like it should only be superlibrarians who can edit all holds, even those from other libraries. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 72

[Bug 35981] New: Add authorized values for Relator Codes
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35981 Bug ID: 35981 Summary: Add authorized values for Relator Codes Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 34677 updates the relator terms and codes list. There are authorized values for Relator Terms but not for Relator Codes. This should be separated out so that the codes can be selected for $4, which is more correct for that subfield. While it is possible for a user to add authorized values for Relator Codes, it would be nice if they were included. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 38806] New: Dismissing a "Wrong transfer detected" modal leads to transfer not cancelable anymore
by bugzilla-daemon＠bugs.koha-community.org 29 May '25

29 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38806 Bug ID: 38806 Summary: Dismissing a "Wrong transfer detected" modal leads to transfer not cancelable anymore Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com 1. syspref TransfersBlockCirc => don't block 2. Find or create an item that belongs to a branch other than the logged-in branch Like 39999000012118 in test data 3. Check in the item - this should trigger a Return to Home transfer 4. Click OK on the modal to confirm the transfer 5. Check in that item again 6. Click away to dismiss the modal 7. in another tab go see the record page and see that the item is in pending transit 8. back to 1st tab, check in that item again 9. "Please return this item", no cancel button. This isn't right, there was already a transfer. 10. Click ok 11. Check in the item again. 12. Still "Please return this item", no cancel button, item status: "Transit pending" This is even more wrong! It's not possible to cancel anymore. Is step 7 finding the expected status? (Transit pending) Or is that a 3rd problem? Is there a better title for the bug? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 30281] New: Schedule batch patron deletion and anonymization
by bugzilla-daemon＠bugs.koha-community.org 29 May '25

29 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30281 Bug ID: 30281 Summary: Schedule batch patron deletion and anonymization Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Would love to see someone incorporate reoccurring scheduling on this page that didn't require us to setup a cron job on the backend. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 27935] New: Allow item search fields to be defined from database fields rather than MARC tags
by bugzilla-daemon＠bugs.koha-community.org 29 May '25

29 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27935 Bug ID: 27935 Summary: Allow item search fields to be defined from database fields rather than MARC tags Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The item search fields interface allows one to specify MARC tags to be used as custom search fields. It'd be handy to also have the option of specifying database fields, for the various bib/item values that don't get stored in the MARC. This would be handy for folks who don't or can't use reports and therefore rely on item search. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2