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

[Bug 30547] New: Plugin for coded data 123p UNIMARC
by bugzilla-daemon＠bugs.koha-community.org 14 Dec '24

14 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30547 Bug ID: 30547 Summary: Plugin for coded data 123p UNIMARC 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 Please, add plugin for coded data 123p UNIMARC $p Planet (Mandatory for planets other than Earth, Not repeatable) $p/0-1 Planet ea Earth ju Jupiter ma Mars me Mercury ne Neptune pl Pluto sa Saturn ur Uranus ve Venus zz Other $p/2 Satellite s The body whose co-ordinates are recorded in subfields $d-$g is a satellite of the planet coded on pos. 0-1. y Not applicable: the body whose co-ordinates are recorded in subfields $d-$g is the planet itself, as coded on pos. 0-1. https://archive.ifla.org/VI/8/unimarc-concise-bibliographic-format-2008.pdf -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 26314] New: "Volumes: show volumes" showing regardless of whether there are volumes linked to the record
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26314 Bug ID: 26314 Summary: "Volumes: show volumes" showing regardless of whether there are volumes linked to the record 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 15851 When cataloguing multi part records with sets and volumes, we currently show a link to "Show volumes" on the set record. The link is always shown on a set record, even if there are no linked volumes. Bug 15851 solves the same issue for analytics. volumes would be a great next step. At the moment Show volumes is only shown on monographs, but we could add the feature for serial records as well. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15851 [Bug 15851] "Analytics: Show analytics" showing regardless of whether they have analytics -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 98

[Bug 20202] New: Link EDI account to Create Edi order
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20202 Bug ID: 20202 Summary: Link EDI account to Create Edi order Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: cunha(a)monterey.org QA Contact: testopia(a)bugs.koha-community.org Currently to send create an EDI order you click "Create EDIFACT order" and are taken to a page to select, if you have multiple EDI accounts, your vendor account from a drop-down menu. It would be great if the Vendor and EDI account could be linked, so there would be no possibility of sending the order to the wrong account. We started with the ByWater beta version of EDI, that was the way it worked in beta. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 29573] New: MARC Framework Subfields Visibility Setting Not Obeyed for 5XX
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29573 Bug ID: 29573 Summary: MARC Framework Subfields Visibility Setting Not Obeyed for 5XX Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jialun(a)toa.edu.my QA Contact: testopia(a)bugs.koha-community.org Created attachment 127988 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=127988&action=e… Tag 583 Subfield constraints I've recently upgraded to version 21.05.05.003 and encountered an issue with the when viewing an item inside the OPAC (opac-detail.pl) while using Normal view inside the Title notes. Our librarians have configured the one of the Subfields for MARC Framework 583 to be hidden in the OPAC but visible for Intranet and Editor. It was working fine in version 20.11 but once we upgraded to version 21.05 it appeared inside the OPAC despite the visibility setting. I've tested changing the Subfields Visibility setting by enabling either OPAC or Intranet only but there was not changes in the OPAC or Staff Client either. The Title Notes were still visible. Thank you in advance for your help! -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 27365] New: Koha doesn't check marcxml field size is < 10000 and fails in various places
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '24

12 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27365 Bug ID: 27365 Summary: Koha doesn't check marcxml field size is < 10000 and fails in various places Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hi ISO standard >The core of the framework is a MARCXML schema that allows lossless round-trip >conversion of an ISO 2709 MARC 21 record and an XML-encoded MARC 21 record. Thus a field size is 9999 bytes max. But /usr/share/perl5/MARC/File/USMARC.pm doesn't care: my $direntry = sprintf( "%03s%04d%05d", $field->tag, $len, $dataend ); and if len >= 10000 it silently creates a bogus directory with a length of 13 rather then 12. These non-conformed marxml will fail in various places. Export, search results list with elasticsearch which store ISO 2709 record in index and use them as data source in results list. eg: Easy to trigger in french UNIMARC with 359 (sorry in french) https://www.transition-bibliographique.fr/wp-content/uploads/2019/02/B359-2… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 55

[Bug 17600] New: Standardize the EXPORT
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '24

11 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17600 Bug ID: 17600 Summary: Standardize the EXPORT Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org On bug 17591 we discovered that there was something weird going on with the way we export and use subroutines/modules. I tried to standardize our EXPORT to use EXPORT_OK only. -- You are receiving this mail because: You are watching all bug changes.

1 215

[Bug 30965] New: Add patron autocomplete search to curbside pickups
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '24

11 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30965 Bug ID: 30965 Summary: Add patron autocomplete search to curbside pickups Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com Depends on: 30578, 30650 So far it's only possible to search for patrons by cardnumber. We should add the regular patron autocomplete search to allow search by surname and firstname. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30578 [Bug 30578] We should drop circ/ysearch.pl in preference to using the REST API's https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30650 [Bug 30650] Convert the Curbside Pickup plugin to Koha core -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 16694] New: Limit SIP2 auth by patron attribute
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '24

10 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16694 Bug ID: 16694 Summary: Limit SIP2 auth by patron attribute Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: magnus(a)libriotech.no Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org In Scandinavia "more open" (Swedish: "Meröppet", Norwegian: "Meråpent") is a hot issue at the moment. What this means is that patrons can use their card and password/PIN to lock themselves into the library even when staff is not around. Typically, this means that patrons can get access to the library building from 7 am to 11 pm, even if the library is only staffed from 8 am to 5 pm. Typically, SIP2 is used to communnicate between the "more open"-system and the ILS, specifically to authenticate the user with a username and password/PIN. Also, you want the ability to turn "more open" access on and off for patrons. An extended patron attribute with possible values of NULL/empty, 0 or 1 should serve well for this. SIP2 does not have a field for saying "this is a moreopen login", so we need a way to identify a SIP2 user as a moreopen user. My plan is to add another attribute to the login element in SIPConfig.xml to achieve this: <login id="koha" password="koha" delimiter="|" error-detect="enabled" institution="kohalibrary" patron-attribute="MEROPPET" /> "MEROPPET" is then the name of an extended patron attribute which can be set to NULL or 0 (patron should not have access to moreopen) or 1 (patron should have access). This should be flexible enough to allow other, similar schemes to use some other patron attribute. -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 25813] New: Enhance patron expiration in SIP display
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '24

09 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25813 Bug ID: 25813 Summary: Enhance patron expiration in SIP display Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 CC: colin.campbell(a)ptfs-europe.com Currently, the patron information returned by SIP only shows "PATRON EXPIRED" when the patron card has expired. This patch makes the display more consistant with the Opac display and also complies with the NotifyBorrowerDeparture system preference. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 30745] New: ES : Search never return result using after-date and/or before-date in labels/label-item-search.pl
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '24

06 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30745 Bug ID: 30745 Summary: ES : Search never return result using after-date and/or before-date in labels/label-item-search.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org With elasticsearch as search engine, using the "after date" or "before date" form elements in labels/label-item-search.pl never return any results. However, searching a specific date of acquisition in the index "Acquisition date" works. Bug 16355 report a similar problem, but there is already a fix and it seems to concern only MARC21. Patch is coming. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 101