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

[Bug 22320] New: Make ILL comments visible to all staff
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '25

04 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22320 Bug ID: 22320 Summary: Make ILL comments visible to all staff Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no Target Milestone: --- The ILL module has several kinds of comments that are only visible to staff who have access to the ILL module. This is a problem because any librarian can get the question "how is my ILL coming along" from a patron at the front desk. We should make some or all of the comments, and probably also the status, of ILL requests visible to all staff in the normal detail view, so they can answer questions about ILL loans that have not arrived at the library yet. It might be a good idea to have sysprefs to let libraries choose which comments should be visible to "other" staff. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 27049] New: It would be helpful to have a bulk waive of debts tool
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '25

04 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27049 Bug ID: 27049 Summary: It would be helpful to have a bulk waive of debts tool Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz With extended periods of libraries being closed and the recent complexities introduced into the accounts system for properly tracking accountline writeoffs, it would be helpful to have a command line too allowing administrators to writeoff accounts in bulk using the proper routines within Koha to properly record the action. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 50

[Bug 22435] New: account_offset types should be codes not descriptions
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '25

04 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22435 Bug ID: 22435 Summary: account_offset types should be codes not descriptions Change sponsored?: --- Product: Koha Version: master 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Currently, account_offset.types are all descriptive strings.. they should really be 'codes' to distinguish them from user-facing data and discourage developers from adding more untranslatable strings at the database level. I also don't think the current strings make a great deal of sense as they're often not describing an 'offset' action but the account action itself which is already better defined within the accountline.accounttype fields. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 282

[Bug 31095] New: Koha::Patron::Debarment should be updated to follow current Koha:: style
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '25

04 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31095 Bug ID: 31095 Summary: Koha::Patron::Debarment should be updated to follow current Koha:: style Change sponsored?: --- Product: Koha Version: master 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The Koha::Patron::Debarment module is written in the C4 style when it should really be a Koha::Object based class now. We should update it to the modern practices to enable simple addition of API's and more standard use codebase wide. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 151

[Bug 31197] New: Enabling Authority checks for all library staff but restrict the ability to edit Authority files to system admin
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '25

04 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31197 Bug ID: 31197 Summary: Enabling Authority checks for all library staff but restrict the ability to edit Authority files to system admin 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: susan.merner(a)nhs.net QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The ability to check whether an Authority such as a subject heading is in the authority file should be available to all staff BUT the option to edit authority files should be restricted to selected staff with system admin permissions. The Authority files affected would be Subject Headings (650), Series (490) and Corporate Authors. We want to ensure staff keep to the authorised lists and do not introduce or amend entries within Authorities. Is there a way to give cataloguers permission to have the "Link authorities automatically" button, but not edit, create or delete the authorities? If we could have a 'check authorities' button with no additional permissions, it would be really helpful! Or a way to flag unauthorised headings upon saving. We all need to be able to check if the subject headings (650 field) being pulled through by z39.50 are included in the authority file on Koha. At present, this is not possible, and there is no way to check z39.50 against the authority file. This raises an issue with cataloguers adding in unauthorised headings -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 28141] New: Accessibility: OPAC Advanced Search fields aren't labelled
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '25

03 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28141 Bug ID: 28141 Summary: Accessibility: OPAC Advanced Search fields aren't labelled 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: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The OPAC advanced search page has unlabelled search fields making them inaccessible to users of screen readers. This is a complicated page to get right and I'm not entirely sure how best to fix this. Here are some of the issues with the page currently: Example issue 1: When using NVDA to access the search form fields out of context, it is hard to tell which index (keyword, author, title etc.) you are searching. This is an issue when searching multiple fields at once. "Enter search terms; edit; has auto complete" It would be better if the search form field was linked to the index combo box. We could use aria-labelledby but there may be better ways to do this. Example Issue 2: The label for "search-field_0" is blank. Example Issue 3: The search terms are linked by 'and' but this isn't entirely clear out of context using a screen reader: " ;combo box; collapsed; Subject" "and;combo box; collapsed; Title" "and;combo box; collapsed; Publisher Location" "Location and availability:; combo box; collapsed; All Libraries" "Sort by:; combo box; collapsed; Relevance" "Language; combo box; collapsed; No Limit" Example Issue 4: The remove field buttons aren't programmatically linked to the field they are removing -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 19772] New: Wrong success message if PATRON_NOTE is not defined
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '25

03 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19772 Bug ID: 19772 Summary: Wrong success message if PATRON_NOTE is not defined Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: aleisha(a)catalyst.net.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 14224 There is no PATRON_NOTE notice template created for new installation. If the pref (AllowCheckoutNotes) is set to on, a patron can let a note from the OPAC and the message "Your note about $TITLE / has been saved and sent to the library." is display to the screen. But actually the Koha logs mention "No circulation PATRON_NOTE letter transported by email at /home/vagrant/kohaclone/C4/Letters.pm line 697." and no notice is generated Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14224 [Bug 14224] patron notes about item shown at check in -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 28638] New: Provide authority records via OAI-PMH
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '25

28 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28638 Bug ID: 28638 Summary: Provide authority records via OAI-PMH Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi, Now Koha only offers bibliographic records via OAI-PMH. We would like to extend the functionality for authority records as well. Michal -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 30329] New: Make URLLinkText configurable separately for items and bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '25

27 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30329 Bug ID: 30329 Summary: Make URLLinkText configurable separately for items and bibliographic records Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Bug 15352 changed the item record link from showing the URL to showing the text defined in the URLLinkText preference. You can now only empty out the pref and affect both bibliographic records and items to undo the change or accept that both show the same text. For the item URLs the use case is often a little different than for the ones in the bibliographic record so it would be nice to have this configurable separately which should also allow to opt for using the old behaviour of showing the URLs as is in the item records. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 30188] New: Hold ratios report is broken
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '25

24 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30188 Bug ID: 30188 Summary: Hold ratios report is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major 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 When trying to access the report I et: CGI::Compile::ROOT::kohadevbox_koha_circ_reserveratios_2epl::reserveratios_2epl(): DBI Exception: DBD::mysql::st execute failed: 'koha_kohadev.reserves.reservedate' isn't in GROUP BY at /usr/share/perl5/CGI/Emulate/PSGI.pm line 30 at /usr/share/perl5/DBIx/Class/Exception.pm line 77 Testing on ktd with sample database. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4