May 2018 - Koha-bugs - lists.koha-community.org

[Bug 19382] New: Add ability to block guarantees based on fees owed by guarantor and other guarantees
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '22

20 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19382 Bug ID: 19382 Summary: Add ability to block guarantees based on fees owed by guarantor and other guarantees 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 14570, 14577 Some libraries would like to not only block the circulation of a guarantor based on fines owed by guarantees, but would also like to block circulation for all guarantees as well. Basically, if a family as a whole reaches a certain threshold of fines, the entire family will be blocked from checking out items. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14570 [Bug 14570] Make it possible to add multiple guarantors to a record https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14577 [Bug 14577] Allow restriction of checkouts based on fines of guarantor/guarantee -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 66

[Bug 20390] New: Elasticsearch - Biblio mappings for UNIMARC (updates existing)
by bugzilla-daemon＠bugs.koha-community.org 15 Jan '22

15 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20390 Bug ID: 20390 Summary: Elasticsearch - Biblio mappings for UNIMARC (updates existing) 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: claire.hernandez(a)biblibre.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 19342] New: Show name private list on biblio when user is logged
by bugzilla-daemon＠bugs.koha-community.org 15 Jan '22

15 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19342 Bug ID: 19342 Summary: Show name private list on biblio when user is logged Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, It would be nice to display name of private list on biblio (/detail.pl and /opac-detail.pl).Actually, you can see the title of the list in a record only when it's a public list. In opac, name of private list would be displayed only when user will be logged. Thanks, Patrick. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[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 20105] New: Ability to allow Article Request to be without an attached record
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '22

07 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20105 Bug ID: 20105 Summary: Ability to allow Article Request to be without an attached record Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: kyle(a)bywatersolutions.com Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com A library inquired about allowing article requests to work similarly to purchase suggestions. Instead of having patron search for the subscription or record that they would like the article from- instead they would like the patron to fill out a form (as they would in a purchase suggestion) with fields (from the system preference : ArticleRequestsMandatoryFields, ArticleRequestsMandatoryFieldsItemOnly, ArticleRequestsMandatoryFieldsRecordOnly Currently when the Request Article link is clicked, it brings up the opac-request-article.pl with a biblio number. This may have a dual purpose - it could potentially be used for ILL material form for a library also! Kelly Bywater Solutions -- You are receiving this mail because: You are watching all bug changes.

1 3

[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 18 Dec '21

18 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 20074] New: Auth_subfield_structure changes hidden attribute
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '21

13 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20074 Bug ID: 20074 Summary: Auth_subfield_structure changes hidden attribute Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org >From bug 18811 comment40: It sounds like there is something else to fix: On a new DB: MariaDB [koha_kohadev]> select tagfield, tagsubfield, hidden from auth_subfield_structure where tagfield=551 and tagsubfield=9 and authtypecode="GEOGR_NAME"\G *************************** 1. row *************************** tagfield: 551 tagsubfield: 9 hidden: 1 Edit the subfields for GEOGR_NAME /admin/auth_subfields_structure.pl?op=add_form&tagfield=551&authtypecode=GEOGR_NAME Possible value for "Select to display or not"/hidden are -5 and 0, so "Show all" is displayed. Save without modifying anything: hidden is now '0'. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[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