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

[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 38135] New: Add a 'display all combinations' option to the new circulation triggers page
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38135 Bug ID: 38135 Summary: Add a 'display all combinations' option to the new circulation triggers page 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 10190 Sometimes it's nice to be able to see all combinations of rule context (library, patron category, itemtype) at a glance. This isn't the default however, as it can quickly become overwhelming, so we only display the explicitly defined rules by default. To quickly calculate the number of rows in the table.. assuming we stick to display the library levels on their own pages, the tables for each would contain (number of patron categories + 1) * (number of item types + 1), so you can see how the table grows quickly.. but I think think it would be a useful view option. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 [Bug 10190] Overdue notice triggers based on item type -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 Martin Renvoize (ashimema) <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |38135 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38135 [Bug 38135] Add a 'display all combinations' option to the new circulation triggers page -- You are receiving this mail because: You are watching all bug changes.

1 0

[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

[Bug 4042] Public OPAC search can fall prey to web crawlers
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4042 Mengu Yazicioglu <mengu(a)devinim.com.tr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mengu(a)devinim.com.tr -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38121] New: Problem with a display constent and authority notices
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38121 Bug ID: 38121 Summary: Problem with a display constent and authority notices Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: Felix.Jutras(a)curateur.gouv.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 172527 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=172527&action=e… Screenshot of an example of the problem in the frech version of Koha I'm working on notice of authority to create authority for zones 600'S in cataloguing. For that i need to put terms to use and wrong term to not use using refferal « see » zone 400. The problem is that when I research a term to select it using the reserch tool at the end of any 600's zone in cataloguing it gives me the term using the display constant « utilisé pour/voir » in english « used for/see » so it means at the same time that the term I put at first i a correct term used for the term I put in the zone 400 of authority ctaloguing and an incorrect term and we have to see the term in the 400 zone to use it instead of the primary term. All the terms if they are correct or not are technically usable because i can choose all of them when I use the research tool. And when we change the option in 008/09 it does nothing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 37461] New: Typo in SMSSendAdditionalOptions description
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37461 Bug ID: 37461 Summary: Typo in SMSSendAdditionalOptions description Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 The SMSSendAdditionalOptions syspref description currently reads If the SMS::Send driver requires more options that just username/login and password, entire them here as YAML key/value pairs: It should be "enter them here". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 35651] New: Toggle for Advanced Editor should not show to staff without advanced_editor permissions
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '24

09 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35651 Bug ID: 35651 Summary: Toggle for Advanced Editor should not show to staff without advanced_editor permissions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Bug 34275 introduces a toggle button for users to move from the basic editor to the advanced editor easily. Currently, this toggle button shows to staff without the advanced editor permission. If a staff chooses to try to toggle to the advanced editor, they will be logged out. It would be best to not show the toggle button if the staff member does not have the advanced_editor permission. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17