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

[Bug 23305] New: Add ability to append to item notes in batch item modification
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '24

08 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23305 Bug ID: 23305 Summary: Add ability to append to item notes in batch item modification Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It'd be useful to be able to append new text onto the end of itemnotes and itemnotes_nonpublic when performing a batch item modification, rather than simply overwriting any existing notes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 28757] New: Allow users to place a reservation when their account is restricted
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '24

08 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28757 Bug ID: 28757 Summary: Allow users to place a reservation when their account is restricted Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: s.graham4(a)herts.ac.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Could a new syspref be added to Koha that would allow a user to place a reservation/hold if the user is restricted? We have a lot of students who on placement, and only come on-campus occasionally.They tend to return and collect books at the same time during their visits to campus. If they have a restriction on their account (because they need to return an overdue item) then this stops them from requesting a hold at the same time, and forces them to come on-campus twice (once to return the book, and then next time to collect their reservations) when ideally it could be done with one visit. Stephen -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 29697] New: Excessive use of StripNonXmlChars
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '24

08 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29697 Bug ID: 29697 Summary: Excessive use of StripNonXmlChars Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We are using C4::Charset::StripNonXmlChars from different places of the code to remove characters that should not be part of the MARC::XML Historically we were removing them every time we were fetching the record. However, since we are starting to use Koha::Biblio::Metadata ($biblio->metadata->record) to retrieve the xml stored in the biblio_metadata table, such characters will not be removed and a degraded view will be displayed on the bibliographic detail page (see bug 23846). We didn't get a lot of complains, and it's part of Koha since 19.05.05. Shouldn't we start to use $biblio->metadata->record where GetMarcBiblio is actually used? Either we assume the MARC::XML that is stored is correct, or we need to add more StripNonXmlChars calls. -- You are receiving this mail because: You are watching all bug changes.

1 171

[Bug 16264] New: Confirm message on deleting an authority framework subfield
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '24

08 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16264 Bug ID: 16264 Summary: Confirm message on deleting an authority framework subfield Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt(a)gmail.com Reporter: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org Just using this as an example because it appears in many places on the intranet Is there a reason that we navigate to a new page to confirm or cancel a delete rather than just using a Javascript confirm message? A JS message would use much less code. I realise that in the past we had a rule that everything had to work without JS enabled but a lot of stuff on the intranet wouldn't work at all without JS so I'm not sure how much that applies anymore. Anyway, just wondering if these extra pages for confirm or cancelling a delete are still necessary or if we can do this via JS now :) -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 30194] New: Adapt Koha for JSON::Validator@5.x
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30194 Bug ID: 30194 Summary: Adapt Koha for JSON::Validator@5.x 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: tomascohen(a)gmail.com CC: tomascohen(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 146

[Bug 30462] New: Should the background job list view hide index tasks by default?
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30462 Bug ID: 30462 Summary: Should the background job list view hide index tasks by default? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 27344 We will certainly end up with lot of indexation tasks. Shouldn't we hide them by default when we list the tasks on Home > Administration > Background jobs ? 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 56

[Bug 27632] New: Add a more easily javascript accessible biblionumber to each record in OPAC results
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27632 Bug ID: 27632 Summary: Add a more easily javascript accessible biblionumber to each record in OPAC results 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be handy to have an easily accessible biblionumber for each record in the OPAC results. I think .bibliocol would be an appropriate place -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 29616] New: Replace library information popup in the OPAC with a modal
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29616 Bug ID: 29616 Summary: Replace library information popup in the OPAC with a modal Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED 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 Created attachment 128138 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=128138&action=e… Screenshot showing the modal information window If you have "OPAC info" for any of your libraries this information will show up as a popup when the user, viewing the bibliographic detail page, hovers over the library name in the holdings table. I think it would be more user-friendly to have the user click to show this information in a modal dialog. -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 29058] New: Add option to not load existing holds table automatically
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29058 Bug ID: 29058 Summary: Add option to not load existing holds table automatically Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In large consortia the holds table can take a long time to load on records with many holds. When attempting to place a hold this table is always loaded We should provide an option to prevent automatic loading of the table -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 21366] New: add plack reload
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21366 Bug ID: 21366 Summary: add plack reload Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Starman daemon as an option to ask for "reload" meaning the renew of all workers, like Apache graceful restart. Starman restart will kill at once the master process and workers. Starman reload will not impact the master process, it will kill and recreate idle workers, it will wait for busy workers to end before renew them. It is a nice way to refresh the plack middleware without impacting any running page, mostly useful for production servers. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 50