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

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

15 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 15 Mar '23

15 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 19693] New: authtypefrom incorrectly set when updating auth recs from file
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '23

15 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19693 Bug ID: 19693 Summary: authtypefrom incorrectly set when updating auth recs from file Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In those cases when authorities are updated by an external agency (or even internally, by reviewing and correcting an exported authority file) when the heading tag will be changed (seems odd but happens: 111 Congress ==> 110 Corporate body.Congress ; 100 Person ==> 110 Corporate body (a company named with person's name ; 151 City--object ==> 150 Object (city) etc.) and then the authority record in Koha database will be updated with bulkmarcimport or by calling directly ModAuthority from a custom script, the merge function "doesn't know" that the change to the authority type has been made and, consequently, doesn't adequately change the tag in related fields in biblio records (as it would if two different records with different authtypecode were merged with Koha interface). This is because at the moment when merge function is being called by ModAuthority Koha::Authority::Types->find($autfrom->authtypecode) Koha::Authority::Types->find($authto->authtypecode) both have the same value (because $autfrom == $autfrom). Therefore the authtype guessed from the old version of the record should be considered. To test: 1) have an authority record used in biblio; export it to file; change 1XX heading tag to different (but reasonable) value and possibly change also the content of the heading (one can delete also 942 but it doesn't matter); make bulkmarcimport.pl -a -update -file <modified_auth_file> and see that the tag in biblio record has not been changed (whereas the type of authority record did change); 2) make orders in database (so that the authority type and the tag of the field in biblio record correspond); apply the patch; 3) repeat the test from 1). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

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

15 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 19454] New: working title
by bugzilla-daemon＠bugs.koha-community.org 11 Mar '23

11 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19454 Bug ID: 19454 Summary: working title Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[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 18002] New: Add functionality to create a vendor and budget in the onboarding tool
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '23

28 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18002 Bug ID: 18002 Summary: Add functionality to create a vendor and budget in the onboarding tool Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 17855 Add two additional interfaces to the onboarding tool to allow the user to create a vendor and budget before logging into Koha for the first time, thereby allowing users to get acquisition requirements set up. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17855 [Bug 17855] Updated Koha web installer and new onboarding tool feature to guide users through setting up Koha -- You are receiving this mail because: You are watching all bug changes.

1 96

[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