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

[Bug 21406] New: Not adding author to request can cause JS errors
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '19

06 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21406 Bug ID: 21406 Summary: Not adding author to request can cause JS errors 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: andrew.isherwood(a)ptfs-europe.com If an ILL request does not contain an author, when viewing the ILL requests table, the following errors are displayed by Datatables: DataTables warning: table id=ill-requests - Requested unknown parameter 'metadata_Author' for row 0, column 0. For more information about this error, please see http://datatables.net/tn/4 DataTables warning: table id=ill-requests - Requested unknown parameter 'metadata_Author' for row 358, column 0. For more information about this error, please see http://datatables.net/tn/4 We need better handling of requests without populated author in the JS -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 20040] New: FailedLoginAttempts syspref will lock out users so that they cannot log in unless the syspref is cleared
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '19

06 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20040 Bug ID: 20040 Summary: FailedLoginAttempts syspref will lock out users so that they cannot log in unless the syspref is cleared Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org I think that the FailedLoginAttempts system preference is only meant to be set ifNorwegianPatronDBEnable is set to 'Enable'; my testing is all done with ifNorwegianPatronDBEnable set to 'Disable'. What's happening: Setting FailedLoginAttempts, then logging in with incorrect credentials will lock the account. The login screen says that the account is locked, and no further attempts to log in will work. It is entirely unclear how to unlock the account -- resetting the password does not work, and the lock is not set via borrower debarments, so it can't be disabled there. The only way I was able to re-enable logins for a locked patron was to blank out FailedLoginAttempts. If this is only meant to be used in conjunction with ifNorwegianPatronDBEnable, it shouldn't be settable unless that is enabled. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 20389] New: Indexing fields concatenated
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '19

04 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20389 Bug ID: 20389 Summary: Indexing fields concatenated 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: claire.hernandez(a)biblibre.com I would like to be able to specify multiple subfields to index as a value in a field. The subfields must be concatenated. Example 1: Author in unimarc in an authority: 700 1 $a Bermès $b Emmanuelle I could record a fields in mappings: author: "700a. .700b" I would have in the field indexed: author: "Emmanuelle Bermès" Example 2: in mappings: author: "700b., .700a" would give: author "Bermès, Emmanuelle" With solr, we managed it with indexing plugins. If it is too early for this, we could manage it in mappings configuration maybe. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 16580] New: Explain the link between the autoBarcode preference and the cataloging plugin
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '19

02 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16580 Bug ID: 16580 Summary: Explain the link between the autoBarcode preference and the cataloging plugin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you have the 'barcode.pl' plugin enabled for the barcode field in your MARC framework, but the 'autoBarcode' preference is turned off, the plugin will appear to be active but won't do anything. I think there ought to be text explaining the connection, to be shown both on the system preference itself and when the barcode plugin is selected during framework editing. Or is there a time when one does something without the other? -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 18001] New: LocalHoldsPriority can cause multiple holds queue lines for same hold request
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '19

31 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18001 Bug ID: 18001 Summary: LocalHoldsPriority can cause multiple holds queue lines for same hold request Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If LocalHoldsPriority is enabled, and a record level request has more than one item that could fill that hold, there is a possibility that a holds queue row will be generated for the request for each of the available items! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 19722] New: Add a MaxItemsToDisplayForBatchMod preference
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '19

31 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19722 Bug ID: 19722 Summary: Add a MaxItemsToDisplayForBatchMod preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The tool is setup to run in the background for actual modifications, but displaying the items beforehand can take too long and cause timeouts. We should add a syspref and use similar functionality from batch delete items where one can edit more than is viewed -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 18322] New: Add facets for ccode to zebra
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '19

30 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18322 Bug ID: 18322 Summary: Add facets for ccode to zebra Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: brendan(a)bywatersolutions.com, jonathan.druart(a)bugs.koha-community.org, katrin.fischer(a)bsz-bw.de, marjorie.barry-vila(a)ccsr.qc.ca, nick(a)bywatersolutions.com, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 17169, 18068 Blocks: 18235 If we're going to add it for elasticsearch, it ought to also be there for zebra ;) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17169 [Bug 17169] Add facets for ccode to elasticsearch https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18068 [Bug 18068] Elasticsearch (ES): Location and (home|holding)branch facets mixed https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18235 [Bug 18235] Elastic search - Configurable facets -- You are receiving this mail because: You are watching all bug changes.

1 52

[Bug 17248] New: Koha::AuthorisedValues - Remove GetKohaAuthorisedValueLib
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '19

28 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17248 Bug ID: 17248 Summary: Koha::AuthorisedValues - Remove GetKohaAuthorisedValueLib Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 17216 Blocks: 15799 The subroutine C4::Koha::GetKohaAuthorisedValueLib just retrieves a description (lib) for a given authorised value. We can easily replace it using: Koha::AuthorisedValues->search({ category => $cat, authorised_value => $av })->lib or Koha::AuthorisedValues->search({ category => $cat, authorised_value => $av })->opac_description Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15799 [Bug 15799] Move authorised values related code into Koha::AuthorisedValues - part 2 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17216 [Bug 17216] Add a new table to store authorized value categories -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 21191] New: GDPR: Script to block inactive users (with no successful logins on a defined period)
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '19

25 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21191 Bug ID: 21191 Summary: GDPR: Script to block inactive users (with no successful logins on a defined period) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: vfernandes(a)keep.pt QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Under the auspices of the recently issued European legislation regarding data privacy (GDPR), the Portuguese government has issued a series of mandatory requirements, as well as general recommendations, for software applications that are implemented under the umbrella of public bodies (RCM 41/2018). Since Koha is mostly used by municipalities and universities in Portugal, some of these mandatory requirements need to be address by Koha implementers in Portugal. We believe that this requirement is also useful for the community at large. Here’s a description of the requirement. *** Requirement description *** The application MUST record the time of a user last logged in. It should have a method to inactivate users that haven’t logged into the application for over X number of months (new setting). *** Scope *** Applies to implementations where user authentication is handled by Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 21734] New: 18.05 manual still shows CheckDigit as sys pref
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '19

24 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21734 Bug ID: 21734 Summary: 18.05 manual still shows CheckDigit as sys pref Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org What is done in this situation, when a system preference is removed from a Koha version, do you keep the system preference in the manual or remove it? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2