September 2017 - Koha-bugs - lists.koha-community.org

[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 17480] New: UpdateNotForLoanStatusOnCheckin preference requires space after colon
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '23

22 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17480 Bug ID: 17480 Summary: UpdateNotForLoanStatusOnCheckin preference requires space after colon Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 11629 YAML requires that there be a space after a colon, so the UpdateNotForLoanStatusOnCheckin preference does too: -1:0 will not work -1:<space>0 will work We should either handle this gracefully for the user (preferable, since this preference will only use numeric values), or update the preference's description to highlight the requirement. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11629 [Bug 11629] Add ability to update not for loan status on checkin -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 19188] New: Self checkout: missing space if fine amount is blocking renewal
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '23

14 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19188 Bug ID: 19188 Summary: Self checkout: missing space if fine amount is blocking renewal Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When a fine amount is blocking the renewal in the web based self checkout, the message reads like: ... EUR15.00 ... EUR is the active currency in my system, so display might vary a bit. We should add a space there and it might be nice to use the Price TT plugin for formatting the fine nicely. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 18247] New: Remove SQL queries from branch_transfer_limit.pl administrative script
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '23

14 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18247 Bug ID: 18247 Summary: Remove SQL queries from branch_transfer_limit.pl administrative script Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org This bug report requires all three SQL queries to be removed from branch_transfer_limit.pl administrative script and placed into suitable perl modules in the Koha or C4 directory. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 18556] New: Message "Patron's address in doubt" is confusing
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '23

14 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18556 Bug ID: 18556 Summary: Message "Patron's address in doubt" is confusing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If a borrower has the patron account flag "Gone no address" set, the message "Patron's address in doubt" appears on the circulation check-out screen. This is confusing -- the borrowers table has the following fields that could be interpreted as an 'address' field: streetnumber streettype address address2 city state zipcode country B_streetnumber B_streettype B_address B_address2 B_city B_state B_zipcode B_country altcontactaddress1 altcontactaddress2 altcontactaddress3 altcontactstate altcontactzipcode altcontactcountry ... and it turns out that the message has *nothing* to do with any of these. I think that the message should read "Patron account flag 'Gone No Address' is set." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 16488] New: UNIMARC to MARC21 xslt to be used in z39.50 import sources
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '23

04 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16488 Bug ID: 16488 Summary: UNIMARC to MARC21 xslt to be used in z39.50 import sources Change sponsored?: --- Product: Koha Version: 3.20 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: gmcharlt(a)gmail.com Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be very helpful to have at least a 'basic' xsl template to be able to convert UNIMARC data to USMARC when trying to search and import data from UNIMARC z39.50 sources. It seems that there is a generic xslt available for UNIMARC to MARC conversion (https://github.com/edsd/biblio-metadata/blob/master/UNIMARC2MARC21.xsl) but it obviously needs a few changes to work with Koha. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 17699] New: DateTime durations are not correctly subtracted
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '23

01 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17699 Bug ID: 17699 Summary: DateTime durations are not correctly subtracted Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal 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: 16911 >From DateTime::Duration pod: """ For positive durations, the "end_of_month" parameter defaults to wrap. For negative durations, the default is "limit". This should match how most people "intuitively" expect datetime math to work. """ Today we are Nov 30, that means $today->subtract( months => 1 ) will return Oct 31, when we usually expect Oct 30 in tests Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16911 [Bug 16911] Koha::Patrons - Move ExtendMemberSubscriptionTo to ->renew_account -- You are receiving this mail because: You are watching all bug changes.

1 48

[Bug 17550] New: Display additional patron data in patron suggestion form
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '23

26 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17550 Bug ID: 17550 Summary: Display additional patron data in patron suggestion form Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When in Home › Circulation › Checkouts and the librarian wants to select a patron to perform a checkout upon, the suggestions currently display only the following patron data: Surname, Firstname (CardNumber) Address City Zipcode Country It would be nice if patron INITIALS were also displayed, like this: Surname, Firstname INITIALS (CardNumber) Address City Zipcode Country The reason is that multiple patrons may have the same Surname and Firstname and in order to distinguish them the librarians feel better to ask the patron for their initials rather than asking for the address (btw in our installation we use Father's name in place of initials, but this doesn't alter the use case) Further more, to better distinguish the various names and to make the Surname and Firstname 'stand out', I suggest converting them to bold, while making the initials italic. For all these changes the patch (in matter of code lines) is trivial: a few lines in two files. You may also find two screenshots of the current and the proposed functionality (the screenshots were taken from a Koha 3.20.x server but the change is applicable to recent versions also and the patch is created using the current master) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 18495] New: Creating a subgroup within report doesn' t add report to that group
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '23

24 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18495 Bug ID: 18495 Summary: Creating a subgroup within report doesn't add report to that group Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org You can create a subgroup while editing/creating a report, but it doesn't add the report to that group. I didn't test if this is the case with the report group. -- You are receiving this mail because: You are watching all bug changes.

1 2