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

[Bug 29311] New: Do not allow editing of bibliographic information when entering suggestion from existing bibs
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29311 Bug ID: 29311 Summary: Do not allow editing of bibliographic information when entering suggestion from existing bibs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a patron makes a suggestion from an existing bib, the patron is allowed to edit the bibliographic information in the suggestion. This leads to confusion, since the suggestion is still tied to the original bib. To recreate: - find a record in the OPAC - click Suggest for Purchase - delete the title, author, ISBN, etc that have been pre-populated from the original bib - fill out a suggestion for an entirely different book - submit - go to your purchase suggestion in your account on the OPAC. See the title you entered, observe it links to the bib you started from - go over to the staff side and Accept your suggestion - put your suggestion into a basket - observe your order is for the original bib but your suggestion still shows the new title The simplest answer I see here is to just not allowing editing of those fields when making a suggestion from an existing title. -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 33740] New: Error 500, when editing authority TAG 000 (leader).
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33740 Bug ID: 33740 Summary: Error 500, when editing authority TAG 000 (leader). Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: pablo.joneslobos(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In the Authority module, when entering a new Personal Name Authority record, clicking on the field fills in the default value " nz a22 n 4500", correctly, but when trying to edit the field, the popup window says " An error has occurred! Error 500...". In general, it does not happen with other types of Authority, "Corporate Names", "Geographical Names", "Chronological Term", etc. Tests performed: -Empty browser cookies (Firefox), does not improve the situation. -In a private window, it works "better", open the editor in the pop-up window first, (Personal Authority Sheet). -In Normal window, it loads without error, after loading default fields like 003,005,008, and open to edit field 008. -When it opens, I can make the changes in the editor, and they are applied to the 000 field. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26608] New: Authorities: linked biblios is inconsistent using elasticsearch and QueryAutoTruncate
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26608 Bug ID: 26608 Summary: Authorities: linked biblios is inconsistent using elasticsearch and QueryAutoTruncate Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com Using ES and QueryAutoTruncate systempreference enabled, the count and list of linked biblios is wrong. This is because auto-truncate feature change the query "an:1" to "an:1*". So all biblio linked to an authid like 15, 1042, 11234 match the query. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 32643] New: Send patron a notification of a new OPAC note
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32643 Bug ID: 32643 Summary: Send patron a notification of a new OPAC note Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Staff members can add notes to a patron via "Add message" button in patron details. This can either be an internal message for staff only, or it can also be visible to the patron in OPAC. When visible in OPAC, it would be useful to also notify patrons of the new note through other communication methods, like email or sms. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 15567] Update API to allow multiple holds for the same record
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15567 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 33799] New: Setting default hold type
by bugzilla-daemon＠bugs.koha-community.org 22 May '23

22 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33799 Bug ID: 33799 Summary: Setting default hold type Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With the new grouping option in our holdings, we are now much closer to being able to place different formats in the same record. However, we still need a little work in terms of holds. I can place different formats in the same record, and I can force the holds to specific items, but it may not be the format the patron wants. There are few modifications I would like to see happen: 1) It would be preferable if in the circulation rules, the OPAC item level hold dropdown were changed to multiple choice selections, so we can check if we want to allow any first available, first available in group, or item level, or any combination. 2) There should be a staff side version of these choices as well. We should be able to control the staff's choices as well. 2) We should have the option of pre-selecting an item or not. There needs to be a way to make the patron make a selection, rather than once being made for them. Particularly if patrons might want to get a first available in a group rather than a specific item. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 32357] New: Set borrower_message_preferences.days_in_advance default to NULL
by bugzilla-daemon＠bugs.koha-community.org 22 May '23

22 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32357 Bug ID: 32357 Summary: Set borrower_message_preferences.days_in_advance default to NULL Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org days_in_advance currently defaults to 0, but it should default to NULL because all but one entry in message_attribute has takes_days=1 making it the exception and not the default. Current column default 0 is already ignored by C4::Members::Messaging::SetMessagingPreference, see https://github.com/Koha-Community/Koha/blob/8c367775470fcecdda54e28270b05d9… , so we should also make NULL default at database level instead. Blocking Bug 18595 (because without this change some tests there will fail unless we replicate the misuse of default values) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 32766] New: Update plugin unimarc_field_116.pl fields
by bugzilla-daemon＠bugs.koha-community.org 22 May '23

22 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32766 Bug ID: 32766 Summary: Update plugin unimarc_field_116.pl fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Update unimarc fields for plugin unimarc_field_116.pl to more precise labels for understanding and translation -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 33336] New: Use a dedicated column for plugin status in plugins table
by bugzilla-daemon＠bugs.koha-community.org 22 May '23

22 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33336 Bug ID: 33336 Summary: Use a dedicated column for plugin status in plugins table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In plugins table plugins/plugins-home.pl the status enable/disable is with the name, styled as a label. With new interface ENABLED is yellow, this looks weird. Also I bet this is bad for accessibility. I propose to move this info to a dedicated column. -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 32992] New: Move background worker script to misc/workers
by bugzilla-daemon＠bugs.koha-community.org 22 May '23

22 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32992 Bug ID: 32992 Summary: Move background worker script to misc/workers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On bug 32594 we are adding a new worker, dedicated to Elastic indexing. We should have a common place for workers, and we agreed on misc/workers -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15