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

[Bug 33066] New: We need a KohaTable Vue component
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33066 Bug ID: 33066 Summary: We need a KohaTable Vue component Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Depends on: 23991 The way we deal with DataTables in Vue component is not nice, especially when we need to add buttons/link in the cell and interact with the rest of the Vue app from there. When I started to work on Vue last year there was no good solution from DataTables, now there is a Vue component. It is not perfect, you still cannot add Vue component in the DT component, but it brings something to follow. Agustin implemented something on theke/import_source_vue, but he went too far, and it will need to rewrite the whole ERM module. Additionally he didn't provide a solution that has the same features as what we have now. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23991 [Bug 23991] Move SearchSuggestion to Koha::Suggestions -- You are receiving this mail because: You are watching all bug changes.

1 159

[Bug 20511] New: Seasonal prediction just in the staff language
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20511 Bug ID: 20511 Summary: Seasonal prediction just in the staff language 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: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com The seasonal (season, day and monthn) prediction it doens't change according the locale defined in the patterns, the pattern uses always the language of the staff user interface. If you create a pattern with staff user language in spanish, it doesn't matter you configure the locale.. the serialq it will be in spanish. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 45

[Bug 21173] New: Run auto item modifications by age every hour and set the item age unit to hours
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21173 Bug ID: 21173 Summary: Run auto item modifications by age every hour and set the item age unit to hours Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Make auto item modification by age cronjob run more often than once daily. Setting this cronjob to run every hour will be set in the /etc/cron.hourly/koha-common. However 2 further changes to the automatic item modification tool to make an hourly running cronjob useful. 1. Be able to set the age of the item in hours not just days. This is so an hourly cronjob has items to alter because items will exceed the age limit more frequently than if the item age is in hours. 2. Give the user the choice of what the age starting point (time from which the age of the item is calculated) used in the cronjob is. The two possible age starting points that users have to choose between are: * Item creation (this is the age starting point in master currently) * Item last altered This is so items whic have been in the catalogue for a while can still be affected by the automatic item modification by age cronjob. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62

[Bug 28445] New: Use the task queue for the batch delete and update items tool
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '24

23 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28445 Bug ID: 28445 Summary: Use the task queue for the batch delete and update items tool 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 22417 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 [Bug 22417] Add a task queue -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 164

[Bug 31645] New: flatpickr - update coding guidelines
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '24

21 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31645 Bug ID: 31645 Summary: flatpickr - update coding guidelines 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: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org The coding guidelines need updating to reflect that we are now using flatpickr instead of jQueryUI Datepicker. Wiki link: https://wiki.koha-community.org/wiki/Coding_Guidelines -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 33853] New: Error upgrading database schema
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '24

20 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33853 Bug ID: 33853 Summary: Error upgrading database schema Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: afrane55(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I tried Upgrading to 20.11.05.010 and database schema fails to upgrade with : Upgrade to 22.11.05.010 [12:59:19]: Bug 33489 - Add indices to default patron search fields ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: BLOB/TEXT column 'middle_name' used in key specification without a key length at /usr/share/koha/lib/C4/Installer.pm line 743 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 22140] New: More use of EasyAnalyticalRecords pref
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '24

19 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22140 Bug ID: 22140 Summary: More use of EasyAnalyticalRecords pref Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- Like Bug 20702 defined GetHostItemsInfo does nothing if EasyAnalyticalRecords pref is disabled, there are other places where code must be dependant on this pref. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 27683] New: Bind results of GetAnalyticsCount to the EasyAnalyticalRecords pref
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '24

19 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27683 Bug ID: 27683 Summary: Bind results of GetAnalyticsCount to the EasyAnalyticalRecords pref Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl C4::Items::GetAnalyticsCount is part of the easy analytics feature. Like Bug 20702 make early return when the system preference EasyAnalyticalRecords is disabled. Actually it may block an item deletion for wrong reason. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 31570] New: Move patron consent title/description to Additional contents
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '24

19 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31570 Bug ID: 31570 Summary: Move patron consent title/description to Additional contents Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Follow-up for 31503. This needs a bit more flexibility in AC. Like bug 31509? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 20380] New: Email consent patron opt-in tracking for anti-spam legislation
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '24

19 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20380 Bug ID: 20380 Summary: Email consent patron opt-in tracking for anti-spam legislation Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: arm(a)hanover.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com An email consent opt-in field is something that many libraries need to accommodate, with recent legislation in US, Europe, and Canada (which may be the most strict yet). Please comment / add suggestions. Useful features would be: - Email Consent field with Authorised Values drop down allowing multiple choices to allow for different legislation e.g. Yes/No, radio button or tick box, - If Yes, then mandatory date from calendar picker - Preference to make this mandatory/non mandatory for new patron and/or at patron renewal (if mandatory it would need Yes/No rather than radio/tick box) - Preference to set mandatory/non-mandatory for OPAC self-registration (with "Yes I consent..." opt-in wording) - Ability to export data (SQL report?) based on consent choices and consent date or timestamp (for upload to mailer program) Also nice to have: - Additional separate library-set categories for Yes to receive library messages, library newsletter, new titles list, book club updates, library events etc. (each with y/n, tick box...) - Timestamp recorded when any consent field changes (to yes or from yes to no). The date picker might be enough for initial consent but legislated requirements may vary in different countries. Libraries are using 'additional attributes' as a workaround but lack the date recorded (or timestamp) for changes to the consent status, and ability to differentiate permission for core library service messages and news/marketing messages. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15