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

[Bug 24115] New: patron import tool should have option to not overwrite specific fields
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '22

02 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24115 Bug ID: 24115 Summary: patron import tool should have option to not overwrite specific fields Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: jeremy.evans(a)phe.gov.uk QA Contact: testopia(a)bugs.koha-community.org Following a test load of users exported from our active directory using the import users tool (Koha 18.11) we have encountered a few issues. The default settings specified for the load are being applied to also overwrite existing users. For example, all users now have the same profile and home library. We would wish to have the option for the default settings to only apply for new users created and for example retain the current user profile and home library for existing users. These 2 fields would not be included in the file loaded to Koha from the Active directory. There are other fields such as the email address, expiry date, address, etc where we do want the load to overwrite the existing records to keep these up to date in Koha. Probably another tick box next to each of the fields listed for the default settings to only apply to new records would make it flexible to retain specific fields whilst allowing others to be updated As a minimum this should apply to user profile and home library. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 24279] New: Claims Returned does not work when set from moredetail.pl or additem.pl
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '22

02 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24279 Bug ID: 24279 Summary: Claims Returned does not work when set from moredetail.pl or additem.pl 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To test: - configure claims returned per bug 14697 - Check an item out to a patron - Go to either moredetail.pl or additem.pl and set the item to your claims returned lost value - observe that the item has followed normal lost behavior rather than claims returned behavior We see two options to fix this, either: - Hide the claims returned lost value from moredetail.pl and additem.pl OR - Make Koha follows claims returned process regardless of how the item is set to that claims returned lost value -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 58

[Bug 27189] New: Unable to delete patron
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '22

02 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27189 Bug ID: 27189 Summary: Unable to delete patron Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nishathahmed(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 114306 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=114306&action=e… Koha-anon-info Hi There! I couldn't delete patrons it says "Unable to delete patron that is set as AnonymousPatron This patron cannot be deleted while set as AnonymousPatron in the system preferences." I set an account with borrower-number (which is superlibrarian account and not meant for deletion) as well there on system preferences. Please check the attachment. But still no luck. Please advice. Regards! Nishath -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 18683] New: biblioitems.marcxml does not match MARC21slim.xsd
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '21

30 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18683 Bug ID: 18683 Summary: biblioitems.marcxml does not match MARC21slim.xsd Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: mail(a)casi.pw QA Contact: testopia(a)bugs.koha-community.org I found the following record in a Koha installation that I manage, running on a Debian server. ---- <record xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd" xmlns="http://www.loc.gov/MARC21/slim"> <leader>[...]</leader> <datafield tag="999" ind1=" " ind2=" "> <subfield code="c">[...]</subfield> <subfield code="d">[...]</subfield> </datafield> <controlfield tag="001">[...]</controlfield> [...] ---- This does not comply with the MARC21slim.xsd Schema definition, which says: <xsd:complexType name="recordType" id="record.ct"> <xsd:sequence minOccurs="0"> <xsd:element name="leader" type="leaderFieldType"/> <xsd:element name="controlfield" type="controlFieldType" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="datafield" type="dataFieldType" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> <xsd:attribute name="type" type="recordTypeType" use="optional"/> <xsd:attribute name="id" type="idDataType" use="optional"/> </xsd:complexType> These malformed xml strings were created by Koha over the time. To localize the errors, I ran a SQL query on the database. > select timestamp from biblioitems where marcxml like "%<datafield tag=\"999\"%<controlfield%" order by timestamp gives 962 rows, since 24th of October 2016 Some of the marcxml fields even contain the field 999 a second time, at the end. > select timestamp from biblioitems where marcxml like "%<datafield tag=\"999\"%<controlfield%<datafield tag=\"999\"%" order by timestamp gives 509 rows, since 4th of January 2017 -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 25971] New: Allow arbitrary database field as runtime parameter
by bugzilla-daemon＠bugs.koha-community.org 23 Dec '21

23 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25971 Bug ID: 25971 Summary: Allow arbitrary database field as runtime parameter Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Yet another runtime parameter idea, how about allowing a syntax like "SELECT * from accountlines WHERE debit_type_code like <<Pick a code|account_debit_types.code>>" So Koha then builds the parameter list based on a "select distinct code from account_debit_types" To make it even nicer, we could allow "<<Pick a code|account_debit_types.code:account_debit_types.description>>" so we use the code as our value but display the corresponding description. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 23793] New: Add an EmbedItems RecordProcessor filter for MARC::Record objects
by bugzilla-daemon＠bugs.koha-community.org 23 Dec '21

23 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23793 Bug ID: 23793 Summary: Add an EmbedItems RecordProcessor filter for MARC::Record objects 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org This should help reduce the current overhead, and by using the features introduced by bug 22454, probably give a performance boost. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 22544] New: Move C4:.NewsChannels to Koha namespace
by bugzilla-daemon＠bugs.koha-community.org 23 Dec '21

23 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22544 Bug ID: 22544 Summary: Move C4:.NewsChannels to Koha namespace Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 263

[Bug 28481] New: Register details "Older transactions" search does not include the selected day in the "To" field in date range
by bugzilla-daemon＠bugs.koha-community.org 23 Dec '21

23 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28481 Bug ID: 28481 Summary: Register details "Older transactions" search does not include the selected day in the "To" field in date range Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When searching for older transactions, the To field should include the current day. Test Plan: 1) Sell an item 2) Cash up to make the sale historical 3) Search "Older transactions" with both dates being the current date, click "Display" to search 4) Note you get no results 5) Set "To" to tomorrow, click "Display" again 6) You should now see your transaction -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 25946] New: borrowerRelationship can no longer be empty
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25946 Bug ID: 25946 Summary: borrowerRelationship can no longer be empty Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: alex.arnaud(a)biblibre.com, andrew(a)bywatersolutions.com, david.roberts(a)ptfs-europe.com, gmcharlt(a)gmail.com, hc(a)interleaf.ie, jonathan.druart(a)bugs.koha-community.org, kyle.m.hall(a)gmail.com, martin.renvoize(a)ptfs-europe.com, nugged(a)gmail.com, stalkernoid(a)gmail.com Depends on: 25322 Since Bug 25322 it is not possible to have an empty borrowerRelationship system preference. The empty relationship dropdown is treated as mandatory. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25322 [Bug 25322] Adding a guarantor with no relationship defaults to first available relationship name -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 28279] New: mappings.yaml no longer in sync
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28279 Bug ID: 28279 Summary: mappings.yaml no longer in sync Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: System Administration Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 19482, 27316, 20589, 25325 We are missing some changes in the mappings.yaml file: * missing staff_client/opac (bug 25325 and bug 20589) * missing mandatory (bug 19482) * sort (bug 27316) became a boolean field Which means export_elasticsearch_mappings.pl generates a file that differs a lot from the one we have in our codebase. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19482 [Bug 19482] Elasticsearch - prevent removal / editing of required indexes https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20589 [Bug 20589] Add field boosting and use elastic query fields parameter instead of deprecated _all https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25325 [Bug 25325] ElasticSearch mapping export lacks staff_client/opac fields https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27316 [Bug 27316] In mappings use yes/no for sortable -- You are receiving this mail because: You are watching all bug changes.

1 11