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

[Bug 19588] New: There is no ILL requests history
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '20

25 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19588 Bug ID: 19588 Summary: There is no ILL requests history Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: In Discussion Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Blocks: 7317 When a request is deleted, the row is removed from illrequests. Is that expected? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7317 [Bug 7317] Add an Interlibrary Loan Module to Circulation and OPAC -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 17232] New: Subfield default values are not ported when creating a new framework from an old one
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '20

24 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17232 Bug ID: 17232 Summary: Subfield default values are not ported when creating a new framework from an old one Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: joachim.ganseman(a)ehb.be QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When creating a new bibliographic MARC21 framework from an old one, any default values set for subfields in the old framework are not ported to the newly created framework. They have to be reset. To reproduce: - Set a default value in an existing bibliographic MARC21 framework, e.g. 040$a to your institution's MARC code. - Create a new framework based on that one - Create a new record using that new framework: the default value is not set. - Upon checking the database table marc_subfield_structure (e.g. WHERE tagfield = 40 and tagsubfield = 'a'), notice there is no defaultvalue set in that subfield in the new framework. This issue occurs in a package install of version 16.05 on Debian. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 19705] New: DecreaseLoanHighHolds.t is still failing randomly
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '20

19 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19705 Bug ID: 19705 Summary: DecreaseLoanHighHolds.t is still failing randomly Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org https://jenkins.koha-community.org/job/Koha_Master_D8/298/console # Failed test 'Static mode should exceed threshold' # at t/db_dependent/DecreaseLoanHighHolds.t line 125. # got: '0' # expected: '1' # Failed test 'Should have duration of 1' # at t/db_dependent/DecreaseLoanHighHolds.t line 127. # got: '0' # expected: '1' # Failed test 'due_date should be a DateTime object' # at t/db_dependent/DecreaseLoanHighHolds.t line 128. # got: '' # expected: 'DateTime' Can't call method "hour" on an undefined value at t/db_dependent/DecreaseLoanHighHolds.t line 131. # Looks like your test exited with 255 just after 5. [18:52:27] t/db_dependent/DecreaseLoanHighHolds.t ......................... Dubious, test returned 255 (wstat 65280, 0xff00) Failed 15/17 subtests -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 18519] New: Add ability to skip irrelevant dates in Koha::Calendar
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '20

17 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18519 Bug ID: 18519 Summary: Add ability to skip irrelevant dates in Koha::Calendar 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 We've seen occurrences of fines.pl and overdue_notices.pl slowing down when there are a large number of (usually old) entries in special_holidays table. Apparently, we're checking each candidate day against the whole fines calendar -- this is unnecessary, as both fines and overdue notices are are bounded; we only need to check the calendar enteries between the current day and the relevant letter delay (for overdue notices) or between the day the item went overdue and the current day (for fines). If we could pass in a start and end date, we could eliminate this overhead. -- You are receiving this mail because: You are watching all bug changes.

1 13

[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 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