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

[Bug 18533] New: MARC::Record->encoding does not handle UNIMARC records
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18533 Bug ID: 18533 Summary: MARC::Record->encoding does not handle UNIMARC records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 18152 Regarding bug 18152 MARC::Record->encoding should not be called directly from our codebase. C4::Charset::SetMarcUnicodeFlag should call MARC::Record->encoding for MARC21 and NORMARC but does the UNIMARC trick for UNIMARC records. It seems that MARC::Record->encoding calls should be replaced with C4::Charset::SetMarcUnicodeFlag everywhere. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18152 [Bug 18152] UNIMARC bib records imported with invalid 'a' char in label pos.9 -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 32906] New: Make 'Replace record via Z3950/SRU' buttons in authorities work consistently
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32906 Bug ID: 32906 Summary: Make 'Replace record via Z3950/SRU' buttons in authorities work consistently Change sponsored?: --- Product: Koha Version: unspecified 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 29173 Bug 29173 implemented search pre-fill for the Replace via Z3950 search form from the authority detail page, but it did so in a very different, and MARC21 specific, way from the same button on the 'Edit authority' page. On the edit authority page we extract the pre-fill terms from the current page and pass them as URI parameters to the search pop-over form. I think we could take a similar approach on the detail display page and perhaps even make the feature work for both MARC21 and UNIMARC in this way? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29173 [Bug 29173] Button "replace authority record via Z39/50/SRU" doesn't pre-fill -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 32920] New: ES indexer should gracefully handle a bad bib record when reindexing after a batch modification
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32920 Bug ID: 32920 Summary: ES indexer should gracefully handle a bad bib record when reindexing after a batch modification 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: emily.lamancusa(a)montgomerycountymd.gov When Elasticsearch reindexes after a batch modification, if one of the modified biblio records contains invalid data, the "Update Elasticsearch Index" job will fail without updating the search indexing for any of the modified records. When reindexing multiple records at once, an error with one record should not prevent the others from being reindexed correctly. To reproduce: 1. Set SearchEngine system preference to 'Elasticsearch' 2. Find or produce a biblio record that contains invalid data (in KTD's sample data, biblionumber 369 works for this) 3. Confirm that the biblio record detail page in the staff interface displays an invalid data error 4. Generate a barcode file that includes items attached to this biblio as well as other items 5. Perform a batch item modification 6. Open the job list. Note "Finished" status for batch item mod job, and "Failed" status for Update Elasticsearch index job 7. Find the modified records via catalog search. Note that none of the modified items display the updated information in the catalog search. I reproduced this error on KTD, by doing a batch edit on all items with publication date 198_ In case it's useful, error message from the failed job: ^ at /kohadevbox/koha/Koha/Biblio/Metadata.pm line 114. DEBUG - Update of elastic index failed with: Invalid data, cannot decode metadata object (biblio_metadata.id=368, biblionumber=369, format=marcxml, schema=MARC21, decoding_error=':8: parser error : PCDATA invalid Char value 31 <controlfield tag="001">00aD000015937</controlfield> ^ :9: parser error : PCDATA invalid Char value 31 <controlfield tag="004">00satmrnu0</controlfield> ^ :9: parser error : PCDATA invalid Char value 31 <controlfield tag="004">00satmrnu0</controlfield> ^ :9: parser error : PCDATA invalid Char value 31 <controlfield tag="004">00satmrnu0</controlfield> ^ :9: parser error : PCDATA invalid Char value 31 <controlfield tag="004">00satmrnu0</controlfield> ^ :10: parser error : PCDATA invalid Char value 31 <controlfield tag="008">00ar19881981bdkldan</controlfield> ^ :10: parser error : PCDATA invalid Char value 31 <controlfield tag="008">00ar19881981bdkldan</controlfield> ^ :10: parser error : PCDATA invalid Char value 31 <controlfield tag="008">00ar19881981bdkldan</controlfield> ^') -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 32048] New: Calendar adding holidays repeated
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '24

06 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32048 Bug ID: 32048 Summary: Calendar adding holidays repeated Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It seems something is getting cached when adding holidays To recreate: 1 - Enter a holiday repeated yearly on a range from the 1st of the month to the 5th 2 - Delete it 3 - Add a new holiday from the 20th to the 25th 4 - When saved, the holiday from the 1st to the 5th is also added again -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 23758] New: Advanced editor should have a widget to automatically populate when a biblio was first entered
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '24

06 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23758 Bug ID: 23758 Summary: Advanced editor should have a widget to automatically populate when a biblio was first entered Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: hayleymapley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be useful for libraries who use the Advanced Editor to have the ability to automatically populate a field with the current date the first time a biblio record is entered. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 28642] New: Add IndependentBranches syspref to hide other items and libraries
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '24

05 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28642 Bug ID: 28642 Summary: Add IndependentBranches syspref to hide other items and libraries Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: michael.hafen(a)washk12.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Independent Branches should not see items from other libraries in the staff client. Also don't show other libraries in the many library selects. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 28082] New: Add acquisitions toolbar to vendors on vendor search page
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '24

01 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28082 Bug ID: 28082 Summary: Add acquisitions toolbar to vendors on vendor search page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org We can improve consistency and expand functionality be adding inclusion of the acquisitions toolbar include on the vendor search results page. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 31208] New: "Check for embedded item record data" should default to "No"
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '24

01 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31208 Bug ID: 31208 Summary: "Check for embedded item record data" should default to "No" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, "Check for embedded item record data" in stage-marc-import.pl defaults to "Yes", but I doubt that the majority of libraries would want to check for embedded item record data. (By extension, I think it would be good to default "How to process items:" to "Ignore items" instead of "Always add items" - just to be on the safe side.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 31755] New: Store biblio OPAC visibility in biblio table
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '24

01 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31755 Bug ID: 31755 Summary: Store biblio OPAC visibility in biblio table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, you have to interrogate the MARCXML to determine if a record is suppressed using OpacSuppression, and you have to iterate through all of a bib's items to see if it's hidden/suppressed using OpacHiddenItems and OpacHiddenItemsHidesRecord. As Tomas said at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31161#c21, it would make sense to have a "suppressed" field in the biblio table so that we can determine a biblio record's OPAC visibility using a simple SQL query. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 26168] New: Create admin Linux user "koha" which is member of all *-koha instance groups
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '24

01 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26168 Bug ID: 26168 Summary: Create admin Linux user "koha" which is member of all *-koha instance groups Change sponsored?: --- Product: Koha Version: unspecified 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 It would be useful to have an administrative Linux user "koha" which is a member of all *-koha instance groups. The high level use case is a non-root (daemon) service that can run "koha-shell kohadev -c 'command'". At the moment, you could just run that (daemon) service as root, but ideally it would be better to run it as a less privileged user. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1