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

[Bug 26027] New: Add ability to let librarians know why higher priority holds were skipped
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26027 Bug ID: 26027 Summary: Add ability to let librarians know why higher priority holds were skipped 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com There are circumstances where higher priority holds are not trapped for a given item. These reasons range from requiring specific item or itemtype, to a hold being suspending, to a hold being given local holds priority. I think the best way to accomplish this would be to capture a list of the skipped holds and the reason for skipping them, then pass that to the template for display on the checkin screen when an item is trapped to fill a hold. This feedback would be especially useful if *none* of the holds were trapped for the given item. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 36696] New: Add an endpoint to fetch a constructed notice
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36696 Bug ID: 36696 Summary: Add an endpoint to fetch a constructed notice Change sponsored?: --- Product: Koha Version: unspecified 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 beneficial to have a way of fetching a built notice via API's. This would allow for more options when it comes to previewing and/or drafting notices. My own use case is for catalog concerns/tickets where I'd like to have the option for 'quick replies' that would allow for a notice template driven quick fill option for replying to patrons regarding catalog concerns (bug 32436). I also see the same use for the proposed 'message user' functionality in bug 29393. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 33398] New: Allow hold notification_method to be based on either messaging preferences or primary_contact_method
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33398 Bug ID: 33398 Summary: Allow hold notification_method to be based on either messaging preferences or primary_contact_method 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a waiting hold is triggered a popup appears that includes "Patron notification:". This is based on the patron messaging preferences for 'Hold filled'. We should allow libraries to choose between having this based on messaging preferences or primary_contact_method. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 33496] New: Add 'host_items' param to Koha::Biblio->items
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33496 Bug ID: 33496 Summary: Add 'host_items' param to Koha::Biblio->items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This patch will add an option to the $biblio->items method to allow retrieving the items and analytic items for a record. This is intended to allow fetching a single Items object, and related object, rather than having to fetch the items, and the host items, and push them together -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 25809] New: Make claims returned claims visible in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25809 Bug ID: 25809 Summary: Make claims returned claims visible in the OPAC 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When an item is claimed returned, there isn't any place in the OPAC for the patron to see their claims. Could we add a claims tab to the patron account on the OPAC, mirroring what's on the staff side? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 30463] New: Authority records are indexed on the fly
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30463 Bug ID: 30463 Summary: Authority records are indexed on the fly Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 27344 C4::AuthoritiesMarc::AddAuthority is indexing the record on the fly, we should index in background. 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 6

[Bug 27552] New: Allow batch cleaning & deleting of files in Manage staged MARC records
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27552 Bug ID: 27552 Summary: Allow batch cleaning & deleting of files in Manage staged MARC records Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org In 'Manage staged MARC records' it is a two-step process to remove a .mrc file. It first must be cleaned and then it must be deleted. It would be nice if it was possible to select multiple .mrc files to clean and delete rather than having to perform the two-step process for every single file. We do have a cron job that batch deletes the oldest files on a regular basis. But recently we exported and then re-imported some digital files. The acquisitions staff would rather not all of those .mrc files jumbled in with the .mrc files they are importing for new materials. So it would be helpful to be able to select specific files all at once and get rid of them in a batch. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 25962] New: In Advanced Editor mandatory subfields are not enforced if tag is not mandatory
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25962 Bug ID: 25962 Summary: In Advanced Editor mandatory subfields are not enforced if tag is not mandatory Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: - set your framework so the 100$a is mandatory but the 100 as a whole is not - open a new record in the advanced editor - save the record without a 100$a - edit framework to make the 100 mandatory as well as the 100$a - open a new record - try to save without a 100$a, get an error It doesn't break anything to have to mark the tag required as well as the subfield, but it's more work and it's confusingly different from how we enforce these in the regular editor. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 35799] New: Loading svc/cataloguing/framework bottlenecks advanced cataloging editor
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35799 Bug ID: 35799 Summary: Loading svc/cataloguing/framework bottlenecks advanced cataloging editor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl, nick(a)bywatersolutions.com The advanced editor loads /cgi-bin/koha/svc/cataloguing/framework?frameworkcode=&callback=define with RequireJS, with a 30 second timeout and no failure handling. That gives you 30 seconds for request, generation, and download, or the advanced editor simply won't load and will sit with a progress indicator spinning forever (and in versions before bug 34275 landed, with no way to edit bibs without editing your cookie so you can get back to using the basic editor). There are two ways (plus the combination) to have it fail to load, generation or network. Network is easy enough to reproduce even in koha-testing-docker, since Firefox's devtools have network throttling that goes back to "Regular 2G" which will certainly time it out. Generation is a bit harder without a decent sized database: with 300K bibs and 600K authorities in my production database it's easy to either write reports that ExtractValue(biblio_metadata.metadata...) and run several at once, or to notice that authority search results actually support &resultsperpage=1000 despite not having UI to set it, and opening a few pages of a thousand authority records that require searching for the number of bibs using each of those thousands of authorities. svc/cataloguing/framework is a json representation of the requested framework plus all authorized values. Frameworks are incredibly compressible, consisting of things like 4273 instances of value_builder of which 4253 are "value_builder":"", but it's sent uncompressed, so 1.8MB for something that gzips to 160KB. It's sent with Cache-Control: no-cache and Pragma: no-cache headers, so even though it continues to load after the RequireJS timeout, just sitting waiting for it (I've had a painfully large number of times where it would consistently load in 31 or 32 seconds) and then reloading does no good. Not caching doesn't really do much of anything to ensure freshness, since if you stick to just one framework in an open instance of the editor, you won't ever reload svc/cataloguing/framework, but it does at least mean that if you know you've changed a framework and you don't see the change you can just open the editor in a new tab without having to actually clear the browser cache. The authorized values are too small of a percentage of the file size to make much difference there, but, they don't vary with the framework, so there's no reason to reload them for each change of framework, and they are 3/4 of the database connections (one for AV, one for itemtypes, one for classification sources), so loading them once separately probably would help for some generation-limited cases and certainly would for the combination of generation- and network-limited cases. Getting three db connections and then loading a tiny file in less than 30 seconds, then getting one db connection and loading a large file in less than a separate 30 seconds is easier than getting four connections and a large file in one 30 second period. Beyond that, there's no clear easy answer. Solving for my sketchy internet at home is easy, just gzip the json after generating it, but that adds server (though not db server) load. Okay, generate an already gzipped file once and serve that, after all, I typically only change my frameworks twice a year, how fresh do they need to be? But, editing frameworks consists of hundreds of tiny saves of each subfield of each tag, so making each one regenerate a static file is going to be painful. Okay, let the browser cache the output so at least a reload after getting it to load in 35 seconds works. Cache it for how long? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 28805] New: Batch checkout shoudl have on-site checkout option
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28805 Bug ID: 28805 Summary: Batch checkout shoudl have on-site checkout option Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The batch checkout is very useful, but currently doesn't support all advanced options of the normal search page. It's missing the "on-site checkout" functionality. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44