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

[Bug 35957] New: Does Serial module still allow saving 0000-00-00 in database?
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '26

30 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35957 Bug ID: 35957 Summary: Does Serial module still allow saving 0000-00-00 in database? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Seeing two issues in 22.11 with invalid/empty date fields: [1] Exception 'Koha::Exceptions::WrongParameter' thrown 'Invalid date '00-1-11-30' passed to output_pref' Crash in output_pref comes from serials/subscription-add.pl line 405 $nextacquidate = $nextacquidate ? output_pref( { str => $nextacquidate, dateonly => 1, dateformat => 'iso' } ) : $firstacquidate; So it received a 0000-00-00. [2] Receive step on serial collection. Save issue without filling dates: | 9531 | 156662 | 318 | No. 12 | 11 | 0 | 0 | 1 | 0000-00-00 | | 0000-00-00 | | NULL | 0 | NULL | Planned and publisheddate were NULL but are now 0000-00-00. Did not check master. Probably still the same? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 38425] New: Add links to full texts based on identifiers
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '26

30 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38425 Bug ID: 38425 Summary: Add links to full texts based on identifiers 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: alexander.wagner(a)desy.de QA Contact: testopia(a)bugs.koha-community.org Marc21 allows to add persistent identifiers to `024 7?` by means of subfields `$2` and `$a`. E.g. one could give the DOI of an eBook as ``` 024 7_ $2doi $a 10.000/123.456.789 ``` For `$2` the LoC refers to the list of standard identifiers, that is actually quite long: https://www.loc.gov/standards/sourcelist/standard-identifier.html Currently, it seems Koha creates a link only if there is a URL in `856 4_` which requires duplication of data. Especially of scientific libraries it would be helpful if ids pointing to "well known" services that assign PIDs would also trigger such a display to point the users to the full texts. The most relevant in this context seem to be: - DOI - PMID - PMC - arXiv - handle - urn In other contexts OpenLibrary was also mentioned. -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 37638] New: Link permissions to entry in the manual
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '26

30 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37638 Bug ID: 37638 Summary: Link permissions to entry in the manual Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lauren_denny(a)sil.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Similar to bug 37624, create a link by the permission that takes you to the manual. If applicable, it would also be helpful to put a note by the permission if a system preference is required. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 20844] New: Reset a hold when it is missing after allocation
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20844 Bug ID: 20844 Summary: Reset a hold when it is missing after allocation Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: hughr(a)brimbank.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There currently is no simple way to 'deallocate' a hold if it has gone missing after it is allocated to a patron but before they collect it. This enhancement would work as follows: 1. item is allocated 2. item cannot be located when patron tries to collect it 3. staff member marks item as Lost 4. if hold was originally a bib-level hold, hold reverts from being specific to the missing item, back to a bib-level hold with priority 1. 5. if hold was originally item-level, staff member gets an alert asking whether to cancel or retain the hold 6. (optionally?) a 'lost hold' notice is queued to be sent to the patron This bug is related to the original description of https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19287#c32 and also to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15679 To do it properly, it may require a couple of new settings, something like: LostBibLevelHoldsRevert SendLostHoldNotices -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 150

[Bug 23998] New: Messages REST API
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23998 Bug ID: 23998 Summary: Messages REST API Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi Expose messages table via REST API. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 38399] New: Create a script that lists records that are not linked to any authority
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38399 Bug ID: 38399 Summary: Create a script that lists records that are not linked to any authority Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: enica(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz It would be nice to have a script that would list which bibliographic records are not linked to any authorities. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 37041] New: Logging into addbiblio.pl triggers a 403
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37041 Bug ID: 37041 Summary: Logging into addbiblio.pl triggers a 403 Change sponsored?: --- Product: Koha Version: Main 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org As Michal Kula noted on Mattermost, trying to log into http://localhost:8081/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=99… in main will yield a bizarre HTTP response that includes headers for a 403 response and a 200 response... This is partially due to bug 37040, but it's mostly due to a bug in addbiblio.pl where the form builder is generating a 403 that gets printed before the 200 response somehow... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 78

[Bug 38327] New: 403 errors when logging back into Koha.
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38327 Bug ID: 38327 Summary: 403 errors when logging back into Koha. Change sponsored?: --- Product: Koha Version: Main 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Firstly, I have been unable to recreate this issue myself, either in a production environment or in k-t-d. Many libraries are reporting 403 errors after signing back into Koha. The only remedy seems to be clearing the browser cache. This is happening to sessions in the staff client but also happening frequently in the SCO module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 34460] New: Patron category should regulate if account can have permissions
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34460 Bug ID: 34460 Summary: Patron category should regulate if account can have permissions 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Permission management would be simpler if there were a setting in patron categories that indicate whether that category of patron can have permissions. - If no, that option would not appear in the patron menu. - If patron category is changed to a category that does not allow permissions, any existing permissions should be cleared when change is saved. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 38330] New: Make bib-level suppression a biblio table field instead of part of a marc tag
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '26

28 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38330 Bug ID: 38330 Summary: Make bib-level suppression a biblio table field instead of part of a marc tag 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: danielle.elder(a)law.utexas.edu QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Suppression should be a biblio table field instead of in a marc field. Running reports with it to extract that field each time is not optimal. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 104