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

[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 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

[Bug 21559] New: Rules for automatic framework codes
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '24

11 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21559 Bug ID: 21559 Summary: Rules for automatic framework codes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Allow setting rules in a system preference, what framework code should be automatically set for biblio, based on the MARC record fields. Does not affect anything if the MarcToFrameworkcodeAutoconvert system preference rules aren't used. The "Default" framework is always overridden, if the rules match, but some other framework chosen by you is always used. Explanation of the rule format: ------------------------------- The syspref is YAML, with a specific format: - <field> <value>: <frameworkcode> If the <field> in the record contains <value>, the <frameworkcode> is used for the record. <field> is one of: "xxx" (field xxx in the MARC record) "xxx/yy" (field xxx, character location yy) "xxx/yy-zz" (field xxx, character locations yy-zz) "xxx$v" (field xxx, subfield v) Fields can be combined with plus-sign, then the field values have plus-sign between them. The field-rules are checked in order from top to bottom, and the first rule with a matching value is used. If the (sub)field has been repeated in the MARC record, only the first matching (sub)field is checked. If none of the rules match, the framework code is not changed. Example: - 008/35-37 + 000/06: fin+a: BKSFIN - 000/06: a: BKS c: MU e: MP This would make record with 000/06 = "a" AND 008/35-37 = "fin" use the BKSFIN framework, and any other record with 000/06 = "a" use BKS, 000/06 = "c" would be MU, and 000/06 = "e" would give MP -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 20588] New: Elasticsearch - Apply dataTable on search fields and mapping tables
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20588 Bug ID: 20588 Summary: Elasticsearch - Apply dataTable on search fields and mapping tables Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com Apply dataTable on search fields and mapping tables to be able to sort and filter data. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 20388] New: Elasticsearch - Ability to add index from UI
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20388 Bug ID: 20388 Summary: Elasticsearch - Ability to add index from UI Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com Currently indexes only coming from mapping.yaml. We need to add some using UI (admin/searchengine/elasticsearch/mappings.pl) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 213

[Bug 18194] New: Elasticsearch should be able to add new indexes
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18194 Bug ID: 18194 Summary: Elasticsearch should be able to add new indexes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 14899 added a configuration page for elastic search indexes. It would be nice to allow for the addition/deletion of indexes as well as their configuration -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 19942] New: Children's search interface
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '24

04 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19942 Bug ID: 19942 Summary: Children's search interface Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Would like to see an alternative OPAC search for patrons geared towards children. Something like this: http://www2.hampton.lib.nh.us:8080/kids?config=default#/categories It would be easy enough to customize searches, but it would be great to be able to customize a background, and add big buttons to the search topics. You will notice that the general search bar at the top limits to children's materials, and the layout of the results is EXTREMELY kid friendly. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 19518] New: Document per-site .psgi files
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19518 Bug ID: 19518 Summary: Document per-site .psgi files Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: magnus(a)libriotech.no Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org koha-plack uses /etc/koha/plack.psgi by default, but it can also use /etc/koha/sites/${instancename}/plack.psgi if one is present. This should be documented in the manpage of koha-plack and the usage embedded in the script. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 21359] New: Add RDF support to OAI-PMH harvester
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '24

02 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21359 Bug ID: 21359 Summary: Add RDF support to OAI-PMH harvester Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The OAI-PMH harvester is set up to import only MARC records into Koha. The goal of this enhancement would be to allow RDF records to be imported into Koha as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 21893] New: Batch Modify button in report with itemnumber only includes titles in first page of results
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '24

29 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21893 Bug ID: 21893 Summary: Batch Modify button in report with itemnumber only includes titles in first page of results Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 19233 added the ability to push report results into item batch modification when the report includes a column of itemnumbers. However, only items on the first page of item results will be pushed to batch modification -- if the report results include 1200 items and the report page is set to display 1000 rows per page, only the first 1000 items will be batch modified. Koha is clear that it's only modifying those 1000 items, but it still creates extra work, especially since the Rows Per Page dropdown on report results doesn't include an option for All. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4