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

[Bug 15278] [Omnibus] Port default slips and notices from bespoke syntax to Template Toolkit
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '24

16 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15278 Emily Lamancusa <emily.lamancusa(a)montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |36608 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36608 [Bug 36608] Port default TO_PROCESS and AVAILABLE notices to Template Toolkit syntax -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 36602] New: Locked account requires a password change
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '24

15 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36602 Bug ID: 36602 Summary: Locked account requires a password change Change sponsored?: --- Product: Koha Version: 23.05 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 It doesn't make sense that a password change is required for a locked account. Accounts are locked because someone has attempted to log into the account multiple times and has failed the threshold. This means that someone knows the account username, but doesn't know the password. If the threshold is not a low number, it is likely someone is trying to gain access to the account that should (especially if they don't use a forgot password method. It seems that the more logical approach is to require a card number and/or username change. I guess it is possible that it could be the patron/user and they are just really bad at password recovery, and persistent, but I'm still not convinced this is the most logical response to being locked out. A change in username would be more likely to thwart abusive users. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 15504] Track Patron's Last Activity
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '24

15 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=33997 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2894] Routing list holds are broken
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '24

15 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2894 Jonathan Druart <jonathan.druart(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Patch doesn't apply |Needs Signoff --- Comment #18 from Jonathan Druart <jonathan.druart(a)gmail.com> --- Sorry I totally forgot about this one. I had a very quick short at rebasing it but haven't tested it! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2894] Routing list holds are broken
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '24

15 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2894 Jonathan Druart <jonathan.druart(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #138971|0 |1 is obsolete| | --- Comment #17 from Jonathan Druart <jonathan.druart(a)gmail.com> --- Created attachment 164892 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=164892&action=e… Bug 2894: Fix Routing list holds This is a try to fix a very old bug. Not familiar with the workflow so cannot confirm it will fix everything. The idea is to fix the behaviour of RoutingListAddReserves, and create item-level holds (so only if items have been created). -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 36601] New: When creating guarantee card from the guarantor’s account can it default to the guarantor’s category?
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '24

15 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36601 Bug ID: 36601 Summary: When creating guarantee card from the guarantor’s account can it default to the guarantor’s category? Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: pwashkevich(a)sjcfl.us QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When creating a guarantee card off of the guarantor’s account (click add guarantee instead of duplicate), the category setting is defaulting to 1 year nonresident. Can it be changed to default to the guarantor’s category? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 20065] New: perennial identifier implementation
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '24

15 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20065 Bug ID: 20065 Summary: perennial identifier implementation Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: fcouffignal(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 70804 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=70804&action=ed… example Add a system preference ? or a plugin ? ... to have perennial identifier in Koha -> object : choice between ARK, DOI, Handle, PURL (Marc bibliographic data) -> contributor : arkXiv, idHAL, IDRef, ISNI (Marc Authority data) see more : http://www.inist.fr/?Identifiants-perennes http://www.mediathequederoubaix.fr/ -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 21102] New: OAI-PMH specification conformance [UMBRELLA]
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '24

15 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21102 Bug ID: 21102 Summary: OAI-PMH specification conformance [UMBRELLA] Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Currently, Koha fails various validation tests on the OAI-PMH implementation. [1] This umbrella bug will ease finding OAI-PMH implementation issues. [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17785#c13 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 36436] New: Error creating biblio when using ElasticSearch
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '24

15 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36436 Bug ID: 36436 Summary: Error creating biblio when using ElasticSearch Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: vanoudt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We've run into an issue where attempting to create new biblios while using ElasticSearch. (Zebra works fine). A bit of troubleshooting finds that it is failing in C4::Biblio in the LinkBibHeadingsToAuthorities function. The logs warn: Exception 'Koha::Exceptions::Elasticsearch::BadResponse' thrown 'Bad response received when submitting request to Elasticsearch' with details => [http://localhost:9200]-[400] [action_request_validation_exception] Validation Failed: 1: type is missing;, type => Request I'm a bit out of my depth here; does anyone have any suggestions? For now, I've headed back to Zebra, but would rather stay with ElasticSearch! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 36048] New: Error actual cost format in receipt summary
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '24

14 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36048 Bug ID: 36048 Summary: Error actual cost format in receipt summary Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: mirjam.vantieghem(a)etf.edu QA Contact: testopia(a)bugs.koha-community.org Since 23.11, when receiving an order, in the receipt summary pop-up screen, when clicking in the field 'Actual cost' and then in another field, it gives the error "Please add amount in valid format: 0.00". We have system preference CurrencyFormat set to "360 000,00 (FR)". In the previous Koha versions the "Retail price" and "Budgeted cost" were formatted that way, but the "Replacement price" and "Actual cost" had a dot for the decimals (US formatting). Now all amounts are formatted according to the system preference, which is a good improvement, but we get an error saying it should be formatted according to the US formatting system. Regardless of which format we use, when confirming the receipt, the amount is saved in the correct format and there do not seem to be any issues. Still, the error is confusing and should not appear. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2