September 2023 - Koha-bugs - lists.koha-community.org

[Bug 31424] New: Prompt to change patron messaging if email/SMS absent or changed
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31424 Bug ID: 31424 Summary: Prompt to change patron messaging if email/SMS absent or changed 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: arm(a)hanover.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Suggesting a prompt to staff or patron to update the messaging preferences if a new member is registered with no email/SMS number and the messaging prefs default to 'on', or if an existing user account is edited and the SMS or email contact info is changed. The lack of this reminder leaves many accounts with failed/unsent messages or pending 'print' messages. Also when an email address is added, notices are not sent because staff/patron may not turn on messaging preferences. There are a couple of old bugs about SMS / failed email. This might help with those. Related: 14964 23497 14590 14872 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19098] New: Additional logic for 260/RDA 264 fields
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19098 Bug ID: 19098 Summary: Additional logic for 260/RDA 264 fields 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If we have implemented 10306 and 19096, we can add some additional logic for multiple RDA 264 fields. Making e.g. the place and year picked more accurate than just glueing together or picking the first one. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 23124] New: trailing spaces in DefaultPatronSearchFields can break patron searching
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '23

17 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23124 Bug ID: 23124 Summary: trailing spaces in DefaultPatronSearchFields can break patron searching Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- We should probably just trim this string on save? To recreate: 1 - Add a trailing space to DefaultPatronSearchFields 2 - Attempt to search for patrons 3 - Error! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 21106] New: oai.pl XML output doesn't validate against OAI-PMH XML schema
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '23

16 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21106 Bug ID: 21106 Summary: oai.pl XML output doesn't validate against OAI-PMH XML schema Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 21102 When using some verbs Koha return a well formed but in invalid XML. CLI test: wget -q "https://www.openarchives.org/OAI/2.0/OAI-PMH.xsd" wget -q "https://demo.bibkat.no/cgi-bin/koha/oai.pl?verb=ListSets" -O test.xml xmllint --noout --schema OAI-PMH.xsd test.xml Web test: An online way to test this is with http://validator.oaipmh.com/ 1. verb=ListSets: When no set is defined Koha incorrectly output <ListSets/>. A set (child element of ListSets) should always be there, minOccurs default value is 1. Otherwhise should be: <error code="noSetHierarchy">No sets defined</error>, AFAIK even if tehere is no error. 2. verb=Identify: setDescription is not a string, is descriptionType ##other, "defined by a community" (?) See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17785#c13 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21102 [Bug 21102] OAI-PMH specification conformance [UMBRELLA] -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24407] New: AuthDisplayHierarchies ignores new nodes and needs protection against cyclic relations
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '23

16 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24407 Bug ID: 24407 Summary: AuthDisplayHierarchies ignores new nodes and needs protection against cyclic relations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Suppose I have term A with children B and C where the children have a 550 tag with broader indication to A. If I go to record A, the tree is built showing B and C. If I add a child D to A, the tree for A is not rebuilt but still showing the old situation. A related problem: If I change term A setting it to a be child of B with a 550 (which it obviously not is), this cyclic relation will trigger deep recursion. Resulting in a gateway timeout and a process eating up resources.. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 34919] New: Unimarc 106 182
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '23

16 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34919 Bug ID: 34919 Summary: Unimarc 106 182 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org The search by "physical representation" does not work if the subfields 182 of the Unimarc field are filled in. It works if you fill out 106, but these subfields are outdated. 106 CODED DATA FIELD: TEXTUAL RESOURCE - FORM OF ITEM Field Definition This field contains coded data relating to the form of an item textual unmediated resources (i.e., no mediation device is required to use or perceive the textual content of the resource). Occurrence Optional. Not repeatable. Indicators Indicator 1: blank (not defined) Indicator 2: blank (not defined) Subfield $a Form of resource Item: Coded Data:Medium Designator A one character code indicates the physical medium of the resource item. The following codes are used: d = large print e = newspaper format f = Braille or Moon script g = microprint h = hand-written i = multimedia (e.g. a resource an item in regular print with a microfiche supplement) (obsolete) This code is replaced by field 182 Coded Data Field - Media type, $a/0 code "m"= "multiple media". j = mini-print r = regular print s = electronic (obsolete) This code is replaced by field 182 Coded Data Field - Media type, $a/0 code "b"= "electronic". To be used when resource Item is intended for manipulation by a computer. The resource item may reside in a carrier accessed either directly or remotely, in some cases requiring the use of peripheral devices attached to the computer. This code is not used for items that do not necessarily require the use of a computer (e.g. music compact discs, videodiscs). t = microform (obsolete) This code is replaced by field 182 Coded Data Field - Media type, $a/0 code "c"= "microform". z = other form of material Notes on Field Contents Where the textual material is regular print, the field may contain code 'r' or be omitted altogether. https://cdn.ifla.org/wp-content/uploads/files/assets/uca/unimarc_updates/BI… https://cdn.ifla.org/wp-content/uploads/files/assets/uca/unimarc_updates/BI… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 31794] New: REST API: GET endpoint for Authorities
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '23

15 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31794 Bug ID: 31794 Summary: REST API: GET endpoint for Authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.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 42

[Bug 34413] New: Flat picker birth date field does not display properly on initial load on iOS
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34413 Bug ID: 34413 Summary: Flat picker birth date field does not display properly on initial load on iOS 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If you are using iOS (iPhone for my test), and create a new patron, the birth date field does not show. there is a squishy blob in it's place. Click on that, and the flatpicker comes up and you can enter the date. Everything from that point forward looks fine. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 34857] New: OPAC advanced search operator "not" is searching as "and" after completing an "and" search
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34857 Bug ID: 34857 Summary: OPAC advanced search operator "not" is searching as "and" after completing an "and" search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate in ktd or sandboxes: 1. In the Koha OPAC go to Advanced search and choose "More options". 2. Do a keyword search for "Doctor Who" with an operator of "Not" and a second keyword search of "video". Only 1 search result shows up. 3. Go back to the advanced search using the back arrow (don't click on Advanced search again). 4. Now search for "Doctor Who" with an operator of "And" and a second keyword search of "video". This shows 3 results. 5. Go back again to advanced search using the back arrow. 6. Try the "Not" video search again. The results show the 3 video results that appeared with the "And" operator. They do not show the 1 result that showed with the "Not" operator. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 34624] New: Many header search forms lack for attribute for label
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '23

14 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34624 Bug ID: 34624 Summary: Many header search forms lack for attribute for label Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Keywords: accessibility Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org In the header search forms, we have a label which is associated with the form field, but in many cases the label doesn't have a "for" attribute. This is a problem for HTML validity and for accessibility. -- You are receiving this mail because: You are watching all bug changes.

1 30