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

[Bug 23352] New: Set serial issue default values when creating a subscription in serials/subscription-add.pl
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '24

27 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23352 Bug ID: 23352 Summary: Set serial issue default values when creating a subscription in serials/subscription-add.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com To speed up the process of receiving serial issues libraries should be able to set default serial issue values for the subscription when they create the subscription. Currently, it is possible for librarians to set default values for 952 MARC fields in the bibliographic frameworks but that would set blanket default values for all subscriptions. As different subscriptions are likely to have different 952 MARC field values it would be useful for libraries to set default values which are only applied to the serial issue items created for a specific subscription. The default values they should be able to set when creating the subscription (in serials/subscription-add.pl) are: * Collection code * Subscription full cost Then when a serial issue is received from the two above values the following 952 subfields will be pre-populated: * 952$8 Collection Code - Pulled in from default set in serials/subscription-add.pl * 952$b Current location - Set to the currently logged in library branch * 952$d Date acquired - This will be pre-populated upon page load rather than when you click on the text input field as is the current behaviour * 952$h Serial Enumeration/ chronology - This will be pre-populated from the subscription numbering pattern * 952$v Cost, replacement price - This will be pre-populated from the calculation of the subscription full cost/number of issues This would only leave the librarian to input 952$p (barcode) and 952$a (permanent location), speeding up the cataloguing process of receiving serials. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 82

[Bug 16654] New: The output from reports/cat_issues_top.pl is not proper CSV
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '24

25 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16654 Bug ID: 16654 Summary: The output from reports/cat_issues_top.pl is not proper CSV Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The output from reports/cat_issues_top.pl is *NOT* csv; it is DSV (delimiter separated values) with the option of using commas as delimiters... and the delimiters aren't properly escaped. To illustrate the point 1/ Check out an item whose title contains a comma. 2/ Go to Home [34m~@� Reports [34m~@� Most-circulated items 3/ Select a date range containing today's date 4/ Select the "To a file" radio button, and use comma (,) as the delimiter. 5/ Click Submit Open the file in the spreadsheet program of your choice. Note that the title containing the comma spans two columns, because it was not properly quoted. If the report is going to use CSV as a file extension, it should be exported using Text::CSV_XS, which properly handles CSV export. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 17216] New: Add a new table to store authorized value categories
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '24

22 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17216 Bug ID: 17216 Summary: Add a new table to store authorized value categories Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement 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 Blocks: 15799 The way we manage authorized values is not consistent: Some are present in the DB, others are not (see bug 15799 comment 4 for more details). Worse, most of the time the FK does not exist (and datatype is not consistent: varchar 32 vs 20, 16,...). To help cleaning up this area, a new table to store authorized value categories would be helpful. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15799 [Bug 15799] Move authorised values related code into Koha::AuthorisedValues - part 2 -- You are receiving this mail because: You are watching all bug changes.

1 148

[Bug 20630] New: An attempt at multitenancy with Mojolicious
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '24

21 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20630 Bug ID: 20630 Summary: An attempt at multitenancy with Mojolicious Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 20582 There seems to be some concerns about the capability for Koha to be multitenant in a persistent environment, in particular with Mojolicious. This bug will try to address those concerns. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20582 [Bug 20582] Turn Koha into a Mojolicious application -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 23540] New: Gender 'N' is not translatable
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '24

18 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23540 Bug ID: 23540 Summary: Gender 'N' is not translatable Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: pasi.kallinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Patrons of type 'I' (institution) automatically get their sex/gender set to 'N' (which is short for "None"), but the 'N' is not translatable and actually shows up in the patron details page. Relevant code in memberentrygen.tt: [% IF ( I ) %]<input type="hidden" name="sex" value="N" />[% END %] The template code for showing the gender text should be unified into single included file, instead of spread over multiple places like: koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember.tt: [% IF ( patron.sex == 'F' ) %]Female[% ELSIF ( patron.sex == 'M' ) %]Male[% ELSE %][% patron.sex | html %][% END %] koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember-brief.tt: [% IF ( patron.sex ) %]<li><span class="label">Gender:</span>[% IF ( patron.sex == 'F' ) %]Female[% ELSIF ( patron.sex == 'M' ) %]Male[% ELSE %][% patron.sex | html %][% END %]</li>[% END %] -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 21314] New: Koha enforces 3 character password length even if RequireStrongPassword is disabled
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '24

18 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21314 Bug ID: 21314 Summary: Koha enforces 3 character password length even if RequireStrongPassword is disabled Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 18298 added the option to enforce password complexity *if* the new system preference RequireStrongPassword is enabled. However, it appears that the code defining the minimum number of characters was not put under control of this preference and thus Koha enforces a minimum password length of 3 even if RequireStrongPassword is disabled. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 20657] New: Globally enable PRE_CHOMP and POST_CHOMP in Template Toolkit configuration
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '24

18 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20657 Bug ID: 20657 Summary: Globally enable PRE_CHOMP and POST_CHOMP in Template Toolkit configuration Change sponsored?: --- Product: Koha Version: unspecified 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org As it currently stands, the HTML output by Template Toolkit includes whitespace anywhere there was a template tag. For example, this is a portion of the generated source of the staff client home page: 1 2 3 4 <!DOCTYPE html> 5  6 7 8 9 10 <html lang="en"> 11 <head> 12 13 <title>Koha staff client</title> Developer tools report: 26.69 KB / 5.83 KB transferred In contrast, this what the same content looks like with PRE_CHOMP and POST_CHOMP enabled: 1 <!DOCTYPE html> 2  3 <html lang="en"><head> 4 <title>Koha staff client</title> Developer tools report: 23.29 KB / 5.65 KB transferred In the samples I looked at this change did not make the HTML source significantly more difficult to read. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 19548] New: Search Result Second page not available
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '24

17 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19548 Bug ID: 19548 Summary: Search Result Second page not available Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: rainer.stowasser(a)zamg.ac.at QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl With the SRU/Z39.50 search using a quotation mark has the interesting effect that the first page of a result is displayed but a second page is not available. Looking at the pl source it seems that quotation marks are used and escaped for the first page but not for a second recall. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 23335] New: "There are no items that can be placed on hold."
by bugzilla-daemon＠bugs.koha-community.org 11 Mar '24

11 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23335 Bug ID: 23335 Summary: "There are no items that can be placed on hold." Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jmmureithi(a)nationalbank.co.ke QA Contact: testopia(a)bugs.koha-community.org Created attachment 91571 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=91571&action=ed… THE MESSAGE APPEARING IN OPAC The clients/users are trying to place hold and the following message is displayed yet there are items: There are no items that can be placed on hold. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 18729] New: Librarian unable to update hold pickup library from patron pages without "modify_holds_priority" permission
by bugzilla-daemon＠bugs.koha-community.org 07 Mar '24

07 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18729 Bug ID: 18729 Summary: Librarian unable to update hold pickup library from patron pages without "modify_holds_priority" permission Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com A librarian can update a hold's pickup library from the record details page, but not from the patron details or checkout pages unless he or she has the "modify_holds_priority". If the librarian does not, an error is displayed instead. This is do to the fact that on those two pages the API is used and it used the PUT for hold to update all hold fields, which requires this permission. Another endpoint for updating only the pickup location should be added that does not require the "modify_holds_priority" permission. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 70