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

[Bug 23583] New: Make the BarcodeSeparators be a YAML syspref
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '21

13 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23583 Bug ID: 23583 Summary: Make the BarcodeSeparators be a YAML syspref Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 26078] New: "Item returns to issuing library" creates infinite transfer loop
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '21

13 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26078 Bug ID: 26078 Summary: "Item returns to issuing library" creates infinite transfer loop 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 23129 changed ModItemTransfer to set the holding branch of an item to current location when generating a transfer. This doesn't play well with the return policy "Item returns to issuing library," which sends an item to its holding branch at checkin. To recreate: - Have 2+ branches - Set your default return policy to Item returns to issuing library - Find an item with holding branch of Branch A - Set your library to Branch B - Check item in - Koha generates a transfer to Branch A. In doing so, it sets the item holding branch to Branch B - Set your library to Branch A - Check item in - Koha generate a transfer to Branch B. In doing so, it sets the item holding branch to Branch A - Set you library to Branch A - Check the item in . . . Repeat indefinitely. It's easy enough to cancel a transfer to get out of this loop, but better not to get into it in the first place. That said, I'm not entirely sure how to avoid it. Can we somehow tell Koha that a checkin that ends a transfer should never start a new transfer? Unless there's a hold involved? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 21932] New: reservetype and reserveexpiration needed for holds (reserves and old_reserves tables)
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '21

13 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21932 Bug ID: 21932 Summary: reservetype and reserveexpiration needed for holds (reserves and old_reserves tables) Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement 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 I see an inherent flaw in the reserves table and process. If a hold is waiting, and someone changes the status from waiting back to a priority level, the waiting status is removed, but the expiration remains. Also, if the hold was a first available hold, it is now changed to an item level hold for the item it was on hold for. I would suggest that a new field be created for the holds table, such as reservetype, and is marked as 'ANY' or 'SPECIFIC'. I would suggest that a new field be created for the reservation expiration called reserveexpiration, separate from the waiting expiration, as to maintain a reservation cutoff date if the status is changed back to a priority level. This would make the expirationdate exclusive to waiting items. I would suggest that when priority level is changed from waiting to a priority level, the reservetype is checked, and if it is marked as ANY, the item number be removed. If it is SPECIFIC, the item number is kept. I would suggest that the expirationdate be cleared if changed from a waiting status to a priority level. I would suggest that all pages that show the "Expiration date" as the reservationexpiration, if exists, or superseded by expirationdate, if exists. No need to have a separate cell for both. I would suggest that when a hold is triggered and marked as waiting, the expiration date is calculated, or limited to the reservationexpiration, whichever is shorter. No sense in holding it longer than the patron was willing to wait for it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 22690] New: Merging problem with records with many items (ElasticSearch)
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '21

13 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22690 Bug ID: 22690 Summary: Merging problem with records with many items (ElasticSearch) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: vitorfernandes87(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- When merging records with many items, Koha reindexes the origin record and the destination record for each item moving (check MoveItemFromBiblio in C4::Items). If the record being eliminated has 1000 items, Koha will make 2000 reindexes. Because of this behaviour, the merging is too slow. Test plan: - Create 2 records (one with 1000 items for example) - Add the records to one list and start the merging process of those records. - Choose the record with many items as the one to be eliminated. - Start the merging - After a while the web server should give you a timeout error (the merging process continues) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 253

[Bug 23035] New: Intranet search is slow if thousands of items are in the biblios shown in the search results
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '21

13 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23035 Bug ID: 23035 Summary: Intranet search is slow if thousands of items are in the biblios shown in the search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Searching Assignee: joonas.kylmala(a)helsinki.fi Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- If you search on intranet for biblios that have in total thousands of items then then the search result will load very very slowly. The slowing down is linear with the amount of items in the bibs. I already tracked this down to a GetAuthorisedValueDesc() call in C4/XSLT.pm. I will start working on a patch for this. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 26776] New: Authorities: Replace authority with Z3950 does not update existing record
by bugzilla-daemon＠bugs.koha-community.org 12 Oct '21

12 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26776 Bug ID: 26776 Summary: Authorities: Replace authority with Z3950 does not update existing record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org When trying to replace an existing auth record in the Authorities module via Z3950, it seems that I can only add new imported records but not replace an existing one. If I get the warning "Duplicate suspected", it only offers me to edit the existing record or add a new one. But I want to replace the old one. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 24197] New: Custom destination for failed overdue notices
by bugzilla-daemon＠bugs.koha-community.org 12 Oct '21

12 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24197 Bug ID: 24197 Summary: Custom destination for failed overdue notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Notices Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Currently failed overdue notices are sent to the branch email , or when that is not set to the KohaAdminEmailAddress syspref. Several of our clients have requested a seperate email address for failed overdue notices to be sent to. This email address will be defined in the: RedirectAddressForFailedOverdueNotices syspref. -- You are receiving this mail because: You are watching all bug changes.

1 40

[Bug 22964] New: Change "product" language on bugzilla bug report page
by bugzilla-daemon＠bugs.koha-community.org 11 Oct '21

11 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22964 Bug ID: 22964 Summary: Change "product" language on bugzilla bug report page Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Bugzilla Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: donna(a)kattekrab.net Target Milestone: --- Created attachment 89957 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=89957&action=ed… screenshot of the "select product" text on bugzilla When filing a bug, we see these words: First, you must pick a product on which to enter a bug: Koha: Koha - Free Software ILS Koha security: Security bugs for Koha. Please use this product ONLY if you are reporting a security bug that should be held in confidence prior to the release of a fix. Project Infrastructure: For logging bugs related to the Koha project infrastructure. Not Koha itself. You almost certainly don't want to log a bug here, but under the Koha project. I find "Pick a product" and "Use this product" to be a bit confusing in this context. Here's some alternative phrasing to consider. First, you need to decide where to enter a bug: Koha: Koha Free Software ILS (integrated library system) Koha security: Security bugs for Koha. Use this ONLY if you are reporting a security big that should be held in confidence prior to the release of a fix. Project Infrastructure: Bugs related to the Koha project infrastructure (eg bugzilla, gitlab, or the project website. Not for Koha itself. You almost certainly don't want to log a bug here, but under the Koha project. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 18328] New: There is no history for article request
by bugzilla-daemon＠bugs.koha-community.org 11 Oct '21

11 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18328 Bug ID: 18328 Summary: There is no history for article request 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: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Il would be useful if the "Cancelled requests" and "Completed requests" of articles request were kept in different tabs, just like it exists for acquisition suggestions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 22829] New: Elasticsearch - some blank subfields cause parsing errors during indexing
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22829 Bug ID: 22829 Summary: Elasticsearch - some blank subfields cause parsing errors during indexing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Target Milestone: --- Some fields in the record cause errors during indexing if they exist but are blank To recreate: 1 - Use the koha sample data or edit a record using the advanced cataloging editor and blank 100$a (probably also shouldn't be allowed) 2 - Save record 3 - Reindex ES 4 - Note you cannot search for the record bug 22828 will show you the error from ES -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4