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

[Bug 29168] New: Disable "Request article" links when limit is reached
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '26

31 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29168 Bug ID: 29168 Summary: Disable "Request article" links when limit is reached Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Since bug 27945 we can limit article request per patron's category. However the "request article" links (detail and search views) are still active. We could disable them and add a tooltip. -- You are receiving this mail because: You are watching all bug changes.

1 47

[Bug 18583] New: Add the ability to merge multiple authorities
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '26

31 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18583 Bug ID: 18583 Summary: Add the ability to merge multiple authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Since bug 8064 it is possible to merge multiple bibliographic records at once, it would be nice to be able to do the same thing with authority records. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 29016] New: viewlog.pl - Problem with many entries
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '26

31 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29016 Bug ID: 29016 Summary: viewlog.pl - Problem with many entries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: vitorfernandes87(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The script viewlog.pl it's very slow because it retrieves all action logs at the same time. It should use KohaTables with pagination/number max of returning entries like other Koha tables (API + AJAX wrapper). Test plan: - We need a database with a large number of entries in the action_logs table (200k for example) - Open view logs tool (viewlog.pl) - Select all modules and search - Timeout or a long waiting time -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 98

[Bug 26653] New: Allow editing of item notes on moredetail.pl with circulation permission
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '26

31 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26653 Bug ID: 26653 Summary: Allow editing of item notes on moredetail.pl with circulation permission 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 If a user has circulation permissions, they can edit the lost/damaged/withdrawn statuses of an item on moredetail.pl (the items tab in the catalog). However, they cannot edit the public and non-public notes for that item. Those notes are only editable on this if one also has edit_items permission, which opens up a lot more actions. I feel the editing of these notes from moredetail should also fall under circulation permissions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 32030] New: Electronic resource management (ERM)
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '26

30 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32030 Bug ID: 32030 Summary: Electronic resource management (ERM) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: new feature Priority: P5 - low Component: Staff Client Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We are building an Electronic Resource Management (eRM) module for Koha. See the related resources for earlier communication: [Koha] Electronic Resource Management for Koha https://lists.katipo.co.nz/pipermail/koha/2022-February/057447.html “Electronic resource management (ERM) is the practices and techniques used by librarians and library staff to track the selection, acquisition, licensing, access, maintenance, usage, evaluation, retention, and de-selection of a library’s electronic information resources. These resources include, but are not limited to, electronic journals, electronic books, streaming media, databases, datasets, CD-ROMs, and computer software.” https://en.wikipedia.org/wiki/Electronic_resource_management Before the emergence of eRM's, libraries would typically store details of electronic subscriptions in a manual way, for example, Excel spreadsheets, or in cupboards or filing cupboards as paper documents. An eRM allows libraries to store and organise these documents electronically. It also services as an index to electronic subscriptions. An eRM can track the whole lifecycle of an electronic resource, from acquisition, to negotiating an agreement with a publisher, storing the license information, activating title and package resources online to identifying usage patterns with resources. Libraries will vary in size from small, specialist library (with maybe a few topic specific resources) like a music library to large universities who will subscribe to tens of thousands of titles. It maybe that a library wants to record a few dozens resources each with their own subscription with a publisher, or track thousands of titles from aggregators like EBSCO. The code is available at https://gitlab.com/joubu/Koha/-/commits/erm The entry point is at https://tree.taiga.io/project/joubu-koha-erm/wiki/home And the current work activities can be seen at https://tree.taiga.io/project/joubu-koha-erm/kanban -- You are receiving this mail because: You are watching all bug changes.

1 91

[Bug 30819] New: Not able to adjust size of barcode numbers
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '26

29 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30819 Bug ID: 30819 Summary: Not able to adjust size of barcode numbers Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Moved from the original bug 10762: (In reply to Jesse Maseto from comment #0) > I created a new layout (section 2.5.3.1 in the manual) that just shows the > barcode, and I set the font size big. First I did 14, then 32 just to make > sure my eyes weren't deceiving me. The numbers below the barcode didn't > change size! > > It seems like the font settings only affect the bibliographic data. What I > want to change is the barcode number itself. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 15739] New: Saving a new printer profile does not work
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '26

29 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15739 Bug ID: 15739 Summary: Saving a new printer profile does not work Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org If you leave either the Printer Name or Paper Bin field empty (ie only putting something in one of those fields and leaving the other empty) then you will get a software error upon clicking Save Can't call method "save" without a package or object reference at /home/vagrant/kohaclone/patroncards/edit-profile.pl line 72. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 28806] New: Labels exported as PDF create zero sized PDF files.
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '26

28 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28806 Bug ID: 28806 Summary: Labels exported as PDF create zero sized PDF files. Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org In my first tries to create biblio labels, I see that export to PDF creates zero sized PDF files, in both individual/single and batch modes. Coult it be due to non-latin characters (Greek) appearing in the label contents? Export to CSV does produce files with the expected number of rows, albeit with non-usable characters. -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 23003] New: Accessibility improvements
by bugzilla-daemon＠bugs.koha-community.org 28 Jul '26

28 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23003 Bug ID: 23003 Summary: Accessibility improvements Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- >From the french mailing list: The Ministry of Culture published a study detailing the accessibility of different OPAC in France. There are some areas that we could improve. Koha gets a quite good score, but a 'C' is given for: 1. the "skip links" - https://www.wikiwand.com/en/Skip_link 2. No search autocomplete 3. Button to place a hold on Also they pointed out that Tanaguru gives Koha a score of 65%, we could certainly improve it. https://www.tanaguru.com/en/open-source-tools-tanaguru/ Important note: The tests have been done using the following catalogue: http://cat-bib.nimes.fr/ (Koha 17.11.13) http://www.culture.gouv.fr/Thematiques/Livre-et-Lecture/Actualites/Barometr… http://www.culture.gouv.fr/content/download/213998/2245555/version/2/file/B… -- You are receiving this mail because: You are watching all bug changes.

1 60

[Bug 31484] New: Renewals disabled message doesn't display all reasons why something cannot be renewed
by bugzilla-daemon＠bugs.koha-community.org 27 Jul '26

27 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31484 Bug ID: 31484 Summary: Renewals disabled message doesn't display all reasons why something cannot be renewed 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 There are many reasons why the renewals-disabled button might display in the issues table but not all of them will display depending on the circumstance, this can hamper librarians ability to make correct choices. For example: 1. Have an item checkout out what can be renewed at least one time BUT make that item overdue. 2. In the renewal column you'll see "0 Not allowed: overdue". That is good. 3. Have 'AllowRenewalOnHoldOverride' set to 'Don't allow' 4. Place the same item from 1-2 on hold. Make it an item level hold on that specific item. 5. Look at the issues table again, it still says "0 Not allowed: overdue". 6. The message should include some language saying the item can't be renewed becuase it is on hold AND it is overdue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2