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

[Bug 40232] New: [DOCS] Use Vale to "lint" the manual against the style guide/content development guide rules
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '25

25 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40232 Bug ID: 40232 Summary: [DOCS] Use Vale to "lint" the manual against the style guide/content development guide rules 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: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)openfifth.co.uk, philip.orr(a)lmscloud.de Use Vale (https://vale.sh/) to check the manual against the content development guide/style guide rules. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 29712] New: [DOCS] [Omnibus] Content development guide
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '25

25 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29712 Bug ID: 29712 Summary: [DOCS] [Omnibus] Content development guide Change sponsored?: --- Product: Koha Version: master Hardware: All URL: https://wiki.koha-community.org/wiki/Documentation_-_C ontent_Development_Guide OS: All Status: ASSIGNED Severity: enhancement Priority: P3 Component: Documentation Assignee: david(a)davidnind.com Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org Omnibus bug for the creation of a content development guide for the documentation team. It will include: * a style guide: guidelines for writing clear and concise content, including grammar and word lists * an information model: structures and guidelines to help us write different types of content consistently * a content strategy: a plan outlining how we develop content, including the types of information products we create, the tools we use, and the processes we follow -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 40233] New: [DOCS] Look at using GitPod to create a browser-based environment for editing the manual and previewing changes
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '25

25 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40233 Bug ID: 40233 Summary: [DOCS] Look at using GitPod to create a browser-based environment for editing the manual and previewing changes 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: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)openfifth.co.uk, philip.orr(a)lmscloud.de Investigate using GitPod (https://www.gitpod.io/) to create a browser-based editing environment for the manual. Features include: - Editing environment pre-configured with VSCode and required modules - Ability to preview the manual with the changes made (rather than just diffs) While GitPod is not FOSS, it could provide an alternative environment for editing the manual that is easier to use for potential contributors. Particularly being able to preview the manual with the changes made. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 40231] New: [DOCS] Accessibility issues for the manual
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '25

25 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40231 Bug ID: 40231 Summary: [DOCS] Accessibility issues for 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: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)openfifth.co.uk, philip.orr(a)lmscloud.de This is an omnibus bug to identify and fix accessibility issues with the manual. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 29577] New: Link bibs to authorities fails if relator terms are in records to be linked
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '25

24 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29577 Bug ID: 29577 Summary: Link bibs to authorities fails if relator terms are in records to be linked Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: bernard.scaife(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org If you use a relator ($e) in the authority and biblio records and run link_bibs_to_authorities.pl, it does not link the records although they are a match Observed at 20.11.09 Workflow: 1. Add PERSONAL authority record with 100a Berridge, Elizabeth and 100e actor 2. Add new biblio record with 700a Berridge, Elizabeth and 700e actor NB/ 700 Field should not be under authority control whilst this data is entered to simulate data that is not linked. Temporarily amend this in cataloguing template for 700 field 3. Run link biblio script on the new test bib's biblionumber: sudo koha-shell -c "/usr/share/koha/bin/link_bibs_to_authorities.pl --bib-limit='biblionumber=<yourbibnumber>' --verbose" <site> 4. Observe log which will say Number of bibs checked: 1 Number of headings linked: 0 Number of headings unlinked: 1 5. Remove 100e actor (from authority) and 700e actor (from biblio) and save 6. Rerun linker script (step 3) Number of bibs checked: 1 Number of headings linked: 1 Number of headings unlinked: 0 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 38537] New: 'Edit items in a batch' should open in a new tab
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '25

24 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38537 Bug ID: 38537 Summary: 'Edit items in a batch' should open in a new tab Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: Laura.escamilla(a)bywatersolutions.com Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Editing items in a batch should open in a new tab - it currently opens within the same tab. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 25098] New: automatic item modification needs report function
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '25

24 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25098 Bug ID: 25098 Summary: automatic item modification needs report function 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: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The automatic item modification cronjob does not have an option for reporting the items that were modified. Can the cronjob log in action_logs, or as a report that's emailed, or into a logfile that can be downloaded? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 40228] New: In inventory, "barcodes not found" are not in the array and therefore not exported
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '25

24 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40228 Bug ID: 40228 Summary: In inventory, "barcodes not found" are not in the array and therefore not exported 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: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When using the inventory tool while checking the box "on export as csv", barcode not found are exported in the csv. However, when using the inventory tool and exporting as a csv the results, barcodes are not exported. This is normal because they are displayed as notification and not in the array. It is a bit weird to have 2 different behaviours. A solution would be to append the errors in the array of results. Should we maybe have a syspref to decide if we append or not ? Can we consider that the not exported array should always have contained the barcode error ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 40227] New: When TT notices fail at generation, no error is visible in the interface
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '25

24 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40227 Bug ID: 40227 Summary: When TT notices fail at generation, no error is visible in the interface Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When using an invalid letter model, the notification will not be generated and will not appear as failed in the message_queue table. There is no way to see that a notification has failed to generate (except by knowing he has requested a notice that has not appeared, it is easy for welcome as it is manual but way harder for DUE, PPREDUE, ... that are automaticly generated). Step to reproduce : 1- Select a borrower with an email address (primay email, no need to be a valid one) 2- On the detail page of the patron, click on "More" then "Send welcoe notice" 3- In tab Notices, check that it is generated correctly (default model) 4- Go to Tools > Notices and slip 5- Update the notice WELCOME with the following model ``` Welcome [% borrower.date_due %] ``` No warning is generated on the interface when saving 6- Repeat step 2 7- No notice is generated, no interface warning/error/message is generated, no log error either : the librarian has no way of knowing that it has failed ! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 37234] New: Order of subfields when there are multiple of a same subfield
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '25

24 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37234 Bug ID: 37234 Summary: Order of subfields when there are multiple of a same subfield Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Bug 22666 fixed the order of the subfields when using an authority record in a bibliographic record. There is a case when this still doesn't work: if the authority record has multiples of a subfield, but not together. Take the following authority Music--Social aspects--Asia--History. it goes $a $x $z $x (notice the two x separated by the z). When this is copied in a bibliographic record, it is copied as Music -- Social aspects -- History -- Asia. $a $x $x $z; the two x were brought together. To recreate: 1. Go to Authorities 2. Click on New authority > Topical term 3. Fill out the mandatory fields (000, 003, 005, 008, 040$a) 4. Click on tab 1 5. Click on 150 - HEADING - TOPICAL TERM 6. Fill out the field - a: Music - x: Social aspects - z: Asia 7. Click on the icon to double the x subfield 8. Type in History 9. Move the History subfield at the end, under Asia 10. Click Save 11. Go to Cataloging > New record 12. Click on tab 6 13. Click on the Tag editor icon next to 650$a 14. In "Search main heading:" type music social 15. Click Choose next to Music Social aspects Asia History --> It is copied in the bibliographic record as Music Social aspects **History Asia** (instead of Music Social aspects **Asia History**) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2