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

[Bug 13654] Cannot place a hold for biblio with too many items to display unless viewing them all
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13654 koha-US bug tracker <bugzilla(a)koha-us.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla(a)koha-us.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23341] New: Hold Notes should allow for HTML tags
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23341 Bug ID: 23341 Summary: Hold Notes should allow for HTML tags Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: training(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In Koha version in 18.11, HTML tags should be allowed in Hold Notes. THis is similar to bug 23194, 22702, 22501. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 25465] New: Batch delete records based on imported MARC batch
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25465 Bug ID: 25465 Summary: Batch delete records based on imported MARC batch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Various vendors send libraries batches of MARC records for deletion -- these are records the library already has in their system that should be deleted as the vendor no longer offers them. Right now we can: - stage the batch for import using a matching rule - run a report to return matched biblionumbers - batch delete based on the report output It'd be great to streamline this. My two thoughts are either we could add a new option to batch record deletion to allow use of an imported file to identify records OR we could add a new matching behavior of "delete matched record" to the batch staging tool. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 4461] Context-sensitive report a problem screen
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4461 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomascohen(a)gmail.com --- Comment #204 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- Nice job! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8338] Fines not cleared with dropbox mode
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8338 Fiona Borthwick <fiona.borthwick(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fiona.borthwick@ptfs-europe | |.com --- Comment #16 from Fiona Borthwick <fiona.borthwick(a)ptfs-europe.com> --- If the user returned the book on time and left it in a bookdrop due to the library being closed, then that user should not have a fine imposed. I realise that the fines job will have run and populated the fine before the library removes the book from the bookdrop. However when they then set the return date to reflect the 'real' date (e.g. yesterday), then Koha will know that the book was returned on time and therefore no fine should have been generated. Personally I think an audit trail is not required for this purpose. The fine (whilst it was applied) would not have been if the library had been open and the user could return the item to the counter. >From a user's perspective they are not going to want evidence of a fine on their account when it was not needed nor a proper fine. I would opt for it to be deleted completely. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 4461] Context-sensitive report a problem screen
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4461 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |25466 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25466 [Bug 25466] Review 'problem_reports' column names and types -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10869] Can't cancel order line if title deleted
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10869 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |20271 CC| |jonathan.druart(a)bugs.koha-c | |ommunity.org Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20271 [Bug 20271] Merge deleted biblio, biblioitems, biblio_metadata, and items tables -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11966] make course reserves branch specific
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11966 Kelly McElligott <kelly(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kelly(a)bywatersolutions.com --- Comment #1 from Kelly McElligott <kelly(a)bywatersolutions.com> --- This would be beneficial for a consortium - to allow for a branch to be assigned to a specific library when creating a new course. This would also help looking for a branch specific course in the OPAC and Staff Client. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15253] Add Koha::Logger based logging for SIP2
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15253 Kyle M Hall <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |25464 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25464 [Bug 25464] Add ability to specify client IP and SIP account used in SIP2 logging -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 22081] New: Alternate merging functionality
by bugzilla-daemon＠bugs.koha-community.org 12 May '20

12 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22081 Bug ID: 22081 Summary: Alternate merging functionality 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: simon.hohl(a)dainst.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- Currently the merging process let's you select which fields ought to be copied over to the "winning" record from the "loosing" record(s). Afterwards, the "loosing" record is deleted (moved to tables "deletedbiblio" etc.). One problem with the current solution: You can't tell after the fact, which deleted record was merged with which existing record. This is bad if you want to provide stable links to bibliographic records, for citation in research papers for example: Ideally you would want to be able to redirect to the "winning" records if somebody calls URL to a deleted record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4