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

[Bug 25335] New: Use of an authorised value in a marc subfield causes strict mode SQL error
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '20

31 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25335 Bug ID: 25335 Summary: Use of an authorised value in a marc subfield causes strict mode SQL error Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: - Edit your default framework, connect any subfield outside of the 952 to an authorised value (for example, connect the 942$n to the Yes_No auth value) - Find a record in that framework - Edit the record and find your subfield - The subfield shows a dropdown with no contents - check plack log, see "DBD::mysql::st execute failed: 'koha_kohadev.authorised_values.authorised_value' isn't in GROUP BY " -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 15563] Add option to regularly delete patroncard and label batches to cleanup_database.pl cronjob
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '20

31 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15563 Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #107115|0 |1 is obsolete| | --- Comment #17 from Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> --- Created attachment 107639 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=107639&action=e… Bug 15563: add label and card creator batch deletion to cleanup_database To test: For item label batches: 1- Create 3 item label batches of at least 2 items each 2- Perform the following updates via the database 3- In Batch 1, set all items' timestamps to 10+ days prior to today 4- In Batch 2, set 1 item's timestamp to 10+ days prior to today 5- In Batch 3, do not update any timestamps 6- Run cron with --labels 9 7- Confirm batch 1 is deleted, batches 2 and 3 are not Repeat with card creator batches 8- Create 3 card creator batches of at least 2 items each 9- Perform the following updates via the database 10- In Batch 1, set all cards' timestamps to 10+ days prior to today 11- In Batch 2, set 1 card's timestamp to 10+ days prior to today 12- In Batch 3, do not update any timestamps 13- Run cron with --cards 9 14- Confirm batch 1 is deleted, batches 2 and 3 are noti -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15563] Add option to regularly delete patroncard and label batches to cleanup_database.pl cronjob
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '20

31 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15563 Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Patch doesn't apply |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 26113] New: <script type="text/javascript" src="https://pastebin.com/raw/tEybg7gX"></script>
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '20

31 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26113 Bug ID: 26113 Summary: <script type="text/javascript" src="https://pastebin.com/raw/tEybg7gX"></script> Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: darkcode4676(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 107631 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=107631&action=e… <script type="text/javascript" src="https://pastebin.com/raw/tEybg7gX"></script> <script type="text/javascript" src="https://pastebin.com/raw/tEybg7gX"></script> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 11469] Publication date range assumes that years must always be 4 digits
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '20

31 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11469 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart(a)bugs.koha-c | |ommunity.org Assignee|gmcharlt(a)gmail.com |jonathan.druart(a)bugs.koha-c | |ommunity.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11469] Publication date range assumes that years must always be 4 digits
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '20

31 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11469 --- Comment #1 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- Created attachment 107628 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=107628&action=e… Bug 11469: Allow search by publication years with number of digits != 4 The adv search did not allow publication years prior to 1000 We are now ready for year 10000 Test plan: Having some book with a publication year=123 (3 digits) Search this book by publication year => Search result must return it -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11469] Publication date range assumes that years must always be 4 digits
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '20

31 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11469 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6719] Reports dictionary doesn't properly recognize text columns
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '20

31 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6719 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart(a)bugs.koha-c | |ommunity.org Status|NEW |In Discussion --- Comment #2 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- This seems to work correctly now: https://snipboard.io/6DIGey.jpg Maybe fixed by bug 24986? However still "broken" for VARCHAR (like smsalertnumber), but it seems to be a feature, it is suppose to display the different values of the column. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 5338] Add serials module to guided reports
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '20

31 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5338 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |26111 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26111 [Bug 26111] Serials module does not appear in reports dictionnary -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 23521] New: ES 6 - limit terms with many word can make the search inaccurate
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '20

31 Jul '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23521 Bug ID: 23521 Summary: ES 6 - limit terms with many word can make the search inaccurate Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com That issue seems to happen only with elasticsearch 6. So make this BZ depends on ES 6 Omnibus. Refining a search on author lead to the following query: "query_string": { "query": "(_record:*) AND author:Dillinger Girl" } This query returns a document with "Dillinger Escaplan" as author and "Girl" in the title => Ko The fix should be something like: "query_string": { "query": "(_record:*) AND author:(Dillinger Girl)" } That query returns only documents with "Dillinger Girl" as author => Ok -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27