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

[Bug 37568] New: Explain category types in the manual
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37568 Bug ID: 37568 Summary: Explain category types in the manual Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: philip.orr(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de In the manual section on patron categories, the section on category types ("Adult", "Child", "Staff"... etc.) is unclear on what the category types actually do. It would be good to document what selecting a specific category type actually does for the patrons created using this category type. Manual page: https://koha-community.org/manual/latest/en/html/administration.html#patron… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 37696] New: Improve perldoc for SIP server
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37696 Bug ID: 37696 Summary: Improve perldoc for SIP server Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de The perldoc for C4/SIP/SIPServer.pm gives off a style warning as per bug 37087#13 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 36344] New: Add schema changes summary to release notes
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36344 Bug ID: 36344 Summary: Add schema changes summary to release notes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org The community release notes have summaries at the end for new and deleted system preferences and new authorised values and letter codes but none for schema changes. A list of new/deleted tables and one for new/renamed/deleted columns in tables would be useful. For example, issues.renewals became issues.renewals_count in 21.11 but this change was buried in bug 30275 (and reports broke as we missed mention of the change). And the schema change in bug 26057 altered the meaning of ‘missing in transit’ as we had defined it in our MIT reports (so they broke too). Schema changes are now included in our ‘upgrade pain-points’ and we will look very closely at them. A summary of the changes would be very useful. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 36391] New: There is no listing of the cron job : archive_purchase_suggestions in the manual
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36391 Bug ID: 36391 Summary: There is no listing of the cron job : archive_purchase_suggestions in the manual Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org There is no listing of the cron job: archive_purchase_suggestions in the current manual. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 37851] New: Add ability to edit facet labels in Elastic Search Facet Order
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37851 Bug ID: 37851 Summary: Add ability to edit facet labels in Elastic Search Facet Order 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: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently the label that is displayed is a database table name. The display is the same in the OPAC and Staff Interface. It would be nice to edit the facet label so the library can customize and add user friendly language. It would also allow the library to have nicer formatting, like consistent capitalization. Translations could be a factor, but could be added later. Right now, labels like 'ln' or 'su-geo' don't make much sense to the average user. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 36604] New: Document what statistics wizards actually count
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36604 Bug ID: 36604 Summary: Document what statistics wizards actually count Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I find the statistic wizards very opaque and it's not clear at all what they actually count. I often have questions about them from clients, especially when libraries are doing their end-of-year statistics. I try to read the SQL in the .pl as best as I can, but it would be great if we could describe what each option in each wizard does in the manual. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 33793] New: Add method to define limited access to run reports
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33793 Bug ID: 33793 Summary: Add method to define limited access to run reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org Currently a user with the execute_reports permission can run any report in the system. A library may wish for a given user to be able run some reports but not others. It would be great to have a mechanism for allowing limited reports access. Maybe something akin to the SubfieldsToAllowForRestrictedEditing preference? We could create ReportGroupsToAllowForRestrictedExecution, in which one selects groups of reports. We add a new execute_reports_restricted permission. A user with that permission can only run reports in the groups specified in the preference. Or maybe ditch the system preference and add a "restricted access" flag to each report? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 40203] New: export link to local covers in a MARC field
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40203 Bug ID: 40203 Summary: export link to local covers in a MARC field 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: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To improve the integration between Koha and Discovery tools or other kind of portals, it could be nice to export the link to local covers in a MARC field. See also https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16916 OAI - Local covers as OAI-DC relations tags -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 40196] New: Add links from license to linked agreements
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40196 Bug ID: 40196 Summary: Add links from license to linked agreements Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: clemens.tubach(a)kit.edu, jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, michaela.sieber(a)kit.edu, pedro.amorim(a)openfifth.co.uk Currently there is a link from the agreement to the lisense, but no link from the license to the agreement. To test: - Activate the ERMModule - Create an agreement - Create a license - Link both from the agreement Confirm (negative) - There is no visible link on the license view: .../cgi-bin/koha/erm/licenses/1 - there is no visible link on the edit form: .../cgi-bin/koha/erm/licenses/edit/1 Confirm (positive) - Linked licenses are visible on the agreement view: .../cgi-bin/koha/erm/agreements/1 - Linked licenses are visible on the edit form: .../cgi-bin/koha/erm/agreements/edit/1 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 32610] New: Add ability to specify patron attribute as a date and apply flatpickr
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '25

20 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32610 Bug ID: 32610 Summary: Add ability to specify patron attribute as a date and apply flatpickr Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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 Sometimes libraries use patron extended attributes that are dates. It would be handy if we could specify that a particular attribute is a date and then have it become a flatpickr instance. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 94