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

[Bug 26183] New: UpdateItemWhenLostFromHoldList should be limited in scope
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '23

22 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26183 Bug ID: 26183 Summary: UpdateItemWhenLostFromHoldList should be limited in scope Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff Client 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 UpdateItemWhenLostFromHoldList lets one update any value in the items table when cancelling a hold from the Holds to Pull list. That includes things that aren't normally editable. For instance, one can use it to change itemnumbers. It doesn't seem likely anyone will set it up to do so, but the potential damage is pretty severe. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 26178] New: When executing a title search in the OPAC for titles that contain "/" in the main title, the search results do not display the entire title. Is "/" a "stop term"?
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '23

22 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26178 Bug ID: 26178 Summary: When executing a title search in the OPAC for titles that contain "/" in the main title, the search results do not display the entire title. Is "/" a "stop term"? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: msomers(a)bridgew.edu QA Contact: testopia(a)bugs.koha-community.org Created attachment 107953 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=107953&action=e… Bug report on using backslash in title search -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 26144] New: Due date should not be subtracted from billable days with FinesCaendar on
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '23

22 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26144 Bug ID: 26144 Summary: Due date should not be subtracted from billable days with FinesCaendar on 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 To recreate: - set finesCalendar to ignore the calendar - set circ rules to charge $1 per day, no grace period - set library as closed yesterday on calendar - check item out with due date of yesterday - run fines.pl - see patron has $1 fine - change finesCalendar to use the calendar - check item out with due date of yesterday - run fines.pl - see patron has no fine When we count billable days for the fine, we don't count the due date itself. So we should not count the due date when counting holidays to be subtracted from the billable days. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 24458] New: OPAC search results don't use Koha::Filter::MARC::ViewPolicy
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '23

22 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24458 Bug ID: 24458 Summary: OPAC search results don't use Koha::Filter::MARC::ViewPolicy Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org With https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15870, we started enforcing the bibliographic framework visibility in the OPAC. However, we're not using this for search results, which means that hidden fields could come through very visibly. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 17453] New: Inter-site holds
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '23

22 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17453 Bug ID: 17453 Summary: Inter-site holds Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Circulation 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: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 46

[Bug 20517] New: Use the "sort bin" field in SIP2 Checkin Response
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '23

22 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20517 Bug ID: 20517 Summary: Use the "sort bin" field in SIP2 Checkin Response Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com The SIP2 Checkin Response (10) can have a "variable-length optional field" for "sort bin", labelled "CL". In the description of the SIP2 protocol, this field is described as follows: "sort bin - CL - variable-length field. This field should contain a bin number that indicates how the items should be sorted. The maximum practical number of sort bins for a patron using 3M SelfCheck system is probably only 3 or 4, but many digits are allowed to accommodate some sort of fantastic sorting device using a hierarchical bin numbering scheme." I have a customer who wants to use this field to display messages on the screen of self service machines that tell users to put items in a separate bin based on itemtype, location etc. The idea is to add a syspref that can contain something like this: itemtype:ILL:1 location:CLOSEDSTACKS:2 - The first field is an item field. - The second field is a value to look for in the given item field - The third field is the value given to the CL field in the SIP2 Checkin Response if the value in the second field matches the item on hand. It should also be possible to set the CL field for items that need to be transferred after they have been returned, that is for items that are returned at another library than the homebranch. This will probably be another syspref. If the returned item needs to be transferred to the homebranch, CL is set to the value of the syspref. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 53

[Bug 25613] New: Broken workflow on CAS login with wrong permissions
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '23

22 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25613 Bug ID: 25613 Summary: Broken workflow on CAS login with wrong permissions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org If you set to login through CAS, and don't have enough permissions for the admin interface, you get into a loop in which you cannot re-try with other credentials, unless you clean the CAS cookies. This also happens when the user doesn't match any user in Koha's DB. This can be very problematic. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 26728] New: Lifted restrictions will only show on checkouts but not on details tab
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '23

21 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26728 Bug ID: 26728 Summary: Lifted restrictions will only show on checkouts but not on details tab Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To test: - Add several restrictions with dates in the past - Verify they show when editing the patron - Verify they show on checkouts tab > Restrictions - Verify they DON'T show on the details tab > Restrictions I initially started testing this because of bug 26053 which is asking for having a clear visual distinction between active and inactive (date in the past) restrictions. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 24974] New: Add Elastic Search to the Manual
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '23

21 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24974 Bug ID: 24974 Summary: Add Elastic Search to the Manual Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We need to add some documentation about Elastic Search in the Manual. Also in Administration for Search Engine Configuration. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24274] New: New installations should not contain field 01e Coded field error (RLIN)
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '23

20 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24274 Bug ID: 24274 Summary: New installations should not contain field 01e Coded field error (RLIN) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic 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 Field 01e comes from the RLIN utility. It is not a standard MARC21 field. Previously, it triggered the warning (in addbiblio.pl) Argument "01e" isn't numeric in numeric ne (!=) This warning was addressed on bug 21172. It is the only non-numeric field tag in Koha; and it does not belong there. We should remove it. This report only deals with new installations. So it fixes the SQL installer files. It does NOT include a database revision for existing installations. You never know if someone used the field somehow ;) See also (question of Magnus in 2009! goto 09:55 hours): http://irc.koha-community.org/koha/2009-06-18 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15