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

[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 34266] New: Item type should not default to biblio itemtype if item-level_itypes is set
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '23

22 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34266 Bug ID: 34266 Summary: Item type should not default to biblio itemtype if item-level_itypes is set Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Cataloging Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When cataloging a new item, a subfield linked to the authorized value "itemtypes" will default to its biblio itemtype. But when the system preference item-level_itypes is set we don't want that. We often use a different authorized value category for biblioitems.itemtype so the values stored there are not appropriate as a default for items.itype. I suggest that Koha uses biblioitems.itemtype as a default only if item-level_itypes is disabled -- You are receiving this mail because: You are watching all bug changes.

1 39

[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 29093] New: Article requests: Checkbox for table of contents
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '23

22 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29093 Bug ID: 29093 Summary: Article requests: Checkbox for table of contents Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If you allow copying or scanning parts of books, a very common question is: I would like to receive a copy/scan of the table of contents. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[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 34117] New: Duplicate patron sets dateenrolled incorrectly
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '23

21 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34117 Bug ID: 34117 Summary: Duplicate patron sets dateenrolled incorrectly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When duplicating a patron, the new patron's registration date on memberentry.pl defaults to a date that is current date + the enrollment period for the category of the patron being duplicated. The registration date should simply default to today's date. To recreate: - have or make a patron - duplicate that patron - on the memberentry page for your new patron, before you save them, scroll down to Registration Date and see that it's defaulting to a date in the future -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[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 33989] New: Inventory tool performs unnecessary authorized value lookups
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '23

20 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33989 Bug ID: 33989 Summary: Inventory tool performs unnecessary authorized value lookups Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org The inventory tool will look up the authorized value description for location, notforloan, itemlost, damaged, and withdrawn for every single barcode - even if it doesn't need to show this data to a user. By only performing these lookups when a user will view this data (ie for items that appear in the "results"), we gain enormous speed improvements. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[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