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

[Bug 26199] New: Record matching rule match check should include Leader/LDR
by bugzilla-daemon＠bugs.koha-community.org 23 Mar '21

23 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26199 Bug ID: 26199 Summary: Record matching rule match check should include Leader/LDR Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, record matching rule match checks can only use control fields and data fields. It would be great if they could also use the leader. This is very useful for matching against LDR06 for instance when you want to make sure that you're getting text instead of an audiobook for instance. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 23929] New: Invoice adjustments should filter inactive funds
by bugzilla-daemon＠bugs.koha-community.org 23 Mar '21

23 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23929 Bug ID: 23929 Summary: Invoice adjustments should filter inactive funds Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 94893 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=94893&action=ed… Screenshot of unfiltered funds in adjustments When adding an adjustment to an invoice, the funds dropdown shows all funds. There should be a filter to allow only active funds, similar to the one on the shipping fund dropdown, as it is impossible to identify the active fund when they are similarly named. See screenshot. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 26964] New: The option to Save is not showing on the Advanced Editor when created a Macro
by bugzilla-daemon＠bugs.koha-community.org 23 Mar '21

23 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26964 Bug ID: 26964 Summary: The option to Save is not showing on the Advanced Editor when created a Macro Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In 20.05.05, the ability to save a new macro is not visible. One needs to create the name of the macro, it will appear on the left, then click that new macro name, and then the options to save and to create the macro public. Seems to need the page refreshed during this process in some way. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 27029] New: Detail page missing Javascript accessible biblionumber value
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '21

22 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27029 Bug ID: 27029 Summary: Detail page missing Javascript accessible biblionumber value Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Bug 26890 raises the point that there's no biblionumber on the detail page that is easily Javascript accessible. We really should be publishing the biblionumber in a feature-independent way, so that different features can leverage the same biblionumber. Here's my ideas so far: 1. data-biblionumber attribute in the body element 2. A RDFa schema.org identifier put in a child of the div.record element 3. Use Template::Toolkit to create a Javascript object that contains the biblionumber as a property 4. HTML element like "<span class="label">Catalogue ID</span>: <span id="biblionumber">1234</span>" I'm actually kind of inclined towards #4, since I have occasionally had people ask for the biblionumber to be published on the HTML to make it easier to see and reference... (although more so for the Staff Interface than the OPAC admittedly) -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 26209] New: BlockReturnofLostItems does not prevent lost items being found
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '21

22 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26209 Bug ID: 26209 Summary: BlockReturnofLostItems does not prevent lost items being found Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: andrew(a)bywatersolutions.com, fridolin.somers(a)biblibre.com, gmcharlt(a)gmail.com, katrin.fischer(a)bsz-bw.de, kyle.m.hall(a)gmail.com, kyle(a)bywatersolutions.com, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 21231 +++ This bug was initially created as a clone of Bug #21231 +++ >When the syspref BlockReturnOfLostItems is set to Block, the item is blocked from being returned, but is still >considered found -- it's set to lost=0 and a refund is applied to the patron (if circ rules allow). The item can >then be checked in a second time and returned as it is no longer lost. There are still a number of logical holes in the code. ModDateLastSeen is called in a number of places without a flag being passed to prevent the itemlost update. I must admit, I find it confusing to be able to update the last seen timestamp when the item is still 'lost'.. it feels like a logical flaw. Should we not alert the user performing the action that the item was lost and get feedback on what to do? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21231 [Bug 21231] BlockReturnofLostItems does not prevent lost items being found -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 15751] New: Koha offline circulation Firefox addon does not update last seen date for check-ins
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '21

22 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15751 Bug ID: 15751 Summary: Koha offline circulation Firefox addon does not update last seen date for check-ins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: contribs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: fridolin.somers(a)biblibre.com, koha-bugs(a)lists.koha-community.org, testopia(a)bugs.koha-community.org When I check in something using the KOCT the last seen date is not updated. It does update the last seen date upon checkout, for what it's worth. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. You are watching all bug changes.

1 22

[Bug 27578] New: Searchid not initialized when adding a new record
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '21

22 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27578 Bug ID: 27578 Summary: Searchid not initialized when adding a new record 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl addbiblio.pl takes a searchid parameter which is built into several urls, however, when adding a new biblio and not coming from a search this value is never initialized and there is a warn -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 25777] New: Datatables on z3950_search.pl show incorrect number of entries
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '21

22 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25777 Bug ID: 25777 Summary: Datatables on z3950_search.pl show incorrect number of entries Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Datatables on z3950_search.pl will say "Showing 1 to 20 of 20 entries", which makes you think that there are only 20 search results. However, if you scroll to the bottom of the page, you'll often see it saying something like "Showing page 1 of 501". We should hide the "Showing 1 to 20 of 20 entries" datatables information if we're not going to implement a JSON sourced table. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 27569] New: marc-framework import function doesn't accept LibreOffice csv/ods file formats
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '21

22 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27569 Bug ID: 27569 Summary: marc-framework import function doesn't accept LibreOffice csv/ods file formats Change sponsored?: --- Product: Koha Version: 20.11 Hardware: PC OS: Linux Status: NEW Severity: blocker Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: braun.kamilla(a)web.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The biblographic marc-framework import function does not except any of the ods-file format standards (i.e. 1.0/1.1; 1.2; 1.2 extended (compatibility-mode); 1.2 extended) used by LibreOffice. The csv-format stored by LibreOffice is also not usable. This makes the marc-framework export/import functions unusable. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 49

[Bug 23282] New: Show all columns in Batch Item Modification and Batch Item Deletion
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '21

19 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23282 Bug ID: 23282 Summary: Show all columns in Batch Item Modification and Batch Item Deletion Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently when using either the Batch Item Modification or Batch Item Deletion, columns will only appear if there is in fact data in these fields. IF there is no value in the Source of Acquisition (for example) field, then the column does not appear with a blank value in it. Libraries may want to see all columns with blank data for double checking purposes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8