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

[Bug 13188] Make it possible to configure mandatory patron data differently between OPAC registration and modification
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '19

28 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13188 --- Comment #11 from Séverine Queune <severine.queune(a)bulac.fr> --- (In reply to Magnus Enger from comment #10) > A more or less related problem: If you set password as mandatory in > PatronSelfRegistrationBorrowerMandatoryField it does not show up in the edit > form (there is a separate screen for changing the password), and the edit > form can never be submitted successfully. > > With a new syspref PatronSelfModificationBorrowerMandatoryField it would be > possible to set it as not mandatory in the edit screen. This peculiar problem with password field is very annoying (at BULAC, we experience it since we update in 18.05, was working on 16.11), shouldn't we open a new ticket to solve this specific point, if no one can work the new syspref ? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13188] Make it possible to configure mandatory patron data differently between OPAC registration and modification
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '19

28 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13188 Séverine Queune <severine.queune(a)bulac.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |severine.queune(a)bulac.fr -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 22377] New: Lost fines may not be refunded if another patron has a writeoff for the same item
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '19

28 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22377 Bug ID: 22377 Summary: Lost fines may not be refunded if another patron has a writeoff for the same item Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- To recreate: 1 - Checkout an item to Patron A, backdate the due date and run fines to generate an overdue 2 - Return the item 3 - Checkout the item to Patron B, mark it lost and ensure a fine is generated 4 - In the DB set the date i=on the lost fine to yesterday 5 - Writeoff the fine for Patron A 6 - Return the item 7 - It is no longer lost, but the lost fine is not refunded -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 23633] New: Filter out historical charges by default on a users 'your charges' page
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '19

28 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23633 Bug ID: 23633 Summary: Filter out historical charges by default on a users 'your charges' page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The 'your charges' OPAC page display all charges (paid for or otherwise) that the user has ever had. It's also the page where, if enabled, a user can initiate an online payment. If there's is a large history of paid charges displayed then it can be cumbersome to pick out the charges owed and scroll to the bottom of the page to reach the pay now buttons. I propose we filter the table by default to just outstanding account lines and allow the full view via a button/checkbox. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 23671] New: Elasticsearch shouldn't throw exception on an uppercase subfield identifier
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '19

28 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23671 Bug ID: 23671 Summary: Elasticsearch shouldn't throw exception on an uppercase subfield identifier Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: trivial Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nicolas.legrand(a)bulac.fr Depends on: 23670 MARC 21 specifies a subfield identifier “may be any any lowercase alphabetic or numeric character” (https://www.loc.gov/marc/96principl.html section 8.4.2). It is not that clear for Unimarc or even for ISO 2709 itself. Our catalogue in Unimarc use uppercase alphabetic subfield identifier for items. When we try to index it with Elasticsearch, it throws an exception (well, it tries to, this is fixed by Bug 23670). We think Elasticsearch shouldn't be picky about uppercase alphabetic subfield identifier, especially when Koha permits their creation in the MARC Framework or in the Elasticsearch mapping. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23670 [Bug 23670] Load Koha::Exceptions::ElasticSearch module in Koha::SearchEngine::Elasticsearch -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 23670] New: Load Koha::Exceptions::ElasticSearch module in Koha::SearchEngine::Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '19

28 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23670 Bug ID: 23670 Summary: Load Koha::Exceptions::ElasticSearch module in Koha::SearchEngine::Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: trivial Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nicolas.legrand(a)bulac.fr When your mapping includes an Invalid MARC field expression, it tries to throw an exception with Koha::Exceptions::Elasticsearch::MARCFieldExprParseError. But since Koha::Exceptions::Elasticsearch isn't loaded in Koha::SearchEngine::Elasticsearch, it dies like this: Can't locate Koha/Exceptions/Elasticsearch/MARCFieldExprParseError.pm in @INC (you may need to install the Koha::Exceptions::Elasticsearch::MARCFieldExprParseError module) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '19

28 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|rel_19_11_candidate | --- Comment #181 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I think it's too late now for 19.11 (feature slush this Wednesday), but was so happy to see progress here and would love to see it early on in 20.05. David, can you provide follow-ups for the problems Severine noted? I think we are close to a sign-off. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13897] Use XML files for installer data
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '19

26 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13897 Zeno Tajoli <ztajoli(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|ztajoli(a)gmail.com | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23902] New: Cataloging Search: Add control number to preview
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '19

25 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23902 Bug ID: 23902 Summary: Cataloging Search: Add control number to preview Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: carnold(a)dgiinc.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We would like to see the Control Number (001 field) when we do a cataloging search on page /cgi-bin/koha/cataloguing/addbooks.pl https://paste.pics/658e5727b28b75aea510b908c27faf9a -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 12446] Enable an adult to have a guarantor
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '19

25 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12446 --- Comment #99 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- This will need to update the cleanup routine introduced in bug 17168. -- You are receiving this mail because: You are watching all bug changes.

1 0