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

[Bug 37478] New: bulkmarcimport.pl can die on bad records
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37478 Bug ID: 37478 Summary: bulkmarcimport.pl can die on bad records Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz bulkmarcimport.pl will die on xml parsing errors when trying to convert the saved metadata (marcxml) back into a MARC::Record object Two cases we have seen are an invalid characters: :9: parser error : PCDATA invalid Char value 31 <controlfield tag="003">aPGcC</controlfield> and invalid/missing subfield: :91: parser error : attributes construct error <subfield code=""">Among nineteenth-century women's rights reformers, Elizab It turns out MARC::Record can read the incoming file - we can convert it to xml to save as metadata, but only on trying to create the record out of the xml do we die. This may point to a bug in MARC::Record -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 36117] New: Can svc/bib_profile be removed?
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36117 Bug ID: 36117 Summary: Can svc/bib_profile be removed? Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Is this used? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 38796] New: ERM : record for print documents should not be imported into ERM
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '25

04 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38796 Bug ID: 38796 Summary: ERM : record for print documents should not be imported into ERM Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Not sure if it is a bug or not, but I don't understand the purpose of importing records of "print" documents (without a link in 856) into ERM Currently Koha imports them but the field "coverage_depth" takes the value "print" Is it useful for some workflows ? Perhaps those records should better not be taken into account if they are present in the list ? -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 38060] New: Bookings table does not render if tab opened from the URL
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '25

03 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38060 Bug ID: 38060 Summary: Bookings table does not render if tab opened from the URL Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: pedro.amorim(a)ptfs-europe.com Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 37047 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37047 [Bug 37047] Patron bookings are not visible from patrons checkout page -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 25323] New: Patrons can act as their own guarantor
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '25

03 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25323 Bug ID: 25323 Summary: Patrons can act as their own guarantor 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: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When searching for a patron to act as a guarantor, if the guarantee's record is returned it can be selected, therefore becoming his/her's own guarantor. This makes no sense. To reproduce: 1) Create two users, a parent and a child both with the same surname (for example Parent Smith and Child Smith) 2) Edit the child record and under the Guarantor information, use the "Search to add" button to search for a guarantor. 3) Search for Smith. Both Parent Smith and Child Smith will be listed in the results. 4) Select Child Smith and save the user record. Child Smith is now the guarantor for Child Smith. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 38787] New: "Paid for?" message in item info lists patrons who did not pay for item
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38787 Bug ID: 38787 Summary: "Paid for?" message in item info lists patrons who did not pay for item Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com Depends on: 19919 To confirm: - have an item checked out - mark it lost, generating a fee on the patron account - check it in, generating a full refund on the patron account - mark the item lost again (it doesn't matter if it's checked out to another patron or not) - go to moredetail.pl, see your item shows "Paid for: [your patron]" Bug 19919 introduced logic to determine whether or not an item had previously been lost and then paid for. It will show the "Paid for" message and a patron's name and barcode if: - the item is currently lost - there is an accountlines entry linked to that item number with the following qualities: -- accountlines.debit_type_code = LOST -- accountlines.status != 'RETURNED' -- accountlines.amountoutstanding = 0 So, show this if the item has an associated charge that reached $0 via means other than a return. But when a lost item gets checked in we update that status to "FOUND" and anyway the debit for a lost item that gets paid off has a NULL status, so it won't be found by looking for status != "FOUND". Would it work to look for lines with debit_type_code='LOST', amoundoutstanding=0, and status IS NULL? I don't have a good enough handle on accountlines statuses to be sure. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19919 [Bug 19919] Writing off a Lost Item Fee marks as "Paid for by patron" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 37460] New: Skip Issues Seems to Not Work for Subscriptions Using the Publication Date Parts
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37460 Bug ID: 37460 Summary: Skip Issues Seems to Not Work for Subscriptions Using the Publication Date Parts Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 169512 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=169512&action=e… pattern With bug 32392, a user can receive an issue and then skip the next issue or multiple issues. However, this does not seem to be working when using the bug [35646] Allows using the publication date parts for serial numbering. It will not skip an issue as instructed. Using this skip issues option for other numbering patterns does work, such as a simple Volume Number Issue. Attaching my Pattern for more clarification -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 26024] New: Purge undone of zebraqueue in cleanup_database.pl
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26024 Bug ID: 26024 Summary: Purge undone of zebraqueue in cleanup_database.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com Purge script misc/cronjobs/cleanup_database.pl with --zebraqueue DAYS will delete entries from zebraqueue table with done=1 We now start to use Elasticsearch only so entries of zebraqueue with done=0 stay in database. I propose we purge all entries in cleanup_database.pl. Even with zebra, if indexing does not occur after several days (30 by default), there is a problem and one need a full rebuild. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 37738] New: Framework update accessibility for existing installations
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37738 Bug ID: 37738 Summary: Framework update accessibility for existing installations 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: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be nice if updated frameworks were available for download in some way. As frameworks are periodically updated in Koha to stay up-to-date with Library of Congress changes. it becomes difficult for existing installations to know about/receive those updates. While it is possible for existing installations to monitor bugs and see what the changes are, they don't receive those updates in the frameworks with an upgrade. This requires a library to seek out the bugs and do manual updates. There may be a number of ways to alert a library that updates are available and/or provide a download of the new framework. Perhaps there could be an alert in Administration that says updates are available, with a link to download the new framework from somewhere. This way a library can choose whether to overlay or manually update a framework as needed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 32168] New: Editing date/datetime fields without the dateaccessioned.pl plugin can cause errors
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32168 Bug ID: 32168 Summary: Editing date/datetime fields without the dateaccessioned.pl plugin can cause errors 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When editing items that are date or datetime formatted without the dateaccessioned cataloging plugin it is quite easy to cause an error. To recreate: 1. Make sure some 952 field with dates (datelastseen, dateaccessioned ) are visible in the editor but make sure the dateaccessiond plugin is turned off. 2. Set the date format system preference to mm/dd/yyyy 3. Edit an item and attempt to edit one of the date fields to something in the correct dateformat, like 11/11/2018. 4. You get an error as Koha is expecting the SQL date type format of YYYY-MM-DD. I'm not sure how to best solve this. My first thought is that we should require the dateaccessioned.pl plugin on date fields. Or we could add a hint about format? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5