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

[Bug 25362] New: Code to create CGISESSID shoudl be in function
by bugzilla-daemon＠bugs.koha-community.org 03 Jul '25

03 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25362 Bug ID: 25362 Summary: Code to create CGISESSID shoudl be in function 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org I found 12 difference instances where we create the CGISESSID cookie, and each one has its own invocation that needs to be updated when you want to change that cookie. It would be better if we wrapped the cookie creation in a function. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 36987] New: Add preference for which fields to prefill when copying a patron
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '25

02 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36987 Bug ID: 36987 Summary: Add preference for which fields to prefill when copying a patron 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: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Similar to PrefillGuaranteeField it would be great to be able to set which fields prefill when duplicating patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 24097] New: Don't show claims tab in patron account, when there are no claims
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '25

02 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24097 Bug ID: 24097 Summary: Don't show claims tab in patron account, when there are no claims Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Not every library will want to use this feature - I think it would be nicer if we didn't show the tab when there are no claims, so this is a bit more 'invisible'. It also matches how we handle other tabs. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 26472] New: Elasticsearch - ES - Authority record results not ordered correctly due to punctuation marks
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '25

02 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26472 Bug ID: 26472 Summary: Elasticsearch - ES - Authority record results not ordered correctly due to punctuation marks Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: heather_hernandez(a)nps.gov When searching authorities, the results are grouped by punctuation, e.g.: Word (Word) Word Word Word-Word Word, Word For example: Saint (Fictitious... Saint Charles School Saint Hilaire Institute Saint Patrick Club Saint-Nazaire (France) Saint-Pierre (Martinique) Saint, Eva Marie Saint, Joseph But it should sort like this: Saint Charles School Saint, Eva Marie Saint (Fictitious... Saint Hilaire Institute Saint Patrick Club Saint-Nazaire (France) Saint-Pierre (Martinique) There is documentation of this filing order in _Library of Congress Filing Rules_ which can be freely accessed here: https://babel.hathitrust.org/cgi/pt?id=mdp.39015022080140&view=1up&seq=3 Especially in section 1, General Filing Order: ---Begin quote: Fields in a filing entry are arranged word by word, and words are arranged character by character. This procedure is continued until one of the following occurs: a. A prescribed filing position is reached. b. The field comes to an end (in which case placement is determined by another field of the entry or by applying one of the rules given hereafter). c. A mark of punctuation indicating a subarrangement is encountered. 1.1. Order of Letters Letters are arranged according to the order of the English alphabet (A-Z). Upper and lower case letters have equal filing value. 1.1.1. Modified Letters Modified letters are treated like their plain equivalents in the English alphabet. Thus all diacritical marks and modifications of recognizable English letters are treated as if they did not exist; e.g., ä, á, å, ł , ñ, ø are filed as a, 1, n, o. The treatment of special letters that cannot be readily equated with English letters is described in Rule 17. Example Hand blows Hand book for Prospect Park Hand in glove Håndbok for sangere Handbook for adventure Hände am Pflug Hands on the past Haṇḍu [Indic surname] 1.2. Placement of Numerals Numbers expressed in digits or other notation (e.g., roman numerals) precede letters and, with few exceptions, they are arranged according to their numerical value. According to this rule, all filing entries beginning with numerals appear before entries beginning with the letter A. Numbers expressed as words are filed alphabetically. Detailed instructions for filing numerals are given in Rule 16. Example 1, 2, 3, and more 1, 2, buckle my shoe 3 died variously 10 ways to become rich 13 jolly saints 112 Elm Street 838 ways to amuse a child 1000 spare time money making ideas 1984 10,000 trade names 1,000,000 delinquents A is for anatomy A4D desert speed run Aa, Abraham Henry II Henry 3 Henry VIII and his six wives Henry Street Settlement, New York Henry the Fourth, part two Longitude 30 west Longitude and time Nineteen eighty-four Oberlin College one, two, three for fun Rubinstein, Moshe F. Ten thousand miles on a bicycle Three 14th century English mystics Three by Tey Thucydides 1.3. Signs and Symbols Nonalphabetic signs and symbols within a field are generally ignored in filing and the remaining letters or numerals are used as the basis of arrangement (see also Rule 18). 1.3.1. Punctuation Punctuation as such has no place in the collating sequence of characters considered in filing arrangement. A mark of punctuation is taken into account, however, in two situations: 1) when it signals the end of an element or field and indicates the need for subarrangement as described in the following rules; and 2) when it serves as the sole separator between two discrete words (e.g., Mott-Smith; 1951/1952; 1:3) and so must be treated as equivalent to a space. The second situation dictates that a hyphen will always be treated as a space (see also Rules 12 and 16). ---End quote -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 64

[Bug 21357] New: Filter elisions from index and search terms in Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '25

02 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21357 Bug ID: 21357 Summary: Filter elisions from index and search terms in Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: ere.maijala(a)helsinki.fi To make searching easier at least in French, it would be nice to have the default configuration handle elisions properly (e.g. l'avion). Coming up with a proposed patch. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 104

[Bug 34365] New: Hold cancellation request workflow cannot be triggered on API
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '25

02 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34365 Bug ID: 34365 Summary: Hold cancellation request workflow cannot be triggered on API Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com CC: tomascohen(a)gmail.com Rigth now the `DELETE /holds/:holds` route does a straight-cancellation of the hold. It should be possible to trigger the hold cancellation request workflow so thrid-party systems can use it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 36679] New: anonymous patron is not blocked from checkout via self check
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '25

02 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36679 Bug ID: 36679 Summary: anonymous patron is not blocked from checkout via self check Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org The anonymous patron is not allowed to checkout through the staff module, but it appears that you can login as this user on the self check and check out items. While it is more likely this could be exploited with a random library card number, this does create a hole in blocking circ on this account. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 37104] New: Block AnonymousPatron from logging into anything
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '25

02 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37104 Bug ID: 37104 Summary: Block AnonymousPatron from logging into anything Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org In Bug 36679 we blocked the AnonymousPatron from logging into SCO. The AnonymousPatron should not log in to anything, staff interface/OPAC/SCO. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 32441] New: Localuse is recorded in statistics but not recreated in pseudonymized_transactions
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32441 Bug ID: 32441 Summary: Localuse is recorded in statistics but not recreated in pseudonymized_transactions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The pseudonymization feature creates a parallel to the statistics table without identifiable patron data. This allows one to then use cleanup_database to delete old entries in statistics to remove that patron data. However, the statistics table also contains records of local use. That data only exists in statistics. It is not duplicated in pseudonymized_transactions, and so is lost if statistics are deleted using cleanup_database. Bug 32440 suggests teaching cleanup_database to not delete localuse entries. This bug suggests putting localuse entries into pseudonymized_transactions, even though no patron is involved. That's a bit illogical, but has the benefit of keeping all of this data together. Meanwhile, Bug 16122 suggesting keeping a local use count in the item record. That would alleviate this issue somewhat, but specific transactional data would be preferable to a running count. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24841] New: REST API should check if patron is restricted/debarred
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24841 Bug ID: 24841 Summary: REST API should check if patron is restricted/debarred Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no Bug 17247 "ILS-DI HoldTitle and HoldItem should check if patron is restricted" adds checks to see if the patron is restricted before a hold is placed. These checks are added to C4::ILSDI::Services::HoldItem() and C4::ILSDI::Services::HoldTitle(). As far as I can tell, the same checks are missing from the REST API, specifically for "POST /api/v1/holds". Koha::REST::V1::Holds::add() does call C4::Reserves::CanItemBeReserved() and C4::Reserves::CanBookBeReserved(), but as far as I can tell, those subs do not check if the patron in question is debarred. Am I missing something or is this a bug? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15