March 2022 - Koha-bugs - lists.koha-community.org

[Bug 30142] New: ElasticSearch MARC mappings should not accept whitespaces
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '22

25 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30142 Bug ID: 30142 Summary: ElasticSearch MARC mappings should not accept whitespaces Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at We had a "funny" bug today, because I updated some ElasticSearch Biblio MARC mappings, and entered "245bn " instead of "245bn" (notice the trailing space?) The Form accepted the invalid value, but after any edit to a biblio we'd get a 500 Error, with this (not very helpful) error message in plack-error.log "Invalid MARC field expression: 245bn " After spotting this, it was easy to fix the typo, but I think that the form should either be stricter when validating input or at least remove whitespace from the MARC input (AFAIK whitesapce is not allowed here). There is a TODO marker in admin/searchengine/elasticsearch/mappings.pl#161 which is probably related :-) I will submit a patch in a minute that will at least remove all whitespaces. Actually checking the format should not be too hard with some regex, but I'm not sure if the format is specified anywhere, and in the DB I see quite different values ("440a", "111(abcd)", "008_/14", "leader_/0-4", ...) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 30118] New: holds_block_checkin behavior is different in Koha and in SIP
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '22

25 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30118 Bug ID: 30118 Summary: holds_block_checkin behavior is different in Koha and in SIP Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In koha interface, a warning is displayed when an item on hold is returned only if the return is for this specific item. We should have the same behavior in SIP, for consistency. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 30426] New: suggestion service missing Auth and Output imports
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '22

25 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30426 Bug ID: 30426 Summary: suggestion service missing Auth and Output imports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org While most scripts have been updated to import specific functions from C4::Auth and C4::Output, /opac/svc/suggestion missed those, which means calls to it generate 500 errors. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 30159] New: Fix display of validation of important fields when biblio cataloguing
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '22

25 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30159 Bug ID: 30159 Summary: Fix display of validation of important fields when biblio cataloguing 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 131029 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131029&action=e… Popup box showing HTML dump of validation for important fields Fields that are marked as important in a biblio framework will trigger a confirmation box to the cataloguer if not filled, asking if they would still like to save. Since Bug 28694, the validation for mandatory fields is nice and pretty, but it appears the validation for important fields was not tested. The confirmation pop-up now spits out the HTML markup and is unreadable. This should be fixed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 29787] New: Add plugin version to plugin search results
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '22

25 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29787 Bug ID: 29787 Summary: Add plugin version to plugin search results Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When you search for a plugin it doesn't tell which version it is going to install. Additionally, it would be great if instead of just an 'install' button, they mutated to 'upgrade' or 'reinstall' if that applies. Otherwise you don't know what's going on. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 30402] New: Authority import hanging when replacing matched record
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '22

25 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30402 Bug ID: 30402 Summary: Authority import hanging when replacing matched record 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org We've discovered a bug with the MARC staged management. When staging an authority record, we're applying a matching rule so that it should REPLACE a matched record. When trying to import, it hangs on 0% and never progresses or succeeds. This does not happen with ignoring or adding, only replacing. This does not happen with biblios but does with authorities. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 29704] New: Holds reminder emails should allow configuration for a specific number of days
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '22

25 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29704 Bug ID: 29704 Summary: Holds reminder emails should allow configuration for a specific number of days Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 The holds reminder email cron takes a DAYS value and sends reminders to all patrons with holds waiting more than that number of days. Currently, once a hold passes the number of DAYS specified in the cron, the patron gets a reminder on EVERY run of the cron going forward. We should also provide an option to send reminder emails only for holds that have been waiting EXACTLY that many days. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 20123] New: Allow multiple instances of Koha to have different timezones on the same server
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '22

25 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20123 Bug ID: 20123 Summary: Allow multiple instances of Koha to have different timezones on the same server 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Most of Koha depends on the local timezone of the server, except for Koha::Database which support an ENV override with the key TZ. We should take this a step further. We should not only accept the TZ environment variable for all of Koha, we should really be able to set the timezone in the koha conf file as well so we don't have to pass that environment variable to things like cronjobs and one-off scripts. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 64

[Bug 26839] New: Add a 'date published' feature to the facets
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '22

25 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26839 Bug ID: 26839 Summary: Add a 'date published' feature to the facets Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org Add a 'date published' facet to the OPAC so that patrons can limit their search results. For example: 2021 (2) 2020 (9) 2019 (14) -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 29135] New: OAI should not include biblionumbers from deleteditems when determining deletedbiblios
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '22

23 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29135 Bug ID: 29135 Summary: OAI should not include biblionumbers from deleteditems when determining deletedbiblios Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major 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 When including items in OAI we add the biblionumbers of deleted items into the deleted list This is from this line: 93 if ( $include_items ) { 94 $sql = "($sql) UNION (SELECT DISTINCT(biblionumber) FROM deleteditems $criteria)"; 95 push @bind_params, @part_bind_params; This is wrong because deletion of a single item does not indicate a record is deleted To recreate: 1 - Create /var/lib/koha/kohadev/OAI.yaml with: format: marcxml: metadataPrefix: marcxml metadataNamespace: http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim schema: http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd include_items: 1 2 - Set OAI-PMH:ConfFile to '/var/lib/koha/kohadev/OAI.yaml' 3 - Delete an item from a record 4 - View the page: http://localhost:8080/cgi-bin/koha/oai.pl?verb=ListRecords&metadataPrefix=m… 5 - Note the record is now listed as deleted -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36