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

[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 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

[Bug 23178] New: If all items are marked 'not for loan' staff results displays 'None available'
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '23

13 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23178 Bug ID: 23178 Summary: If all items are marked 'not for loan' staff results displays 'None available' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- If all items on a record are marked not for loan on the item or by item type configuration, the result list displays: None available. This is not quite true. Usually in Koha 'available' is used to indicate the item ins on the shelf, 'available for loan' or 'not available for loan' would indicate that the items are there, but cannot be checked out. I think changing it to 'none available for loan' would be more accurate here. Or alternatively: Treat them separately and use "x availble for reference" similar to the result list in the OPAC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 20108] New: Hold Queue Timeout
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '23

13 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20108 Bug ID: 20108 Summary: Hold Queue Timeout 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be good if there were a preference to set a Hold Queue Timeout, where a hold request goes to a branch queue for X amount of days, and if it isn't filled, it goes to the next library queue according to the cost matrix, etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 15708] New: Add ability to allow only items whose home/holding branch matches one of a group of libraries to fill a given hold
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '23

12 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15708 Bug ID: 15708 Summary: Add ability to allow only items whose home/holding branch matches one of a group of libraries to fill a given hold 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This enhancement will extend the functionality added in Bug 15532 using the library groups editor in Bug 15707 to allow not only holds from a single library match but a group of libraries that match. This will give much greater flexibility in defining what items should full what holds within a groups of libraries. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 22284] New: hiding libraries outside group for holds dev
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '23

12 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22284 Bug ID: 22284 Summary: hiding libraries outside group for holds dev Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: nick(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- hiding libraries outside group for holds dev -- You are receiving this mail because: You are watching all bug changes.

1 472

[Bug 16436] New: Allow action logs to be logged to the koha log file
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '23

11 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16436 Bug ID: 16436 Summary: Allow action logs to be logged to the koha log file Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be very useful if it were possible to log actions to a log file as well as to the database. With Koha::Logger we can give the option of sending those logs to a separate file, but by default they can go to the standard log files. They should also be off by default. -- You are receiving this mail because: You are watching all bug changes.

1 22