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

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

[Bug 22004] New: When decreaseLoanHighHolds is set to Enable, suspended holds still count in the number of holds
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22004 Bug ID: 22004 Summary: When decreaseLoanHighHolds is set to Enable, suspended holds still count in the number of holds Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The system preference decreaseLoanHighHolds if set to enable allows the library to modify the checkout length if a records has X number of holds. Unfortunately, Koha will look at the holds and determine to use this system preference and not discard the suspended holds. For example if a library had this system preference to decrease the loan period if a record has 2 holds on it, if there are 2 holds on the item, but one hold has been suspended, then Koha should not decrease the checkout period - however it does. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 18017] New: [Unimarc] Importing biblios from Z39.50 servers duplicates related authorities
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18017 Bug ID: 18017 Summary: [Unimarc] Importing biblios from Z39.50 servers duplicates related authorities 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: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This is a unimarc bug only: When importing biblios from Z39.50, related authorities are wrong matched by the linker. This causes duplicates of authorities. The problem come from a bad marc definition in unimarc/authorities/authority-koha-indexdefs.xml which does not create a index for matching an entire heading. -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 16825] New: Add API route for getting an item
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '21

06 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16825 Bug ID: 16825 Summary: Add API route for getting an item Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: larit(a)student.uef.fi QA Contact: testopia(a)bugs.koha-community.org Add API route for getting an item GET /api/v1/items/{itemnumber} Gets one Item -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 93

[Bug 22445] New: Ability to define a url for custom cover images
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '21

05 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22445 Bug ID: 22445 Summary: Ability to define a url for custom cover images Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- So far we have cover images from a list of webservices, COCE, locally, but we cannot define a custom url. -- You are receiving this mail because: You are watching all bug changes.

1 152

[Bug 20206] New: Should GetItemnumberFromBarcode ignore leading zeroes?
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '21

27 Sep '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20206 Bug ID: 20206 Summary: Should GetItemnumberFromBarcode ignore leading zeroes? 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org GetItemnumberFromBarcode will not find 51320 if it should be 051320. Could we need that? I noticed that Excel stripped leading zeroes and we got missing messages in Inventory. Anyone interested in a patch like the attached one? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31