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

[Bug 24658] New: Deleting items with fines does not update itemnumber in accountlines to NULL causing ISE
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '21

12 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24658 Bug ID: 24658 Summary: Deleting items with fines does not update itemnumber in accountlines to NULL causing ISE Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: addie(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When batch deleting items through the staff client, the itemnumber in the accountlines table remains and does update to NULL. If you then go into the Accountlines tab of a borrower and into the Transactions you will get an internal server error if there is a fine in that patrons accountlines with an itemnumber in the database for the deleted item -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 24519] New: Change calculation and validation in Point of Sale should match Paycollect
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '21

12 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24519 Bug ID: 24519 Summary: Change calculation and validation in Point of Sale should match Paycollect Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Bug 22359 updates the paycollect form logic to clarify each input fields use and adds validation to reduce the risk of errant data being entered. The point of sale screen payment form should match these changes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 22243] New: Advanced Cataloguer editor fails if the target contains an apostrophe in the name
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '21

12 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22243 Bug ID: 22243 Summary: Advanced Cataloguer editor fails if the target contains an apostrophe in the name Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- As the title, if a z39.50 target has an apostrophe in the name, the editor fails with an "Unexpected token" Javascript error. The array containing the targets is constructed then embedded in the page template and, since the string is enclosed in unescaped single apostrophes, things fall over. The fix is to replace ' in target names with ' -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 20971] New: additem Corrupted storable string
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '21

12 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20971 Bug ID: 20971 Summary: additem Corrupted storable string Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Sometimes additem.pl will complain about "Storable::thaw failed to thaw LastCreatedItem-cookie.", see bug 14844. Now, actually fix the bug. The bug is caused by trying to URI (un)escape MARC::Record, binary data. We'll use a base64 url-safe version instead. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 25462] New: Shelving location should be on a new line in holdings table
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '21

12 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25462 Bug ID: 25462 Summary: Shelving location should be on a new line in holdings table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the staff client, if an item has a long shelving location description, it displays on the same line as the Home Library, which doesn't look very good. It ought to be on the next line. https://snipboard.io/YzSTDH.jpg -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 25292] New: L1 cache too long in Z3950 server (z3950-responder)
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '21

12 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25292 Bug ID: 25292 Summary: L1 cache too long in Z3950 server (z3950-responder) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal 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 -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 24470] New: Set import_status when file used to populate basket in acquisitions
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '21

12 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24470 Bug ID: 24470 Summary: Set import_status when file used to populate basket in acquisitions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a staged MARC file is used to populate a basket in acquisitions, import_batches.import_status remains set to "staged" even though those records have been imported. To test: - Create a basket - Add to basket From a New File - Select a marc file and stage without checking for duplicates - Add titles to your basket - Confirm from acquisitions that new bibs were created - Go to manage-marc-import.pl and find your file - Confirm that you are still given an "Import this batch into the catalog" button - Query import_batches.import_status and confirm it shows "staged" We could set the status to the existing value of "imported" or could create a new status unique to acquisitions. See also bug 24469 about import_biblios.matched_biblionumber. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 21301] New: Restriction of the informations given by GetRecords ILS-DI service
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '21

12 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21301 Bug ID: 21301 Summary: Restriction of the informations given by GetRecords ILS-DI service Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Websites, Mailing Lists, etc Assignee: wizzyrea(a)gmail.com Reporter: anne-claire.bernaudin(a)univ-rennes1.fr QA Contact: testopia(a)bugs.koha-community.org Actually, the GetRecords service gives many information : bibliographic data (marcxml field) item data (items field) issue data (issues field) The issue data should not be sent by these service. For example, this service is actually used by EDS clients to display real-time item informations on EDS. Ebsco should not have access to the issues information, even if they are partially anonymised (only the firstname of the patron is sent) in 16.05 and maybe in the later versions of Koha. This would be more compliant with GDPR (see bug 18081). Thanks, Anne-Claire -- You are receiving this mail because: You are watching all bug changes.

1 66

[Bug 25802] New: Koha::Calendar->addDate should be renamed addDuration to better reflect it's purpose
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '21

12 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25802 Bug ID: 25802 Summary: Koha::Calendar->addDate should be renamed addDuration to better reflect it's purpose 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The Koha::Calendar->addDate method actually expects a 'Duration', either as a DateTime::Duration object or as an integer and a unit definition. It would be better-called addDuration to reflect it's nature. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 25054] New: Document and allow customization of search index shortcuts in Search Engine Configuration
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '21

12 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25054 Bug ID: 25054 Summary: Document and allow customization of search index shortcuts in Search Engine Configuration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com It'd be great if the Search Engine Config page in ES would document the various shortcuts available (ti for title, sn for local number, etc). Even better would be an interface to allow local creation of custom shortcuts. Maybe this could be a column added to the two mappings tabs to allow the definition of aliases? The hardcoded default aliases could be populated there in the default mapping? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25