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

[Bug 18399] New: Reason is missing in suggestion management part
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '17

27 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18399 Bug ID: 18399 Summary: Reason is missing in suggestion management part Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org When we want to deal a suggestion by editing it (suggestion.pl?suggestionid=XX&op=edit), we can change the status but we can't add a reason. It's a pitty because changing the status would trigger the workflow and mail sending and in email we provide the reason if the suggestion is rejected... So patron will not have the reason if we change the status here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 17176] New: Did you mean searches should respect UseAuthoritiesForTracings and search by terms instead of numbers
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '17

27 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17176 Bug ID: 17176 Summary: Did you mean searches should respect UseAuthoritiesForTracings and search by terms instead of numbers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In catalogs where some authorities may not be linked it would be beneficial to have 'Did you mean?' searches constructed with terms rather than authority numbers as the latter can result in dead links. Alternatively 'Did you mean?' shouldn't suggest unused authorities -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 19252] New: Upgrading message shows identical Version
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '17

27 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19252 Bug ID: 19252 Summary: Upgrading message shows identical Version Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 66836 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=66836&action=ed… Screenshot upgrading message with identical version in web installer While upgrading, the web installer shows a message similar like "We are upgrading from Koha 17.06.00.004 to 17.06.00.004" Expected: Different version numbers for "from" and for "to". It seems that dbversion and kohaversion are the same in installer/step3.tt (see screenshot). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 19402] New: Date of birth datepicker year range depending on current value
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '17

27 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19402 Bug ID: 19402 Summary: Date of birth datepicker year range depending on current value Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 18447 sets for date of birth a year range "c-100:c" meaning current year and 100 years earlier. This is good when imput is empty. But when input already contains a date, say "01/01/1950", years range is 1850 to 1950. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 19536] New: Odd number of elements in anonymous hash in svc/bib
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '17

26 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19536 Bug ID: 19536 Summary: Odd number of elements in anonymous hash in svc/bib Change sponsored?: --- Product: Koha Version: master 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Testing Rancor gave me: Odd number of elements in anonymous hash at /usr/share/koha/masterclone/svc/bib line 69. Odd number of elements in anonymous hash at /usr/share/koha/masterclone/svc/bib line 118. Odd number of elements in anonymous hash at /usr/share/koha/masterclone/svc/bib line 69. Called in koha-tmpl/intranet-tmpl/lib/koha/cateditor/koha-backend.js -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 19481] New: Elasticsearch - Set default fields for sorting in mappings.yaml
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '17

26 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19481 Bug ID: 19481 Summary: Elasticsearch - Set default fields for sorting in mappings.yaml 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 Currently sorting options are hardcoded, some of the options are not defined as sortable in the default ES mappings leading to search errors -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 18357] New: On-site checkouts issues with 'Unlimited'
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '17

26 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18357 Bug ID: 18357 Summary: On-site checkouts issues with 'Unlimited' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When on-site checkouts are 'Unlimited' the checkouts can be blocked if there is a limit for checkouts in general To reproduce: Set All/All rule with Unlimited/unlimited for normal/onsite checkouts Will be able to perform onsite checkout Edit rule to be 15/Unlimited normal/onsite Will get error 'Too many: 1 on site checkout, only are allowed' Set rule to 15/15 Onsite checkouts work again Similar issue with Default checkout, hold and return policy and Default checkout limit by patron category -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 18131] New: Matching staged records when using elastic search fails
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '17

26 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18131 Bug ID: 18131 Summary: Matching staged records when using elastic search fails Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl There is a perl related bug in C4/Matcher.pm when collecting matched records. "simple_search_compat" returns a reference to an array of matches. When using ElasticSearch, this array contains MARC::Record objects. The score for these matches are then collected (currently line 692-694) into a hash "%matches" where the matched object is used as the key. Perl converts all hash keys into strings, so the object is lost. The hash "%matches" is used in a foreach (line 708) where it assumes the object can be recovered from the key, but this is not the case. The error in the log is: stage-marc-import.pl: Can't locate object method "fields" via package "MARC::Record=HASH(0xb403da8)" (perhaps you forgot to load "MARC::Record=HASH(0xb403da8)"?) at /home/vagrant/kohaclone/C4/Biblio.pm line 2691., referer: http://localhost:8081/cgi-bin/koha/tools/stage-marc-import.pl Steps to reproduce (given an instance using ElasticSearch as search engine): 1. Export a bibliographic record in MARC format. 2. Create a matching rule that matches on "999$c" with a score and threshold of 1000 (doesn't really matter as long as they're the same) 3. Edit the record in Koha so that they're slightly different (this is probably unnecessary). 4. Upload the exported file in Stage MARC import, and select the matching rule you created, then click on "Stage for import". Expected outcome: Redirected to the batch page with the matching record being shown. Actual outcome: Things seem to hang, but in reality the staging has crashed with the error shown above. -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 17051] New: Default order biblio subfields in framework
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '17

24 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17051 Bug ID: 17051 Summary: Default order biblio subfields in framework Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, It would be nice if subfields in framework editor could have subfields put in any order. With RDA, subfield "i" is often in first position. It would be nice having a way to set by default an order of subfield for a framework. Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 18616] New: The "Add forgot password link to OPAC" should allow patrons to use their library card number in addition to userid
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '17

23 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18616 Bug ID: 18616 Summary: The "Add forgot password link to OPAC" should allow patrons to use their library card number in addition to userid 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: techservspec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 8753 will only accept the patron's username. However some libraries do not use the username for identifying patrons, only their library card number. The "Forgot your password" feature should allow patrons to enter either their username or their card number in the Log In box (in addition to their email address) in order to reset their password. -- You are receiving this mail because: You are watching all bug changes.

1 41