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

[Bug 23609] New: Tie patron gender to an authorized value
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '24

13 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23609 Bug ID: 23609 Summary: Tie patron gender to an authorized value Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In the interest of allowing greater flexibility, it'd be great to have gender tied to an authorized value so libraries can edit/add/delete options. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[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 23357] New: overdue_notices.pl can send library doubled emails for patrons with no email/sms if both transports enabled
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23357 Bug ID: 23357 Summary: overdue_notices.pl can send library doubled emails for patrons with no email/sms if both transports enabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz In overdue_notices.pl we have a check to avoid sending a patron two notices if they are missing an email address and an sms number, however, we don't apply this check to generating the notice content and so send the library the same info twice -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 23497] New: Notices defaulting to print
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '24

09 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23497 Bug ID: 23497 Summary: Notices defaulting to print Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Why is it that Koha defaults to printing? Shouldn't the default be no notification, and we have to select which notices are printed, if any? Right now, if a patron doesn't have an e-mail selected as the form of notification, the notice defaults to print. I would like to suggest that a print column be added, and if nothing is checked, nothing is generated. Maybe in the notices tab for the patron a place holder could be made saying that patron opted for no notification, or something like that? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 23558] New: REST API: Get an ILL request
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '24

06 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23558 Bug ID: 23558 Summary: REST API: Get an ILL request Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com Method GET /ill_requests/{ill_request_id} https://wiki.koha-community.org/wiki/Illrequests_endpoint_RFC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 22440] New: ILL API response objects inconsistent with other endpoints
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '24

06 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22440 Bug ID: 22440 Summary: ILL API response objects inconsistent with other endpoints Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Target Milestone: --- The response object returned from the /api/vi/illrequest GET route isn't consistent with response objects supplied by other routes, such as the patrons route. We have an RFC for this route here: https://wiki.koha-community.org/wiki/Illrequests_endpoint_RFC Josef has made some initial recommendations on what the properties should be named to make them consistent with other routes. We could do with expanding this RFC to make it complete, including a spec on how object embedding should be done since, to date, this is the only route that does this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 66

[Bug 23557] New: REST API: Add ILL request
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '24

06 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23557 Bug ID: 23557 Summary: REST API: Add ILL request Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com Method POST /ill_requests https://wiki.koha-community.org/wiki/Illrequests_endpoint_RFC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7