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

[Bug 20344] New: Transferring an item while on hold results in a transfer were the destination is the same as the source
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '24

24 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20344 Bug ID: 20344 Summary: Transferring an item while on hold results in a transfer were the destination is the same as the source 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: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com 1. Check out an item 2. Place a hold on the specific item with a pickup at a different branch 3. Check in: Confirm hold and transfert 4. Check the branchtransfers table to ensure that the transfert is here SELECT * FROM branchtransfers order by datesent DESC LIMIT 10; 5. Home › Circulation › Transfers 6. Create a transfer identical as the existing one 7. You should see «Item is already at destination library.» 8. Check the branchtransfers table 1. First one should have been canceled «Canceled, new transfer from A to A created» 2. Another one should have been created from A to A 3. These 2 things are the issue. Because doing the same without a hold - doesn't create a new transfer - doesn't cancel the first one -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 19375] New: Show message when transfer is finished by checking in
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '24

24 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19375 Bug ID: 19375 Summary: Show message when transfer is finished by checking in 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When book is in transfer and is in transfer and is checked in in target library, the transfer is finished by this operation. It would be nice to have some message about that. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 12620] Proxy Add-on for Koha z39.50/SRU servers
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '24

24 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12620 Adolfo Rodríguez Taboada <adolfo.rodriguez(a)xercode.es> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adolfo.rodriguez(a)xercode.es --- Comment #13 from Adolfo Rodríguez Taboada <adolfo.rodriguez(a)xercode.es> --- Created attachment 165452 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=165452&action=e… Allows to search in z39.50 servers using a proxy In some environments it is necessary to use a proxy to search in z39.50 servers wether it's because it doesn't have access to Internet or that the z39.50 ports are blocked. This commit allows to configure a proxy in a new system preference HTTPS_Proxy. Sometimes some of the z39.50 servers don't work with the proxy, so we have added a column at server level so you can specify which ones won't use the proxy. To use the proxy the preference must be configured and the "Do not use proxy" checkbox in the z39.50 must be unchecked. Test plan 1 Check searching agains z39.50 No results. 2 Apply patch, restart services 3 Configure system preference HTTPS_Proxy 4 Check searching agains z39.50 and see that you get results. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 35503] New: Increase 'status' column size in bugslist
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '24

24 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35503 Bug ID: 35503 Summary: Increase 'status' column size in bugslist Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Bugzilla Assignee: jonathan.druart+koha(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com The status column is very narrow and some of our status's start with the same 4 characters which makes it hard to distinguish between them in search results. Could we extend the column width. Reported by Aude and Caroline recently, but also spoken about on IRC a few times -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 31184] New: Add default permissions by patron category
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '24

24 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31184 Bug ID: 31184 Summary: Add default permissions by patron category Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It could be useful to assign default permissions by patron category. (This was pointed out to me by a librarian who had similar functionality in a previous system.) Alternatively, I suppose we could create "permission profiles" and assign those at patron creation time I suppose. The idea being that you set up permissions for certain staff categories (like cataloguing or circulation) and then the staff automatically have their permissions set up and don't require you to manually check all the right checkboxes on a per-user basis. (I suppose role/group-based authorization would cut down even further on having to manually manage so many permissions...although this probably more of a problem for large libraries than small libraries...) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 7003] Canned report to show patrons and permissions
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '24

23 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7003 Andrew Fuerste-Henry <andrewfh(a)dubcolib.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrewfh(a)dubcolib.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7003] Canned report to show patrons and permissions
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '24

23 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7003 Caroline Cyr La Rose <caroline.cyr-la-rose(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=20813 -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 7003] Canned report to show patrons and permissions
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '24

23 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7003 Caroline Cyr La Rose <caroline.cyr-la-rose(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |caroline.cyr-la-rose@inlibr | |o.com --- Comment #5 from Caroline Cyr La Rose <caroline.cyr-la-rose(a)inlibro.com> --- I was just about to write a new bug report about this. I'm looking for all the users in one instance who have a specific permission. Maybe this could be done in conjunction with the revamp of user permissions (bug 20813?), but we need an easier way to see who has which permission than an SQL report like this monster https://wiki.koha-community.org/wiki/SQL_Reports_Patrons#Accounts_with_perm… (kudos to Christopher for figuring all that out!) it's massive! A page in Administration would be great I think. - See all the users who have permissions - See all permissions of a user (could be a link to their "set permissions" page) - See all users who have a particular permission - Seeing this page could be limited by a permission or could be linked to the existing "permissions" permission -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 12141] On Display Module
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '24

23 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12141 Chanel Wheeler <chanel.wheeler(a)yavapaiaz.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chanel.wheeler(a)yavapaiaz.go | |v --- Comment #24 from Chanel Wheeler <chanel.wheeler(a)yavapaiaz.gov> --- As we have both academic libraries and public libraries, we would love for there to be separate course reserve and display modules. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 36670] New: Add a button to intranet detail for a biblio to enable "Reindex this record now"
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '24

23 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36670 Bug ID: 36670 Summary: Add a button to intranet detail for a biblio to enable "Reindex this record now" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 Sometimes there's a reason a record needs to be Reindexed Right Now (es queue is backded up, librarian is impatient, pick something). It would be nice to have a button on the detail page to request an es index "right now" for a single given record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5