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

[Bug 24413] New: MarkLostItemsAsReturned functionality does not lift restrictions caused by long overdues
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '20

12 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24413 Bug ID: 24413 Summary: MarkLostItemsAsReturned functionality does not lift restrictions caused by long overdues Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If an account has been restricted by the long overdue process, and the item causing the restriction is returned by marking it lost (via MarkLostItemsAsReturned), the restriction is not lifted despite 'AutoRemoveOverduesRestriction' being marked to 'Do'. To replicate: 1. Set MarkLostItemsAsReturned to 'from items tab of the catalog module' 2. Set AutoRemoveOverduesRestrictions to 'Do' 3. Set up an overdues restriction in the notice triggers 4. Check out an item and let the overdues process restrict the account 5. Navigate to the moredetail.pl page (items tab) for the overdue item 6. Mark the item lost 7. Return to the account in question - notice the item has been returned, but the restriction remains -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 24062] New: Circulation tests fail randomly if patron category type is 'X'
by bugzilla-daemon＠bugs.koha-community.org 11 Jun '20

11 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24062 Bug ID: 24062 Summary: Circulation tests fail randomly if patron category type is 'X' Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED 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 The items are not issued if the patron category's type is 'X', used for statistics. koha_1 | # Failed test 'ISSUED_TO_ANOTHER question flag should be set if AutoReturnCheckedOutItems is disabled and item is checked out to another' koha_1 | # at t/db_dependent/Circulation.t line 1994. koha_1 | # got: undef koha_1 | # expected: '1' koha_1 | # Looks like you planned 2 tests but ran 1. koha_1 | # Looks like you failed 1 test of 1 run. koha_1 | koha_1 | # Failed test 'CanBookBeIssued + AutoReturnCheckedOutItems' koha_1 | # at t/db_dependent/Circulation.t line 2001. koha_1 | Can't call method "borrowernumber" on an undefined value at t/db_dependent/Circulation.t line 1998. -- You are receiving this mail because: You are watching all bug changes.

1 25

[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 23039] New: Hold found modal on checkin screen ( circulation.pl ) obscures Check in message info
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '20

10 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23039 Bug ID: 23039 Summary: Hold found modal on checkin screen ( circulation.pl ) obscures Check in message info Change sponsored?: --- Product: Koha Version: unspecified 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 Target Milestone: --- During the checkin process, all the message info is completely obscured by any modal forms that may be triggered by the checkin. In some cases that info could be vital to making an informed decision as to what option to choose in the modal itself. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 24371] New: OPAC 'Showing only available items/Show all items' is double encoded
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '20

10 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24371 Bug ID: 24371 Summary: OPAC 'Showing only available items/Show all items' is double encoded Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The show all items link is double encoded when attempt to limit a seach via the facets and toggle 'Showing only available items/Show all items' To Recreate: 1. Make an OPAC search with plenty of results. 2. Use the search facets to limit the search in some way, item type, author, etc. 3. Click on 'Limit to currently available items', everything is still fine. 4. Attempt to return to 'Show all items', there will be no search results. The ':' is being double encoded here. (%253A). I think... -- You are receiving this mail because: You are watching all bug changes.

1 17

[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

[Bug 22699] New: Remove documentation on Keywords to MARC mapping
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '20

10 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22699 Bug ID: 22699 Summary: Remove documentation on Keywords to MARC mapping Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 11529 Target Milestone: --- Once bug 11529 is pushed, we'll also need to update the manual and remove any reference to that functionality. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11529 [Bug 11529] Add subtitle, medium and part fields to biblio table -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 23994] New: AdditionalFields.t is failing randomly (U18)
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '20

09 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23994 Bug ID: 23994 Summary: AdditionalFields.t is failing randomly (U18) 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 t/db_dependent/Koha/Objects/Mixin/AdditionalFields.t .. 1/12 # Failed test '->additional_field_values should return the correct values' # at t/db_dependent/Koha/Objects/Mixin/AdditionalFields.t line 82. # Structures begin differing at: # $got->[0]{value} = 'bar value for basket2' # $expected->[0]{value} = 'foo value for basket2' # Looks like you failed 1 test of 12. We do not really know why, but the values are not returned in the order they are stored in DB. Fixing this random failure for now at test level. -- You are receiving this mail because: You are watching all bug changes.

1 16