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

[Bug 20722] New: Searching only for an ITEMTYPECAT itemtype is impossible
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '20

19 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20722 Bug ID: 20722 Summary: Searching only for an ITEMTYPECAT itemtype is impossible Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Searching for only the itemtype usually works, but not for itemtypes that are actually ITEMTYPECAT categories grouping several itemtypes together. In this case you will need to add a second search criteria for the search to work. Only searching for the group will return you to the advanced search page. To test: - Create an entry for the ITEMTYPECAT authorised value category. Make sure to fill in the OPAC description. - Go to administration > itemtypes and add the new category to 2 item types. - Go to the OPAC and check that the advanced search shows your new itemtype group instead of the individual itemtypes. - Check the checkbox and Search. - You will be returned to the advanced search page without error. - Search for another ungrouped itemtype, it will return correct search results. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 17531] New: Search categories for itemtypes broken
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '20

19 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17531 Bug ID: 17531 Summary: Search categories for itemtypes broken Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The feature introduced with bug 10937 appears to be broken on current master. You can add a search category and the display on the advanced search page is correct, but the search won't return any results. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 17362] New: Patron import overwrite adds debarments
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '20

19 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17362 Bug ID: 17362 Summary: Patron import overwrite adds debarments Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org When importing patrons via tools, if overwrite is chosen and there is a debarred column with 1, the debarments add up with every import. Might be related to bug 15010. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 17000] New: Patron Modification log access permission
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '20

19 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17000 Bug ID: 17000 Summary: Patron Modification log access permission Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: ed.veal(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com You can only see patron modification log when viewing a patron record if you have one or both of the “parameters Manage Koha system settings (Administration panel)” permissions. This is good information for the circulation staff to be able to access. Ed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 16970] New: In OPAC Search results, <Limit to current available items > hides a record if some of its items are available and others unavailable
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '20

19 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16970 Bug ID: 16970 Summary: In OPAC Search results, <Limit to current available items> hides a record if some of its items are available and others unavailable Change sponsored?: --- Product: Koha Version: 3.22 Hardware: PC OS: Windows Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: thysia(a)live.com QA Contact: testopia(a)bugs.koha-community.org This is a misleading bug for users on OPAC, as they can think that a book is not currently available when it has still available items. If we cannot solve this bug, it would be better not to give this feature. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 11677] Limit to Only items currently available for loan or reference not working
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '20

19 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11677 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thysia(a)live.com --- Comment #44 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- *** Bug 16970 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23900] New: Label maker cannot concatenate database fields
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '20

19 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23900 Bug ID: 23900 Summary: Label maker cannot concatenate database fields Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The manual explains that one can use double quotes when listing fields for one's label layout to make two or more values concatenate onto a single line in one's label. >From https://koha-community.org/manual//18.11/en/html/tools.html#layouts: "You can also enclose a whitespace-separated list of fields to concatenate on one line in double quotes, for example “099a 099b” or “itemcallnumber barcode”. Testing this on both 18.11 and 19.05, this works for MARC fields but not for database fields. To test: - define a label layout with this field list: "100a 245s","enumchron copynumber" - find or create a record with values for all of those fields - generate a label for that record - the 100a and 245s successfully display on one line - the enumchron and copynumber do not display at all -- You are receiving this mail because: You are watching all bug changes.

1 23

[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 15272] aqbookseller addresses are combined into "physical address" field
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '20

19 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15272 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA --- Comment #15 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I am not sure about this approach goes in the right direction. I wonder if it wouldn't be better to split the information into multiple fields in the GUI instead, making it match how we handle addresses for patrons and libraries. Pros: - Allows more than 4 lines in addresses - Doesn't lose data without notifying the user - Makes physical and postal address consistent Cons: - Special handling is needed in HTML notices to keep line breaks - Notices: Harder to parse the address if you want different formatting. Probably possible with TT, but much more complex. Existing notices will have be updated after update or break. - Reports: Existing reports will be broken and it will be much harder to report on specific information. Example: a report on delivery time of vendors in and outside the country. - CSV export: People using serial letters or other ways to create order letters will have to adapt (this would directly affect us as well) - Creates inconsistency in address handling with patrons and libraries Usually we try to avoid creating a need for changes to be made manually after an update, but I don't think we could avoid that here (reports, notices, CSV profiles for basket exports etc.) Some notes for further testing beyond the test plan: - Export reports on vendor data - CSV basket and basket group exports - PDF basket group printing - Vendors API Found some more occurrences of address3 in the PDF templates: Koha/pdfformat/layout2pages.pm: $text->text($bookseller->address3); Koha/pdfformat/layout2pagesde.pm: $text->text($bookseller->address3); Koha/pdfformat/layout3pagesfr.pm: $text->text($bookseller->address3); ... Failing for the last - but maybe we should discuss this a bit more? I hope, I didn't miss something important. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15297] Preselect earlier date than today for date of birth date pickers when creating a patron account in staff or OPAC
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '20

19 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15297 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Patron registration default |Preselect earlier date than |date |today for date of birth | |date pickers when creating | |a patron account in staff | |or OPAC --- Comment #3 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Both the datepicker for date of birth in staff and OPAC go back a 100 years by default now. Both preselect to today's date. I am not sure if going back 15 years by default would really be helpful with the new longer year select and the option to type the date in directly? It might raise questions instead for being arbitrary. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0