February 2023 - Koha-bugs - lists.koha-community.org

[Bug 32226] New: Capitalization: Edit html content
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32226 Bug ID: 32226 Summary: Capitalization: Edit html content Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org HTML is an abbreviation and should be capitalized: Edit html content koha-tmpl/intranet-tmpl/prog/en/modules/admin/branches.tt:259 -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 32027] New: Terminology: change "librarian interface" to "staff interface" in additional contents tool
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32027 Bug ID: 32027 Summary: Terminology: change "librarian interface" to "staff interface" in additional contents tool 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com According to the terminology list (https://wiki.koha-community.org/wiki/Terminology#S) "staff interface" is the preferred term to designate the staff interface. In a couple of places in the additional contents tool, "librarian interface" is used. 1. Go to Tools > News 2. Click "New entry" --> In the "Display location" drop-down menu, there is "Librarian and OPAC interfaces" and "Librarian interface" as choices 3. Create a news item with the display location set to "Librarian interface" and save --> In the table of all the news, "Librarian interface" is displayed as the location 4. Go to Tools > Pages 5. Click "New entry" --> In the "Display location" drop-down menu, there is "Librarian and OPAC interfaces" and "Librarian interface" as choices 6. Create a page with the display location set to "Librarian interface" and save --> In the table of all the pages, "Librarian interface" is displayed as the location --> "Librarian interface" is also displayed in the "Page URL" column -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 31860] New: 952$h - Serial enumeration / chronology: use sentence case for label
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31860 Bug ID: 31860 Summary: 952$h - Serial enumeration / chronology: use sentence case for label Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org The label for Serial enumeration / chronology (952$h) is displayed as "Serial Enumeration / chronology" - note the capital "E". For consistency, this should be displayed in sentence case wherever it is required in the staff interface and OPAC, including: - details view in the staff interface: MARC view, edit items table, add and edit item form - MARC view in the OPAC: holdings table Note: Libraries can update this themselves by updating $952$h for all the frameworks it is used in. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 24121] New: Item types icons not showing in intra search results if item-level_itypes syspref is set to biblio
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24121 Bug ID: 24121 Summary: Item types icons not showing in intra search results if item-level_itypes syspref is set to biblio Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: pjamorim91(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 32907] New: Add a field for personal ID
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32907 Bug ID: 32907 Summary: Add a field for personal ID Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I know storing social security numbers are a big no-no in some countries, but in others it is perfectly fine and legal. At least libraries in Norway and Sweden expect an ILS to store and handle these numbers. They are not considered "top secret", but are used "everywhere" to identify people. In these countries it looks like a strange omission that "personal IDs" are not handled properly by the system, but have to be shoe-horned in as an extended patron attribute. This also makes it harder than necessary to write reports, sync data from external sources etc. I propose that we - add a database column like borrowers.personalid - add a syspref called something like UsePersonalID - set UsePersonalID to false as the default - make all display and handling of personalid dependent on UsePersonalID This way handling personal IDs will be opt-in only, and something that can be a choice for libraries that want/need to use it. Personal IDs could not only be social security numbers either, in an academic library it could be used for e.g. ORCIDs: https://orcid.org/ A further enhancement to this would be to use personalid for logins, as a third alternative to cardnumber and userid. This could also be governed by a syspref. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 32792] new
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

1 0

[Bug 20395] New: Paycollect does not use Price formatter
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20395 Bug ID: 20395 Summary: Paycollect does not use Price formatter Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org paycollect.tt still uses format('%.2f') instead of $Price -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 32899] New: Unused ILL configs in koha-conf.xml should be removed
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '23

08 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32899 Bug ID: 32899 Summary: Unused ILL configs in koha-conf.xml should be removed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com CC: katrin.fischer(a)bsz-bw.de, magnus(a)libriotech.no, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com Depends on: 19822 staff_request_comments and reply_date in koha-conf.xml are only used in _censor method in Koha::Illrequest but this _censor method is not used anywhere else in Koha. Bug 19822 aims to move ILL config from koha-conf.xml into system preferences, but would it make sense to move configs that are not being used anywhere? Some ILL backends may use these, but all that I have checked so far do not. Backends maintained by PTFS-Europe do not use these. Tomas has confirmed the backends he maintains do not use these. Asking others in the community for confirmation and opinion on this. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19822 [Bug 19822] Add system preferences for ILL Module -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 32774] New: Add information about patron type to suggestion management tables
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '23

07 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32774 Bug ID: 32774 Summary: Add information about patron type to suggestion management tables 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some librarians would find it useful if the suggestion management tables on suggestion.tt included some information about the patron type in the Suggested by column. This could help staff make rapid decisions regarding suggestions based on the patron type. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 32903] New: callnumber.pl plugin - leading 0s are not added when using a prefix
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '23

07 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32903 Bug ID: 32903 Summary: callnumber.pl plugin - leading 0s are not added when using a prefix Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The description in the script for the cataloguing/value_builder/callnumber.pl says that if a prefix is used, then leading zeros are added when needed. Example: If this call number exists for an item "PREFIX 0009678570", then adding PREFIX to another item should generate "PREFIX 0009678571". However, it generates it as "PREFIX 9678571". To replicate (using KTD): 1. In a MARC21 instance, add the callnumber.pl plugin to 952$o for the BKS framework. 2. Edit an item for a record and add "PREFIX 0009678570" as the call number and save. 3. Edit another item for another record. 4. For the call number, enter "PREFIX" and then click on the three dots. 5. Note that it generates the call number as "PREFIX 9678571" instead of "PREFIX 0009678571" with the leading 0s. [1] Full description from the script: Is used for callnumber computation. If the user send an empty string, we return a simple incremented callnumber. If a prefix is submited, we look for the highest callnumber with this prefix, and return it incremented. In this case, a callnumber has this form : "PREFIX 0009678570". - PREFIX is an upercase word - a space separator - 10 digits, with leading 0s if needed -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1