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

[Bug 27824] New: Report batch operations break with space in placeholder
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27824 Bug ID: 27824 Summary: Report batch operations break with space in placeholder Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 23390 I found this bug while testing Bug 5697: Using the system for defining a column name placeholder (Bug 23390), if there is a space inside the column name placeholder it won't work. The SQL example in Bug 5697: SELECT i.itemnumber, i.itemnumber as Exemplarnummber, [[i.itemnumber| itemnumber for batch]], CONCAT('<a href=\"/cgi-bin/koha/cataloguing/additem.pl?op=edititem&biblionumber=', i.biblionumber, '&itemnumber=', i.itemnumber, '#edititem', '\">', i.itemnumber, '</a>' ) AS "itemnumber as edit link" FROM items i "[[i.itemnumber| itemnumber for batch]]" has a space before "itemnumber for batch." With that space removed it works as expected. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23390 [Bug 23390] Add placeholder syntax for column names -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 26862] New: MARC 530 is missing a descriptive lavel in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26862 Bug ID: 26862 Summary: MARC 530 is missing a descriptive lavel in the OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org In the XSLT 530 is missing a label with the description of the field. To test: - Catalog a 530 in any record - Verify the display in the OPAC and staff is missing the label and the content appears in a different size than the rest of the entries from the bibliographic record http://www.loc.gov/marc/bibliographic/bd530.html -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 18855] New: Fines cronjob can cause duplicate fines if run during active circulation
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18855 Bug ID: 18855 Summary: Fines cronjob can cause duplicate fines if run during active circulation Change sponsored?: --- Product: Koha Version: master 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On systems with a decent amount of fines it seems the fines cron can cause issues for patrons. The problem seems to be: 1 - Fines job runs and selects overdues 2 - Patron with an overdue returns books, fine is updated, item is checked in 3 - Fines job iterates to the item that was checked in during step 2, sees there is no accruing fine, generates a new accruing fine I am not sure what the best solution here is, possibly we should confirm the issue before generating the fine in the cronjob? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 60

[Bug 23775] New: Claiming a serial issue doesn't create the next one
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23775 Bug ID: 23775 Summary: Claiming a serial issue doesn't create the next one 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: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com == test plan == 1. have a vendor with an email address for claiming late issues 2. have a subscription linked to this vendor - You can create a new one with arbitrary values 3. Go to "Serial collection" 4. click "Edit serials" 5. Status of the latest: change from Expected to Claimed 6. save 7. see that the next issue has been created 8. go to /cgi-bin/koha/serials/claims.pl 9. make a claim on the expected issue of the previously used serial 10. Then you see that the next issue hasn't been created -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 26700] New: Remove unused C4/SIP/t directory
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26700 Bug ID: 26700 Summary: Remove unused C4/SIP/t directory Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor 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 It doesn't seem like C4/SIP/t is used, so we may as well remove it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 24517] New: Zebra: date-entered-on-file misses 6th position
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '23

18 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24517 Bug ID: 24517 Summary: Zebra: date-entered-on-file misses 6th position Change sponsored?: --- Product: Koha Version: master 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Date entered on file is in MARC21 tag 008 position 00 to 05 (or 1-6 for normal humans). In Koha only the first 5 digits are indexed with Zebra. Does not really facilitate searching ;) <index_control_field tag="008" offset="0" length="5"> <target_index>date-entered-on-file:n</target_index> </index_control_field> <index_control_field tag="008" offset="0" length="5"> <target_index>date-entered-on-file:s</target_index> </index_control_field> <xslo:template match="marc:controlfield[@tag='008']"> <z:index name="date-entered-on-file:n"> <xslo:value-of select="substring(., 1, 5)"/> </z:index> <z:index name="date-entered-on-file:s"> <xslo:value-of select="substring(., 1, 5)"/> </z:index> Elasticsearch appears to do a better job: date-entered-on-file: label: date-entered-on-file mappings: - facet: '' marc_field: '008_/0-5' marc_type: marc21 sort: ~ suggestible: '' - facet: '' marc_field: '008_/0-5' marc_type: normarc sort: ~ suggestible: '' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 29769] New: Claim return status cannot be changed without checking item in
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '23

16 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29769 Bug ID: 29769 Summary: Claim return status cannot be changed without checking item in Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With the addition of bug 24279, libraries can no longer change the status of a claim return without checking the item in, which is not a desired behavior. Example: a library sets an item to claims return, looks for the item for three months per policy, item is not found, status needs to be changed from Claim to Lost so the patron is billed for the item. In this scenario, the item should not be checked in to clear the claim status. Marking the claim as resolved does not allow the status to be changed either. Perhaps this could be a setting with Claims Return system preferences as to whether staff are permitted to change the claim/lost status of an item from moredetail.pl? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 28618] New: Move t/lib modules to lib/Koha/Test
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '23

16 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28618 Bug ID: 28618 Summary: Move t/lib modules to lib/Koha/Test Change sponsored?: --- Product: Koha Version: master 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 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 29258] New: Add a value builder for filling in the vendor id in the item form
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '23

16 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29258 Bug ID: 29258 Summary: Add a value builder for filling in the vendor id in the item form Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When using the acquisitions module the vendor field in the item form (item.booksellerid) will be filled with the id of the vendor record. Sometimes, there are items that will still be catalogued outside the acquisitions module, like older acquisitions or donations. To not have a mix of "string" vendor names and ids in the item field, it would be nice if we have a value builder/cataloging plugin that allowed to search for vendors and added the id to the form when editing/adding items. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 22820] New: Display 830 series information when there is no 490 tag (MARC21)
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '23

16 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22820 Bug ID: 22820 Summary: Display 830 series information when there is no 490 tag (MARC21) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Currently, the 830 tag will display only when the 490 tag is present and indicator 1=1. It is possible to have a valid 830 tag without a corresponding 490 tag. We need to include logic in the stylesheet to display the 830 when no 490 is found. -- You are receiving this mail because: You are watching all bug changes.

1 22