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

[Bug 18398] New: CHECKIN/CHECKOUT/RENEWAL don' t use AutoEmailPrimaryAddress but first valid e-mail
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18398 Bug ID: 18398 Summary: CHECKIN/CHECKOUT/RENEWAL don't use AutoEmailPrimaryAddress but first valid e-mail Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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 If the system preference AutoEmailPrimaryAddress is set to alternate or work this e-mail addresses should be used to send out all emails. This works for most notices, but sadly not for CHECKIN, CHECKOUT and RENEWAL notices. http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=C4/Message.pm;hb=… sub _to_address is hardcoded to use the first e-mail field that is set in the patron record. It should follow the AutoEmailPrimaryAddress setting instead. Bug 12802 fixed it, but it's a new feature. Woudl still be good to fix this especially for stable releases. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 31695] New: Type standard number is missing field ci_raw in field_config.yaml
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31695 Bug ID: 31695 Summary: Type standard number is missing field ci_raw in field_config.yaml Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com In Elasticsearch fields config field_config.yaml, default type as a field 'ci_raw'. This is used for exact search. This field is missing for type standard number 'stdno'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 32301] New: Show correct defaultSortField in Staff Client Advanced Search
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32301 Bug ID: 32301 Summary: Show correct defaultSortField in Staff Client Advanced Search Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: wainuiwitikapark(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 144096 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144096&action=e… Sort by option in Staff Client Advanced Search The defaultSortField system preference doesn't seem to affect the Staff Client Advanced Search, it still shows 'relevance' as the sort field whichever option you use in the syspref. However, when you submit the search it does in fact search by the value of the syspref. Need to: - In the advanced search in the staff client, display the correct default "sort by" option that is chosen in the defaultSortField system preference -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 27513] New: Add description to Reports page
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27513 Bug ID: 27513 Summary: Add description to Reports page Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: christofer.zorn(a)ajaxlibrary.ca QA Contact: testopia(a)bugs.koha-community.org Hello! Is it possible to add the report Notes field (which appears on the Edit and results page) to the parameters page? As an Admin, I can see the details of the notes and remember what the report does and why, but for the normal user, there might be beneficial notes or reminders that can be put there (i.e. This report runs for the last month, or last two years). Not a huge change, but could be helpful. Thanks Christofer -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[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 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 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 31212] New: Datelastseen should be a datetime
by bugzilla-daemon＠bugs.koha-community.org 19 May '23

19 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31212 Bug ID: 31212 Summary: Datelastseen should be a datetime Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This field should be updated to be a datetime field and the interface adapted to display the full date and time to help librarians track items -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 71

[Bug 23450] New: Display issue and subscription price for each issue in subscription tab of /catalogue/detail.pl
by bugzilla-daemon＠bugs.koha-community.org 19 May '23

19 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23450 Bug ID: 23450 Summary: Display issue and subscription price for each issue in subscription tab of /catalogue/detail.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 32373] New: Show Date of Restriction on Patron Screen
by bugzilla-daemon＠bugs.koha-community.org 19 May '23

19 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32373 Bug ID: 32373 Summary: Show Date of Restriction on Patron Screen Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: smhodson123extra(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 144337 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144337&action=e… Photo of patron account with restriction and flags (where I'd love to see the date they were placed) It would be nice to see the date a restriction was placed, without having to go in and view the restrictions. We are planning to add a more detailed message about the restriction, so it would be nice to be able to look for the date without having to leave the page. It would also be nice to get a date for when the lost card and gone--no address flags were added. (See attached photo.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48