November 2017 - Koha-bugs - lists.koha-community.org

[Bug 15723] New: Add preview marc in authority results authorities-home.pl
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15723 Bug ID: 15723 Summary: Add preview marc in authority results authorities-home.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 47560 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=47560&action=ed… authority search Hi, In a results list of authorities , it would be great to have a Marc preview of each notice. We could then check quickly the authorities to merge. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[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 19482] New: Elasticsearch - prevent removal / editing of required indexes
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '21

22 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19482 Bug ID: 19482 Summary: Elasticsearch - prevent removal / editing of required indexes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Sorting options are currently hardcoded, in view of future z39 support with ES and other interfaces it is probably best to provide a base set of fields that are indexed and sortable. Using the base set of sorting this patchset will prevent editing/removal of these fields by default -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 106

[Bug 15749] New: Add library menu to OPAC header
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '21

17 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15749 Bug ID: 15749 Summary: Add library menu to OPAC header Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: chad(a)pennmanor.net QA Contact: testopia(a)bugs.koha-community.org Our librarians requested the ability to search a specific library from the opac without requiring a patron to login or setup filters. We have a number of young patrons and the current process is rather cumbersome. I have some code that creates a Library menu in the opac header. It allows for an anonymous patron to select a library from the menu and have their search results automatically filtered. I have been working with Kyle Hall and the rest of the ByWater team to cleanup some of our modifications for potential inclusion upstream. A patch is coming... -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 17269] New: Library::CallNumber:: LC does not follow LC standards for Area Subarrangments of cataloged maps
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '21

06 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17269 Bug ID: 17269 Summary: Library::CallNumber::LC does not follow LC standards for Area Subarrangments of cataloged maps Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Library::CallNumber::LC is used to generate cn_sort for Library of Congress callnumbers. According to the LC document "Special Instructions and Tables of Subdivisions for Cartographic Materials", in the section 'Area Subarrangments' The document can be found at http://www.loc.gov/catdir/cpso/class_g.pdf; see page 6: "Regions and political divisions within a city or town may be classified with the use of a colon (:) followed by the number 2 or 3, indicating whether the subdivision is (2) geographic or (3) political and a Cutter number for the subdivision. Examples: G4364 California (map city and town number) .L8:2G7 Los Angeles, Griffith Park (classified as a region) G4114 Michigan (map city and town number) .E4:2M4 East Lansing, Michigan State University (classified as a region) G3804 New York State (map city and town number) .N4:3Q4 New York City, Queens (classified as a political division) " When I use Library::CallNumber::LC::Normalize(), 'G4364 .L8:2G7' and 'G4364 .L8' generate entirely different call numbers: Library::CallNumber::LC->normalize("G4364 .L8:2G7") => G4364 .L00008:00002G00007 Library::CallNumber::LC->normalize("G4364 .L8") => G4364 L8 If I'm reading the Library of Congress instructions instructions correctly, I believe that "G4364 .L8:2G7" should generate as "G4364 L8:2G7", which would sort after "G4364 L8", whereas "G4364 .L00008:00002G00007" sorts before "G4364 L8". I'm also filing a bug with the module maintainer: https://github.com/libraryhackers/library-callnumber-lc/issues/10 -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 16551] New: Display the name of lists to the search results at the OPAC
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '21

04 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16551 Bug ID: 16551 Summary: Display the name of lists to the search results at the OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: OPAC Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org This new enhancement will allow to add the name of lists containing a biblio to the search results at the OPAC -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 17240] New: Allow processes that rely on background jobs run in Plack mode
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '21

03 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17240 Bug ID: 17240 Summary: Allow processes that rely on background jobs run in Plack mode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Since Plack mode (PSGI), the processes running with background jobs are broken. Bug 15218 corrected by using CGI mode for concerned pages. This patch proposes to allow running those pages in PSGI mode by disabling background jobs when PSGI is used. -- You are receiving this mail because: You are watching all bug changes.

1 46

[Bug 17775] New: blocker of bug 7172
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17775 Bug ID: 17775 Summary: blocker of bug 7172 Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: mnashbat(a)alfaisal.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Koha & ldap authentication fail authenticating new users when enabling plack, it works fine only if plack is desabled. Ldap authentication works fine with old registered users. -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 19444] New: Automatic renewal script should not auto-renew if a patron' s record has expired
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '21

23 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19444 Bug ID: 19444 Summary: Automatic renewal script should not auto-renew if a patron's record has expired 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: janet.mcgowan(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently with the automatic_renewals.pl script, materials are still auto-renewed even if the patron's account has expired. The automatic renewals script has error conditions which prevent automatic renewals in these circumstances: $error eq 'too_many' or $error eq 'on_reserve' or $error eq 'restriction' or $error eq 'overdue' or $error eq 'auto_too_late' or $error eq 'auto_too_much_oweing' or $error eq 'auto_too_soon The error conditions should take into account the expiry date of borrower and not auto renew if the borrower's account has expired. For example adding a new error code such as 'borrower_expired' - or whatever convention achieves this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 17979] New: Fatal error when searching from addbooks.pl due to ISBN flaw
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '21

23 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17979 Bug ID: 17979 Summary: Fatal error when searching from addbooks.pl due to ISBN flaw Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If you're doing a "Cataloging Search" from /cgi-bin/koha/cataloguing/addbooks.pl, and you type in "1st to die", you'll see the following: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 5 at /<koha>/lib/C4/Breeding.pm line 107 The reason is that the string is 10 characters long and contains a digit, so Koha thinks it's an ISBN. But when it tries to normalize it, it fails, and instead Koha generates no data for the WHERE clause and then the SQL statement fails because it contains a WHERE without the actual clause. The code: if ($query) { # fill isbn or title, depending on what has been entered #u must do check on isbn because u can find number in beginning of title #check is on isbn legnth 13 for new isbn and 10 for old isbn my ( $title, $isbn ); if ($query=~/\d/) { my $clean_query = $query; $clean_query =~ s/-//g; # remove hyphens my $querylength = length $clean_query; if ( $querylength == 13 || $querylength == 10 ) { $isbn = $query; } } if (!$isbn) { $title = $query; } ( $countbr, @resultsbr ) = BreedingSearch( $title, $isbn ); } -- You are receiving this mail because: You are watching all bug changes.

1 27