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

[Bug 35815] New: [Elasticsearch] Fix indexing of bibliographic records when items are deleted
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '24

04 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35815 Bug ID: 35815 Summary: [Elasticsearch] Fix indexing of bibliographic records when items are deleted 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Bibliographic records do not always get reindexed in Elasticsearch when items are batch deleted. This means that search results show an inaccurate number of remaining items. To reproduce: 1. Spin up a Koha instance in your testing environment which uses Elasticsearch 2. Create a new bibliographic record and add three items to it 3. Do a search for your record that will return multiple results, so that you are shown the search results. Confirm that the search results shows three items are attached to the record. 4. Go to the record and select the checkbox for an item. 5. Click the link to Delete selected items. Confirm this again on the next page. 6. Confirm the job is enqueued then completed. It should say your item has been deleted. 7. Do a search for your record again so that you see it in the search results. Notice the number of items has not been updated - it still says three --> BUG -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 13888] 'Lists' permission should allow/disallow using the lists module in staff
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '24

04 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13888 Andrew Auld <andrew.auld(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew.auld(a)ptfs-europe.com | |, katrin.fischer(a)bsz-bw.de, | |martin.renvoize@ptfs-europe | |.com --- Comment #3 from Andrew Auld <andrew.auld(a)ptfs-europe.com> --- I would like to bump this, as turning off lists permissions for a staff user doesn't seem to stop the lists button from appearing on the home page, or stop the user from accessing and managing lists. Has this bug been forgotten about? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14806] Action Log for Modifying borrower messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '24

04 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14806 Ray Delahunty <r.delahunty(a)arts.ac.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |r.delahunty(a)arts.ac.uk -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 26299] New: Help text for OPAC SMS number should be less North American-centric
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '24

04 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26299 Bug ID: 26299 Summary: Help text for OPAC SMS number should be less North American-centric Change sponsored?: --- Product: Koha Version: unspecified 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 At the moment, the help text on opac-messaging.pl is "Please enter numbers only. (123) 456-7890 would be entered as 1234567890." The first style is a North American style, which looks strange to people from other countries like Australia where we frequently format non-mobile phone numbers like 02 5555 5555 or mobile numbers like 0455 555 555. We should use a more generic style like we do on memberentry.pl when we say "SMS number should be in the format 1234567890 or +11234567890" -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 30026] New: International Phone Number Not supported for SMSAlert
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '24

04 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30026 Bug ID: 30026 Summary: International Phone Number Not supported for SMSAlert 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: florian.bontemps(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The SMSNumber field used when registering a phone number for SMS alerts does not work with some international number formats. Currently, the format 00 AAAXXXXXXXXX (A = country indicator between 1 and 3 digits, X = regular digits) is not supported. While the format +AAAXXXXXXXXX can sometimes work, some network providers don't accept the latter format. These formats are very used in Europe for instance (Germany, Sweden, France, etc) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 30758] New: Handle Google Books API requests for OPACSuggestionAutoFill on server side
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '24

03 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30758 Bug ID: 30758 Summary: Handle Google Books API requests for OPACSuggestionAutoFill on server side Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 14242 Bug 14242 allows to use the Google Book API to pull in information about a book from the ISBN or similar. At the moment the request is done in the browser, but for privacy concerns it would be better if the request could be made from the Koha server instead. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14242 [Bug 14242] Use ISBN-field to fill out purchase suggestions using Google Books API -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 26130] New: opacbookbag 'Cart' confuses patrons - add optional name alternatives?
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '24

03 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26130 Bug ID: 26130 Summary: opacbookbag 'Cart' confuses patrons - add optional name alternatives? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: eb(a)efdss.org QA Contact: testopia(a)bugs.koha-community.org This is in reference to the 'Cart' - short term list making facility in the OPAC. It is useful for making lists, to download a bibliography or to print out, or e-mail. But especially now that our building is closed, patrons are thinking that it's a way to order materials (similar to holds, which we don't use). 'Cart' has transactional implications - people are used to seeing it in online shopping sites. If you put something into a cart and finish the ordering process, you expect to receive it. While 'Cart' may work in some libraries, it doesn't work everywhere. It's also ambiguous with cart used elsewhere in Koha. Would it be possible to either have a short pull down menu of names for this feature in the opacbookbag setting, or the ability in System Preferences to name it ourselves, or, change the name to something more logical. Some ideas: 'My List' 'Temporary List' 'My Shelf' and whatever happened to 'Book Bag'? -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 9596] Allow longoverdue.pl to be configured by library
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '24

03 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9596 HKS3 Tadeusz Sośnierz <tadeusz(a)sosnierz.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #162250|0 |1 is obsolete| | --- Comment #12 from HKS3 Tadeusz Sośnierz <tadeusz(a)sosnierz.com> --- Created attachment 167343 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=167343&action=e… Bug 9596: Add branch and skip-branch options to cronjobs/longoverdue.pl This script doesn't seem to be included in cron files by default. This change is to allow script parameters to effect only certain branches. This allows the script to be added multiple times to a cron file with different settings for different branches. Test plan: 1. apply patch 2. identify two books at different branches the same number of days overdue. 3. run the longoverdue.pl script specifying one of the branches in the --branch command line parameter. i.e. koha-shell -c 'misc/cronjobs/longoverdue.pl --branch branch_code --lost 60=2 --maxdays=61 --confirm' instance_name 4. observe that the book at the specified branch has been or would be affected by the script while the other book is not. Signed-off-by: Tadeusz „tadzik” Sośnierz <tadeusz(a)sosnierz.com> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 9596] Allow longoverdue.pl to be configured by library
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '24

03 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9596 HKS3 Tadeusz Sośnierz <tadeusz(a)sosnierz.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 8461] Block returns of withdrawn items show as 'not checked out'
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '24

03 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8461 --- Comment #21 from Andrii Nugged <nugged(a)gmail.com> --- UX issue, which became very annoying for our customers, as raised by librarians: They often "return again" sometimes after SIP to check, and obviously (and it's correct behaviour) the system says for them, "Item was not checked in", but they become confused very, thinking that the item wasn't checked in by SIP (sic!) :). We should make a more straightforward message so as not to confuse librarians. Saying something like, for example: "Item was not checked in because it is already checked in". -- You are receiving this mail because: You are watching all bug changes.

1 0