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

[Bug 16503] New: Label creator: grouping fields with quotes does not work in layout creator
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '20

19 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16503 Bug ID: 16503 Summary: Label creator: grouping fields with quotes does not work in layout creator Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The description for "Data field" under label-edit-layout.pl shows "Enter a comma separated list of fields to print. You may include any Koha field or MARC subfield. See online help for advanced options ex: barcode, itemcallnumber, title, "050a 050b", 300a Fields homebranch_description, holdingbranch_description, ccode_description, location_description and permanent_location_description show description instead of code." This seems to indicate that grouping fields using quotes, non-comma separated, *should* work: Given an item with the following data: title: Juggling for the complete klutz / author: Cassidy, John. itemcallnumber: JNF 793.8 Cas Using the data fields "title author", itemcallnumber Should yield a CSV export this: "Juggling for the complete klutz / Cassidy, John.","JNF 793.8 Cas" Instead I get this: ,"JNF 793.8 Cas" To replicate: 1/ Create a record using the title, author and itemcallnumber above. 2/ Go to tools > label creator 3/ Add a batch containing the created item 4/ Add a new layout. Click the list fields radio button, and add the fields title, author, itemcallnumber 5/ Export the batch as CSV using the new layout. The resulting file will look like this: "Juggling for the complete klutz /","Cassidy, John.","JNF 793.8 Cas" 6/ Edit the layout, change the field list to "title author", itemcallnumber 7/ Export the batch again, the new CSV file will read ,"JNF 793.8 Cas" The bug was replicated under version 3.23. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 22999] New: Switch two-column templates to Bootstrap grid: Circulation
by bugzilla-daemon＠bugs.koha-community.org 17 Apr '20

17 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22999 Bug ID: 22999 Summary: Switch two-column templates to Bootstrap grid: Circulation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 20654 Target Milestone: --- The circulation (check out) template should be updated to use the Bootstrap grid. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20654 [Bug 20654] Omnibus: Update two-column templates to use Bootstrap grid -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 23236] New: Remove 'its items may still be processed' in action if no match is found
by bugzilla-daemon＠bugs.koha-community.org 17 Apr '20

17 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23236 Bug ID: 23236 Summary: Remove 'its items may still be processed' in action if no match is found Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I think this is only a string bug, but I'd like a developer to make sure nothing happens behind the scenes. When importing records and looking for duplicate records using record matching rules, there is an option if NO match is found to "ignore incoming record (its items may still be processed)". This doesn't make any sense. Where would the items go if there is no match? To reproduce : 1) Go to tools > Stage MARC for import 2) Browse and choose a file and click on Upload file 3) Go to the Look for existing records in catalog? section 4) Open the drop down for Action if no match is found 5) Note that one option says Ignore incoming record (its items may still be processed) This option should only say Ignore incoming record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 21708] New: Editing a record moves field 999 to first in the marcxml
by bugzilla-daemon＠bugs.koha-community.org 17 Apr '20

17 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21708 Bug ID: 21708 Summary: Editing a record moves field 999 to first in the marcxml Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor 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 1) Import or create a new record. 2) Examine the marcxml of that record in the database - the fields are in the correct numerical order. 3) Edit the record - no need to change any data, just save it. 4) Examine the marcxml in the database - the 999 field is now right after leader and before 001. This is due to TransformHtmlToMarc in C4/Biblio.pm, specifically the $param eq 'biblionumber' case, which pushes the param in the array first, and then the sub uses $record->append_field() Perhaps the array should be sorted by field tag before appending the fields? AFAIK, this doesn't really show up anywhere in Koha, but if you ever edit the records via a script using MARC::Record, new fields cannot be easily inserted into correct position. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 17143] New: Popup Notification for decreaseloanhighholds preference
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17143 Bug ID: 17143 Summary: Popup Notification for decreaseloanhighholds preference Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If you have an item that meets the holds requirement by the decreaseloanhighholds preference, but doesn’t get a decrease in the actual checkout period; you still get a popup notification that the high demand feature is being used and the loan period will be decreased. The notification shouldn't populate if the decreased loan period matches or is higher than the original loan period. The current behavior in the system looks at the the number of holds and doesn't take the loan periods with an equal value into consideration when enforcing the preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 17693] New: Add option to export deleted bibs in export_records.pl
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17693 Bug ID: 17693 Summary: Add option to export deleted bibs in export_records.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Currently the export_records.pl script has an option to export a list of deleted items, but not deleted biblios. There are cases where such an export would seem useful (at Aristotle University of Thessaloniki we have been using it for a long time), the data is already kept in the deletedbiblio table, so the enhancement is easy to implement as it only requires a couple lines of code in the export script. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 23488] New: Line wrapping doesn't always respect word order in Patron card creator
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23488 Bug ID: 23488 Summary: Line wrapping doesn't always respect word order in Patron card creator Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: maryse.simard(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org In patron card creator, layouts can define up to three lines of text to print to the card. When the text of a line is too long, wrapping will happen. If the wrapped text contains a word that is repeated at least once in the string, the words in the text can be rearranged, the repeated words being grouped together. To reproduce, I use the following text that I put in a card layout : "one two three one two three one two three one two three one two three one two three one two three one two three" I then export some patron cards using this layout. In the resulting file, the words are all out of order : all of the ones appear first, followed by all the twos and only then the threes. The problem is that wrapping happens by finding the last word that can be cut from the string and putting it in a new line. But, when the word is then removed from the original text, only the first occurrence is removed if it appears more than once. The new last word to be removed from the end of the line is the same word again and again until there is none left. We should make sure to remove the word at the end of the line, exactly where we found it to start with. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 22744] New: 'Do not notify' is really a 'Clear' option
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '20

15 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22744 Bug ID: 22744 Summary: 'Do not notify' is really a 'Clear' option Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- 'Do not notify' in messages sort of hints that messages will be prevented, however, when checked it simply clear the other boxes. Hold notices wil generate print even when nothing is selected, so we shouldn't imply that there is an 'Opt out'/'Do not notify' (see bug 5501 for that) The goal of this bug is to simply rename this option -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 21416] New: 'gr' option missing from ZEBRA_LANGUAGE options in koha-sites.conf
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '20

15 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21416 Bug ID: 21416 Summary: 'gr' option missing from ZEBRA_LANGUAGE options in koha-sites.conf Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P3 Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: arouss1980(a)gmail.com Bug 11927 added a Zebra charmap file (sort-string-utf.chr) for Greek language sorting support and also updated the 'koha-create' script to list 'gr' as an available option to the --zebralang argument. However, the main configuration file in /etc/koha/koha-sites.conf (AKA debian/templates/koha-sites.conf in git) does not list 'gr' as an option for the ZEBRA_LANGUAGE variable. I believe 'gr' should be listed among the other language codes, otherwise those who are unaware of Bug 11927 won't know that such support has been added. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 22943] New: The in_ipset syspref name can be confusing.
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '20

15 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22943 Bug ID: 22943 Summary: The in_ipset syspref name can be confusing. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- In bug 14407 we introduced a new system preference to allow limiting the online self checkout system to an IP or IP Range. The preference introduced, however, is called in_ipset which can be confusing (as for those in the know there is a tool in linux called ipset which isn't related to the original bug). We should therefore rename the system preference to in_iprange to more accurately describe it's function. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28