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

[Bug 21255] New: memberetnry.pl is missing categories in the Category pull-down list
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '23

08 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21255 Bug ID: 21255 Summary: memberetnry.pl is missing categories in the Category pull-down list Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cnighswonger(a)foundations.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In some instances, when editing a patron, the Category pulldown under the "Library management" section is missing categories. I'm at a loss as to how to accurately describe the problem, but here goes: 1. The given patron's category shows up correctly on every other screen. 2. Navigating to the Patron Detail screen and selecting the edit option for Library use section results in the Modify Patron screen. 3. The heading on the Modify Patron screen displays the correct category. 4. However, the Category pulldown does not. 5. Furthermore, the pulldown does not even contain the correct category for the given patron. Doing a bit of looking around turned up a few things which may or may not be related. For the given patron: 1. The problem seems to be with the child category. 2. The Koha::Patron::Categories object may contain missing or incorrect category information. Here is a snip of the object returned for the 'C' category type by this line http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=members/memberent… 'attrs' => { 'bind' => [], 'join' => 'categories_branches', 'order_by' => [ 'categorycode' ], 'where' => { 'category_type' => 'C', 'categories_branches.branchcode' => [ 'JL', undef ] }, 'alias' => 'me' }, 3. The underlying data appears to be sound. 4. This was not a problem prior to upgrading a month ago. Unfortunately, I'm not sure what version this system was at prior to the upgrade. Maybe this will get the discussion started and someone with more knowledge of this area of the code can give some direction to it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 23580] New: Add C4::Context->yaml_preference
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '23

06 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23580 Bug ID: 23580 Summary: Add C4::Context->yaml_preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I propose to add a way to retrieve the decoded YAML from (YAML) system preferences. This way we don't need to write code in vain for decoding them in-place. Also, I propose we move pipe-separated sysprefs into YAML lists. This raised on reviewing 22996. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 19436] New: Add SRU support for authorities
by bugzilla-daemon＠bugs.koha-community.org 04 Apr '23

04 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19436 Bug ID: 19436 Summary: Add SRU support for authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be great if Koha also supported SRU for authorities, as libraries like the National Library of Germany only support SRU and no longer offer Z39.50 access. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 57

[Bug 23616] New: Private repeatable note field needed in Serials Subscription Record
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '23

01 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23616 Bug ID: 23616 Summary: Private repeatable note field needed in Serials Subscription Record Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: niamh.walker-headon(a)it-tallaght.ie QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com It is useful to have a record of emails and dates of correspondence in the note field of a journal record in KOHA serials subscriptions. We want to keep this type of note for staff view only while still having the option of a public note also. Staff need to see at a glance what and when action is taken when a claim is escalated. When a missing journal eventually arrives and is marked arrived?, Currently, the notes in the note field must be deleted, as they will show on the OPAC. So the record of what happened is lost in KOHA serials. It would be useful to have a repeatable private note field as well as the public one. See: Electrical Times: https://librarysearch.it-tallaght.ie//cgi-bin/koha/opac-detail.pl?biblionum… ? On this record, See the note for July 2018. It is far easier to see what is happening when the notes are in KOHA serials than stored elsewhere. Serials - Record: Serials administrators need a repeatable private note field, for administration of the subscription and claiming processes. This field would be attached to the subscription field and would not display on the opac. Serials therefore needs two note fields in subscriptions. One for public display and a separate repeatable one for non-public display only. This change would also mean that we can change the status of an issue to “missing (not received)” and be able to explain this status further, such as “not published” or “combined with December issue” in the public note, while still being able to use the non public note for recording details in relation to correspondence and actions relating to claiming the missing issue. These notes are kept to observe patterns in failure to supply, issues with delivery, non-publication etc., so that staff know who was contacted when regarding issues about issues. Processing of serials claims would be more accurate and efficient. This simple change would allow the serials workflow to stay within the serials module making it more streamlined and efficient.Staff feel that this data does not belong on the marc record. Loss of information re business relationship and contractual efficiency with supplier. We currently use this note field to record any problems/correspondence in relation to subscriptions. It enables us to spot patterns in non-supply. On arrival of an issue we must then delete the notes from this field or they will show to the public. The history of correspondence/problems will now be lost. These notes can be useful for tracking ongoing/previous problems. Having to ensure that notes are deleted before displaying publicly allows for possible human error. As far as I can see, this is not the same issue as bues 11492 and 23416, but related -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 23567] New: Printable QR links
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '23

01 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23567 Bug ID: 23567 Summary: Printable QR links Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Suppose there were a tool that would allow you to process items, much like you would for spine labels, but instead printed custom messages along with a QR code to useful things. For example, you might select a "Comment QR label". You would enter a generic message like "Tell us what you thought of this book." Labels would print for each item with this message, and the QR code beneath, and you would affix this label inside the back of the book. When the patron is done reading the book, they scan the code, and it takes them straight to the comment form in the OPAC (after signing in, if required) for that book, and they can fill out a comment right on their device. Other options, instead of comments, might include rating, tagging, or bragging about the book in a specific social media. For example, they scan the QR code and it would go to Facebook and start a post with a link to the book in the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 17515] New: Advanced Editor - Rancor - Z39 sources not sorted properly
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '23

31 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17515 Bug ID: 17515 Summary: Advanced Editor - Rancor - Z39 sources not sorted properly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This appears to be a bug, the list of servers is retrieved from the database in order, however, it is stored in an unordered object, so the lists are posted to the page in a random order. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 23997] New: sample_z3950_servers.sql is failing on MySQL 8
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '23

31 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23997 Bug ID: 23997 Summary: sample_z3950_servers.sql is failing on MySQL 8 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Blocks: 23996 koha_1 | DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'rank, syntax, encoding,recordtype) VALUES koha_1 | ('lx2.loc.gov',210,'LCDB','','','LIBRA' at line 2 at /usr/share/perl5/DBIx/RunSQL.pm line 273. https://dev.mysql.com/doc/refman/8.0/en/keywords.html => RANK (R); added in 8.0.2 (reserved) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23996 [Bug 23996] MySQL 8 support -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 17649] New: Create only one message per borrower and overdue level
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '23

30 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17649 Bug ID: 17649 Summary: Create only one message per borrower and overdue level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Following a discussion on french list koha-infos, it appears that, among other ones, 2 things are expected from the overdue_notices.pl script (but not currently achieved) : 1) It should be possible to send only one message grouping all branches overdue items with same delay level => by now there are as much messages sent as overdue items branches with same level ( a patron that have overdue with same level in library A and B will received 2 messages claiming the same items.) This patch try to solve this problem ( provided to use only a default notice model in Notices and Slips). It introduces a new option (a|all_in_one) that has to be followed by a branchcode from which will be set the sender address of the message. 2) each branch should be able to send claims including only its very overdue items => by now messages also include, if they exist, all overdues with same delay level from other branches, even if library option is used. Patch from bug 17470 aims to solve this problem. Test plan (almost entirely and shamefully copied from bug 17470 !) 0/ Have (or create) at least two branches B1 and B2. Have (or create) a default notice for all branches in Notices and Slips Module 1/ Make sure you're logged in with an account belonging to B1, or switch to branch B1 2/ checkout item I1 (belonging to B1) to patron P (preferably while specifying a due date < today) 3/ switch to branch B2 4/ checkout item I2 (belonging to B2) to patron P (preferably while specifying a due date < today) 5/ make sure you have defined "Overdue notice/status triggers" for that patron category, ie with Delay=1 so that "Overdue Notice" is selected and "Email" is checked. 6/ from cli run 'perl ./misc/cronjobs/overdue_notices.pl' (optionally specifying also '-library B1 -library B2') example (say that B2CODE is the branchcode of B2 branch ): ./overdue_notices.pl -t -a B2CODE 7/ Two new entries will be generated in message_queue DB table, coming from different branches that have the SAME list of overdue items 8/ either see the 'content' field in these entries, or run 'perl ./cronjobs/process_message_queue.pl' to receive the actual emails (provided the email is properly setup). Apply patch redo step 6/ You will see that only one message had been created. Its content shows both B1 and B2 overdue items and the sender address matches B2 address as well. Olivier Crouzet -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 17754] New: MARCXML encoding problems
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '23

29 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17754 Bug ID: 17754 Summary: MARCXML encoding problems 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 Uploading authorities in MARCXML in 16.11 and master kills Umlauts while they work ok in the same file in mrc format. I have not checked biblios yet. Upload mrc: Universität Berlin (Freie Universität) Upload xml: Universitt̃ Berlin (Freie Universitt̃) -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 21135] New: Upon log in, user is redirected to account page instead of the page where they logged in from
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '23

28 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21135 Bug ID: 21135 Summary: Upon log in, user is redirected to account page instead of the page where they logged in from 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When a user clicks on a link "log in to ..." they are redirected to their account page instead of staying on the page they were on to do whatever they needed to log in to do. To reproduce : 1- In Administration > System preferences, enable TagsEnabled 2- Make sure TagsInputOnDetail is set to Allow 3- Go to OPAC, and do a search 4- Click on title to go to the details page 5- Click on the "Log in to add tags" link 6- Enter your login credentials in the popup window Result : user is redirected to "My account" Desired result : user is now logged in but stays on the record detail page Second case : 1- In OPAC, click on Lists > View All 2- Click on "Log in to create new lists" 3- Enter your login credentials Result : user is redirected to "My account" Desired result : user is now logged in but stays on the lists page -- You are receiving this mail because: You are watching all bug changes.

1 9