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

[Bug 30292] New: Link recall to checkout
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '24

21 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30292 Bug ID: 30292 Summary: Link recall to checkout 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When patron biblio-level recall is issued, and an item/checkout combination is chosen to proceed with the actual checkout, we should store the checkout_id. This way we would avoid guessing the right checkout. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31369] New: Koha::Recalls->add_recall should validate there's a related checkout
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '24

21 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31369 Bug ID: 31369 Summary: Koha::Recalls->add_recall should validate there's a related checkout Change sponsored?: --- Product: Koha Version: unspecified 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I haven't really tried, but the code cleary relies on an $recall->checkout returning a Koha::Checkout object... Which shouldn't be taken for granted. The way it is constructed is fragile and makes the controller need to perform all the checks, that really belong here. It should probably throw an exception as well. Right now the code can generate a recall object (store it on the DB) and then explode because of the lack of the checkout. This also points to the need of a transaction. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 16223] New: Automatically remove any borrower debarments after a payment
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '24

21 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16223 Bug ID: 16223 Summary: Automatically remove any borrower debarments after a payment 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: larit(a)student.uef.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries debar Borrowers at the end of the year for having unpaid fines, like in Bug 15157. Currently librarians have to manually remove this type of debarments after Borrower has paid his/her fines. Add a system preference to define debarments that should be automatically removed after a payment is made, and add functionality to actually remove the defined debarments from Borrower. Also let libraries to define the amount of outstanding fines after payment after which the debarment will be removed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 152

[Bug 33825] New: Allow more granular options when sharing item templates
by bugzilla-daemon＠bugs.koha-community.org 20 Aug '24

20 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33825 Bug ID: 33825 Summary: Allow more granular options when sharing item templates 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: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be great if rather than shared with everyone or private it could be shared with a patron list, or users in your library group, or users at your library. With larger libraries sharing templates could easily become overwhelming if you really only want to share with a few other staff members. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 36850] New: Add volume of work $v to Elasticsearch series title MARC21 index mappings
by bugzilla-daemon＠bugs.koha-community.org 20 Aug '24

20 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36850 Bug ID: 36850 Summary: Add volume of work $v to Elasticsearch series title MARC21 index mappings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz We would like to add $v volume of work to the title-series elasticsearch index, or 'Series title' option in the advanced search dropdown. So the mappings would become as follows: * 440av * 490av * 830av -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 36847] New: Add "Multiple matches" as a match type when staging records
by bugzilla-daemon＠bugs.koha-community.org 20 Aug '24

20 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36847 Bug ID: 36847 Summary: Add "Multiple matches" as a match type when staging records Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mnero(a)oslri.net QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When staging records, the only way to tell if an incoming record matches on multiple existing records is to visually scan the entire results list. This is fine for small files but when loading large files, this is inefficient. It would be useful to have something like "Multiple matches found" to group any that matched on more than one record when sorting on Match Type for review. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 24773] New: Report spacing incorrect on import from Mana
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '24

17 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24773 Bug ID: 24773 Summary: Report spacing incorrect on import from Mana Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Mana-kb Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com When importing a report from Mana, there are missing whitespaces that break the query. I'm not certain whether the spaces are lost when the report comes into mana or when the report comes down to Koha. It might be dropping newlines? Whatever the details, the reports require an amount of correction after download that is prohibitive for some users. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 35325] New: Add the ERM module to Library Groups
by bugzilla-daemon＠bugs.koha-community.org 16 Aug '24

16 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35325 Bug ID: 35325 Summary: Add the ERM module to Library Groups Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: kelly(a)bywatersolutions.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com For multi-library systems in Koha currently, to use the ERM module, there is no separation to identify what agreements and licenses go to which library. It would be fantastic to add the ERM module to Library Groups to allow a way to separate and identify between libraries. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 17650] New: Create the option to save the cover with the uploaded files.
by bugzilla-daemon＠bugs.koha-community.org 16 Aug '24

16 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17650 Bug ID: 17650 Summary: Create the option to save the cover with the uploaded files. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: rsantellan(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Create the option to save the uploaded cover files with the rest of the files. Removing them from saving on the DB and save them on the koha uploads directory. Giving the implementation of creating cache miniatures for using them. There must be an option to enable this feature or not for backward compability. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 25983] New: Accessibility: 2.4.7 Focus Visibility
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '24

15 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25983 Bug ID: 25983 Summary: Accessibility: 2.4.7 Focus Visibility 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 The purpose of this success criterion is to help a person know which element has the keyboard focus. It must be possible for a person to know which element among multiple elements has the keyboard focus. If there is only one keyboard actionable control on the screen, the success criterion would be met because the visual design presents only one keyboard actionable item. Where the success criterion says “mode of operation”, this is to account for platforms which may not always show a focus indicator. In most cases, there is only one mode of operation so this success criterion applies. https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html -- You are receiving this mail because: You are watching all bug changes.

1 7