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

[Bug 36281] New: Restricted info is displayed even if item is not restricted (OPAC details)
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36281 Bug ID: 36281 Summary: Restricted info is displayed even if item is not restricted (OPAC details) 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: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org If you define a description for restricted = 0 : In OPAC details, restricted info is displayed even if item is not restricted (value 0). -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 36489] New: Making fields 386$m and 386$a visible for the users
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36489 Bug ID: 36489 Summary: Making fields 386$m and 386$a visible for the users Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: piia.semenoff(a)ouka.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 164250 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=164250&action=e… Fields 385$m and 385$a. Could fields 386$m - Demographic group and 386$a - Creator/contributor be shown on the page: cgi-bin/koha/catalogue/detail.pl? as the fields 385$m and 385$a already are shown? The information in the 386 - Creator/Contributor Characteristics -field is currently not visible in any screen other than the MARC-record, but it is useful information for the users. Fields 386$m and 386$a would look on the catalogue-page for example like this: Creator/Contributor Characteristics: Occupation/field of activity: singer-songwriter I attached a picture of how fields 385$m and 385$a are shown on that same page: cgi-bin/koha/catalogue/detail.pl? That is how we would like fields 386$m and 386$a to be shown. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 36450] New: SIP2: Login ignores branchcode in optional CP field
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36450 Bug ID: 36450 Summary: SIP2: Login ignores branchcode in optional CP field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org The spec allows passing a branchcode in the 93 request. Koha just ignores it in MsgType::login_core. Even an unexisting branch can be passed. 9300CNTermNRD02|COtest1234|CPWRONG| 941 The WRONG branch does not exist! Should Koha compare the passed branch with the one recorded in the config? What if there would be no branch in the config? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 30627] New: koha-run-backups may delete the backup files after work done
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30627 Bug ID: 30627 Summary: koha-run-backups may delete the backup files after work done Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: mengu(a)devinim.com.tr QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz I've a doubt about the koha-run-backups script that it deletes its backup files if the backup destination directory is empty. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 23943] New: koha-run-backups --days is misleading
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23943 Bug ID: 23943 Summary: koha-run-backups --days is misleading Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net The documentation for the --days option to koha-run-backups says: --days: the number of days to keep backups around for (default: 2) Sometimes I do the following: 1. Rename a backupfile, e.g. from instance-2019-10-22.sql.gz to instance-2019-10-22-1230.sql.gz 2. Run koha-dump to create a new instance-2019-10-22.sql.gz This reveals that --days does not really care about days at all, just the number of files in the backup dir. This means that if I have adjusted the cronjob to keep backups for 14 days, after the next time it runs, I actually have backups for 13 days. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 36479] New: Z39.50 responder does not support element set / composition "B"
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36479 Bug ID: 36479 Summary: Z39.50 responder does not support element set / composition "B" Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The Z39.50 responder currently has a hard-coded expectation that the element set / composition provided by the client is either blank or "F". It would be handy if it also supported "B" (brief) for backwards compatibility, since the default Zebra configuration also supports "B" (as effective a synonym for "F" (full)). Doing this would avoid a compatibility issue when switching from zebrasrv as the Z39.50 server to the Z39.50 responder for clients that happen to set the element set to "B". In particular, we've seen at least one case where the EBSCO/EDS item availability checker was configured to request "B". The error message associated with this is returning error 239: Unsupported syntax/composition 1.2.840.10003.5.10/B Koha::Z3950Responder::Session::log_error /usr/share/koha/lib/Koha/Z3950Responder/Session.pm (341) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 32465] New: koha-worker debian script missing 'queue' in help
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32465 Bug ID: 32465 Summary: koha-worker debian script missing 'queue' in help Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 27783 There is no mention of the 'queue' parameter in koha-worker --help output Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27783 [Bug 27783] Introduce background job queues -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 36312] New: Koha Z39.50 missing Subject-heading 21
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36312 Bug ID: 36312 Summary: Koha Z39.50 missing Subject-heading 21 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you do a 1=21 (ie Subject-heading) Z39.50 search against Koha's authority database, you won't get a result. There's a few reasons for this. If using Zebra: - /etc/koha/zebradb/authorities/etc/bib1.att is missing a line like “att 21 Subject-heading” - /etc/koha/zebradb/marc_defs/marc21/authorities/authority-zebra-indexdefs.xsl isn’t indexing the 150 field into the “Subject-heading” index If using z3950_responder.pl with Elastic, ./etc/z3950/attribute_mappings.yaml doesn't have an appropriate mapping. At a glance, I don't see a subject specific index for subject authorities either in ./admin/searchengine/elasticsearch/mappings.yaml If using z3950_responder.pl with Zebra, then it's the same problem as if you were just using Zebra. -- At the moment, I'm concerned with Zebra, but I'll want to look at Elastic at some point... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 33080] New: Add helpers that return result_set for further processing
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '24

01 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33080 Bug ID: 33080 Summary: Add helpers that return result_set for further processing Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: agustinmoyano(a)theke.io CC: tomascohen(a)gmail.com Add "search_rs" and "find_rs" helpers to REST API, which retrieves a result set with all search queries and attributes applied. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53

[Bug 36478] New: add title field to documents OR allow file description with no upload
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '24

01 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36478 Bug ID: 36478 Summary: add title field to documents OR allow file description with no upload Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: billieanne.gebb(a)frontier.edu CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com In the documents section, you might want to reference documents in a physical location that have not actually been uploaded. If no file is uploaded, there's no description for the document, so only the other fields show. It would be helpful to have a title or a document description even when there is no file being uploaded. -- You are receiving this mail because: You are watching all bug changes.

1 0