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

[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 2093] Add OPAC dashboard for logged-in users
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '17

26 Nov '17

1 0

[Bug 8995] Show OpenURL links in OPAC search results
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '17

26 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8995 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|rel_17_11_candidate | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12768] Replacement cost and processing fee management
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '17

26 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12768 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|rel_17_11_candidate | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14769] Authorities merge: Set correct indicators in biblio field
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '17

24 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14769 Janusz Kaczmarek <januszop(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14769] Authorities merge: Set correct indicators in biblio field
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '17

24 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14769 --- Comment #11 from Janusz Kaczmarek <januszop(a)gmail.com> --- Created attachment 69343 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=69343&action=ed… 14769: Authorities merge: Set correct indicators in biblio field -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14769] Authorities merge: Set correct indicators in biblio field
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '17

24 Nov '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14769 Janusz Kaczmarek <januszop(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |januszop(a)gmail.com --- Comment #10 from Janusz Kaczmarek <januszop(a)gmail.com> --- Hello to all. To not open a new bug I would like to submit here a patch that should fix this painful and far-too-long-still-not-resolved issue. The proposed approach relies on authority records (which should be correct--that's exactly why they are called 'authority' records). Especially MARC 21 case, as stated by Zeno, is more complex, specially for 6XX (2nd ind., $2 subfield etc.) To test -- have some authority recs. with different tags (eg. 100, 130, 150), use them in biblio, especially in 6XX, 7XX (setting 2nd ind). Have running indexer and proper value of AuthorityMergeLimit, i.e. not 0. Then play with indicators in authorities. For MARC 21 auth used in 6XX play also with 008/11 and 040 $f (if 008/11 set to 'z'). Have a look at the results in biblio (see subfield $2 in MARC 21 6XX if 008/11 = z and 040 $f defined). -- You are receiving this mail because: You are watching all bug changes.

1 0