May 2022 - Koha-bugs - lists.koha-community.org

[Bug 30789] New: Improve performance of AddBiblio
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '22

12 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30789 Bug ID: 30789 Summary: Improve performance of AddBiblio Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 30850] New: Add default mapping for biblio.author to 110$a (MARC21)
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '22

12 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30850 Bug ID: 30850 Summary: Add default mapping for biblio.author to 110$a (MARC21) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 Currently, biblio.author is only linked to 100$a, which is fine in most cases. But some records have a corporate author (110$a) and those authors don't appear anywhere where the author usually appears (checkout table, letters, labels, etc.) I propose we add a default mapping from 110$a to biblio.author. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 30539] New: Koha upgrade error "Column 'claimed_on' cannot be null"
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '22

12 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30539 Bug ID: 30539 Summary: Koha upgrade error "Column 'claimed_on' cannot be null" Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: saiful(a)semanticconsulting.com QA Contact: testopia(a)bugs.koha-community.org Running koha-upgrade-schema for migration (from 17.x to 21.x) encountered this error which breaks the upgrade during '19.12.00.085': {UNKNOWN}: DBI Exception: DBD::mysql::st execute failed: Column 'claimed_on' cannot be null at /usr/share/perl5/DBIx/C8. ...[snip]... DBIx::Class::Storage::DBI::__ANON__("DBD::mysql::st execute failed: Column 'claimed_on' cannot be "..., DBI::stundef) called at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 22065 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 30057] New: Move Virtualshwlves exceptions to their own file
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '22

12 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30057 Bug ID: 30057 Summary: Move Virtualshwlves exceptions to their own file 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org They are wrongly placed right now. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 29871] New: Remove marcflavour param in Koha::Biblio->get_marc_*
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '22

12 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29871 Bug ID: 29871 Summary: Remove marcflavour param in Koha::Biblio->get_marc_* Change sponsored?: --- Product: Koha Version: master 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: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Remove marcflavour param in Koha::Biblio->get_marc_* We use system preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 30713] New: Patron entry should limit date of birth selection to dates in the past
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '22

12 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30713 Bug ID: 30713 Summary: Patron entry should limit date of birth selection to dates in the past Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com In the patron entry form, the calendar widget lets the user pick dates in the future. It should require dates in the past. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 30864] New: Patron category form - no validation for password expiration field
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '22

12 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30864 Bug ID: 30864 Summary: Patron category form - no validation for password expiration field 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: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When creating a patron category or editing an existing one, there is no validation for the "Password expiration" field. If letters or other characters are entered, there is no error message and if not a number whatever is entered is not saved. To replicate: 1. Go to Administration > Patrons and circulation > Patron categories. 2. Add a new patron category (or edit an existing category). 3. For the "Password expiration" field, enter letters or characters such as L$%. 4. For the "Age required" field, enter letters or characters. 5. Note that for the "Age required" field you are prompted to "Please enter only digits", but for "Password expiration" there is no validation error message. 6. If you save with letters or other characters in the "Password expiration" field, it is shown as a "-" on the patron categories list and is blank when you edit the category. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 29260] New: UNIMARC 210a is reported to Autor (meeting/conference) when upgrading an authority through Z3950
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '22

12 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29260 Bug ID: 29260 Summary: UNIMARC 210a is reported to Autor (meeting/conference) when upgrading an authority through Z3950 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When upgrading an authority with Z39.50, the field 2XX is sent into the research grid. The field 210a is sent into the search field "Author (meeting/conference)". Or a collective authority is more often a corporation than and meeting so librarian has to copy and paste this data to the field "Author (corporation)". (In unimarc field 210a is used both for corporation and meeting.) 1- Find an authority with collectivity type (with a field 210a). 2- Click on "Edit" then on "Edit record" 3- Click on "Replace record via Z39.50/SRU search" 4- See that the field 210 is reported in the search grid in "Author (meeting/conference)" field instead of "Author (corporation) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 30778] New: ModBiblioInBatch is not used and can be removed
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '22

12 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30778 Bug ID: 30778 Summary: ModBiblioInBatch is not used and can be removed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.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 13

[Bug 27868] New: Adding the Expiration Date to the Holds Awaiting Pickup report
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '22

12 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27868 Bug ID: 27868 Summary: Adding the Expiration Date to the Holds Awaiting Pickup report Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: andrew(a)bywatersolutions.com, bwsdonna(a)gmail.com, gmcharlt(a)gmail.com Looking ahead to the passing of bug 8367, it would be nice to have the Hold's expiration date be visible on the Holds Awaiting Pickup Report. When different item types will have the potential to have different expiration dates, it would be a nice column to have in this report to easily see what has expired and what is about to expire. But overall, I do think that a Date Expiration column would greatly help libraries with this current report, Holds Awaiting Pickup. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16