January 2019 - Koha-bugs - lists.koha-community.org

[Bug 21746] New: Remove NO_LIBRARY_SET
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '20

16 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21746 Bug ID: 21746 Summary: Remove NO_LIBRARY_SET 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 Depends on: 20489 NO_LIBRARY_SET was used when the DB user was logged in. Since bug 20489 it's not longer possible. We could remove the code. We also have 2 TT variables: LoginBranchcode, LoginBranchname And 1 template method, Branches.GetLoggedInBranchcode. We could simplify and unify that code Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20489 [Bug 20489] Prevent DB user login -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 21137] New: Remplace BORROWER_INFO and USER_INFO with logged_in_user
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '20

16 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21137 Bug ID: 21137 Summary: Remplace BORROWER_INFO and USER_INFO with logged_in_user Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 18403 We now have a Koha::Patron object sent to the templates, logged_in_user. It must be used everywhere patron's info are needed. BORROWER_INFO and USER_INFO can be replaced using it. See commit d2f2590c894efca417112795e05248dbd16636f5 Bug 18403: Send logged_in_user to template from C4::Auth Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18403 [Bug 18403] Hide patron information if not part of the logged in user library group -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 20483] New: Allow users to delete specific borrower history entries, independent of of anonymising data
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '20

16 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20483 Bug ID: 20483 Summary: Allow users to delete specific borrower history entries, independent of of anonymising data 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: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Borrowers should be able to granularly delete or anonymise their own issuing histories. Possibly we should only remove what the item was, not the entire record of the checkout. For example, if someone had issued 10 books in the past, but didn't want "the three little pigs" to turn up in their history anymore, they should be able to delete this. This borrower could either show a statistic of "10 issues" with titles for 9, or we could remove the record of the issue altogether. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 19833] New: Kill the "biblios"
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '20

15 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19833 Bug ID: 19833 Summary: Kill the "biblios" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org For bibliographic record we use three string variants: - biblio - biblio record - biblliographic record According to our terminology we should always use "bibliographic record", we should modify it in all templates. https://wiki.koha-community.org/wiki/Terminology -- You are receiving this mail because: You are watching all bug changes.

1 72

[Bug 21086] New: Wrong mock of DateTime->now in tests
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '20

13 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21086 Bug ID: 21086 Summary: Wrong mock of DateTime->now in tests Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 20287, 19705 prove t/db_dependent/DecreaseLoanHighHolds.t t/db_dependent/DecreaseLoanHighHolds.t .. 1/17 Can't locate object method "truncate" via package "80" (perhaps you forgot to load "80"?) at /home/vagrant/kohaclone/C4/Circulation.pm line 3497. What is happening: We mock DateTime->now in the script to avoid the date comparaisons to fail on slow servers (see bug 19705). my $now_value = DateTime->now(); my $mocked_datetime = Test::MockModule->new('DateTime'); $mocked_datetime->mock( 'now', sub { return $now_value; } ); Since bug 20287, we have the following calls: Koha::Patron->store => Koha::Patron::Category->get_expiry_date which does: 221 return $date->add( months => $self->enrolmentperiod, end_of_month => 'limit' ); as enrolmentperiod is generated by t::lib::TestBuilder, it can be quite big, and so the date change from one call to the others. The failure is actually coming from the date becoming > 9999, which is not handled correctly, on purpose, by Koha::DateUtils (infinite) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19705 [Bug 19705] DecreaseLoanHighHolds.t is still failing randomly https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20287 [Bug 20287] Move AddMember and ModMember to Koha::Patron -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 18369] New: Broken title link in UNIMARC catalog search results table
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '20

12 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18369 Bug ID: 18369 Summary: Broken title link in UNIMARC catalog search results table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: synapse.ova(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In staff client, «Search the catalog» returns a table, where biblio title has a broken link (biblionumber is absent), yet other links works good (Holds, Edit Record, Edit items, OPAC view) Steps to Reproduce: In staff client, search the catalog (Cataloging → «Search the catalog» (/cgi-bin/koha/catalogue/search.pl)) Actual Results: Title of the biblio has a link, that doesn't have biblionumber Expected Results: Title of the biblio should have a link with a proper biblionumber at the end Additional Information: Each biblio in the results table is shown by XSL transformation of MARC data. XSL (\intranet-tmpl\prog\en\xslt\UNIMARCslim2intranetResults.xsl) prepares a link, and adds a biblionumber, that it expects to get from controlfield 001. But since this field could be either empty or contain something different than biblionumber (see https://lists.katipo.co.nz/public/koha/2015-September/043652.html) it is better to pass the biblionumber to this script. This script is already receiving sysprefs (that is not according to marcxml standart), so I suggest to pass the biblionumber the same way. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 20391] New: Koha creates new authorities for 100 & 700 tags bringing in the relator term into the new authority
by bugzilla-daemon＠bugs.koha-community.org 11 Jun '20

11 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20391 Bug ID: 20391 Summary: Koha creates new authorities for 100 & 700 tags bringing in the relator term into the new authority Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Current behavior for when you have the system preference for AutoCreateAuthorities set to generate and BiblioAddsAuthorities set to allow, when creating new authority records for 100 & 700 tags, it also creates relator terms. Steps to recreate: When you save a bib record in the basic editor, authorities are connected or created if the system does not have that authority. When Koha creates new authorities for 100 & 700 tags for people it also brings the relator term into the new authority. Most people do not want relator terms in their authority records so they need to inspect their personal authorities and bring in the proper authority from LC (or another source). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 16248] New: ModZebra doesn't update zebraqueue if ES is enabled
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '20

10 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16248 Bug ID: 16248 Summary: ModZebra doesn't update zebraqueue if ES is enabled 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The zebraqueue table should still be populated with updates if ES is enabled, so the Zebra indexer keeps the Z39.50/SRU indexes up to date. To reproduce: - Set SearchEngine = Elasticsearch - Watch for zebraqueue changes $ watch -n 0.5 'echo "SELECT COUNT(*) FROM zebraqueue WHERE done=0" | sudo koha-mysql kohadev' - Call touch_all_biblios.pl to simulate record changes $ sudo koha-shell kohadev ; cd kohaclone $ perl misc/maintenance/touch_all_biblios.pl -v => FAIL: Notice the watch is not changing the number of records to be indexed. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 20948] New: Hold requests on detail.pl
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '20

10 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20948 Bug ID: 20948 Summary: Hold requests on detail.pl Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The next hold request showing on the detail.pl page next to items is useless and should be removed or fixed. The information for requests on an item is misleading. It shows the next item level hold rather than showing the next hold it will fulfill. I understand how this might be useful in some obscure circumstances, but for the most part it leads staff to believe that this is the next hold it will fill, and that is not the case. Case in point...we have a new item, only one in the collection. 33 next available holds, and 1 item level hold at the very end of the list, going to a different library. With all the other holds ahead of it, and the fact that we have local holds priority enabled, this looks very wrong, and leads staff to confusion and panic. It might be helpful to some libraries to see that there is a specific hold on a particular item, but around here, most libraries will view this as misleading. There should be a setting to change the behavior, or turn it off. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 15972] New: Make it possible to include additional title information in notices (such as 245$b)
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '20

10 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15972 Bug ID: 15972 Summary: Make it possible to include additional title information in notices (such as 245$b) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org For some titles the 245$a (MARC21) is not specific enough and it would be necessary to include the 245$b information in the notices, that is currently not mapped in the database. Apart from 245$b (remainder of title) other information like 245$n/$p for volumes would be nice to have. This was reported by a library using serial claims - where the title is often the same and the correct serial can only be identified with the help of additional information. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8