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

[Bug 26117] New: itemlost_on value should be updated when item changes from one lost value to another
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26117 Bug ID: 26117 Summary: itemlost_on value should be updated when item changes from one lost value to another 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: - set an item to lost=1 - get the itemlost_on value for your item from the database - change the item to lost=2 - get the itemlost_on value again, confirm that the time hasn't changed I'm sort of torn on this. Just now, we ran into an issue where it we needed to know when a lost value was changed. But I can also imagine a situation where one would want to know when an item became lost originally. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 26112] New: Errors in marc21_authorities files for uk-UA
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26112 Bug ID: 26112 Summary: Errors in marc21_authorities files for uk-UA Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: b.pastern4k(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 107630 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=107630&action=e… uk-UA fixed queries for default authority Upon fresh install when I choose to add authorities, the following error shows near every authorities file install.pl: DBD::mysql::st execute failed: Incorrect integer value: '' for column `koha_sql`.`auth_tag_structure`.`repeatable` at row 1 After completing install, I tried executing those SQL commands in phpmyadmin and it seems that in mandatory and repeatable columns have values '' or 1. I tried replacing those empty strings with zero and it worked. Seems like each SQL query in those files should be checked and columns mandatory, repeatable should only have values 0 or 1 as it is type tinyint(4). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 17350] New: Add option to delete data stored in saved_reports
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17350 Bug ID: 17350 Summary: Add option to delete data stored in saved_reports Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org This is a follow-up bug to bug 14435 which reactivates an old feature that allows you to store the results of a run report in saved_reports. Now that this will work again, there should also be an option to clean up the data stored - either from the script, the GUI or ideally from both. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 26107] New: Add ability to delete saved SQL report results
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26107 Bug ID: 26107 Summary: Add ability to delete saved SQL report results Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Currently we can generate report output to be presented in the Koha interface in a scheduled fashion, but we cannot delete any of the previous runs, either automatically via a scheduler or on the fly from the interface. I propose we add two functions: 1. the ability to delete individual saved report results from the Koha interface (a link or a button near the run a user might like to delete) 2. the ability to have a flag for cleanup_database to remove saved report results older than a syspref'd number of days. Please, don't make it a number on the cron definition - we want libraries to be able to control it themselves from the interface. This can potentially reduce the reliance on e-mail as a delivery mechanism for saved reports, which in certain circumstances can be less reliable than we'd hope. Liz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 32311] New: Add option to delete saved reports results from staff interface
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32311 Bug ID: 32311 Summary: Add option to delete saved reports results from staff interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org Once a set of report results has been saved, there's no way to delete those saved values. Bug 17350 adds a way to delete them via cleanup_database, but it would also be good to have a way to delete them from the staff interface. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 26028] New: Allow HoldsToPullStartDate to be blank
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26028 Bug ID: 26028 Summary: Allow HoldsToPullStartDate to be blank Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When a patron places a hold, then suspends it, and later unsuspends it, the hold will not show on the Holds to Pull list unless the date is set to include the original hold date. This date range is controlled by the system preference HoldsToPullStartDate. When you leave that system preference blank, the system still defaults to 2 days. Libraries should have the option of leaving the system preference blank to show ALL holds that need to be pulled regardless of the original hold date. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 26025] New: Data loss issue during Schema database upgrade from 16.11 to 20.05
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26025 Bug ID: 26025 Summary: Data loss issue during Schema database upgrade from 16.11 to 20.05 Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mishravk79(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi While trying to run database upgrade command from Koha 16.11 to 20.05 it gives following error: Upgrade to 16.12.00.003 done (Bug 17486 - Remove 'Mozilla Persona' as an authentication method) DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha_library`.`deletedbiblio_metadata`, CONSTRAINT `deletedbiblio_metadata_fk_1` FOREIGN KEY (`biblionumber`) REFERENCES `deletedbiblio` (`biblionumber`) ON DELETE CASCADE ON UPDATE CASCADE) [for Statement " INSERT INTO deletedbiblio_metadata ( biblionumber, format, marcflavour, metadata ) SELECT biblionumber, 'marcxml', 'CHANGEME', marcxml FROM deletedbiblioitems; "] at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 13816. Above seems to be data loss under deletedbiblioitem etc. as per discussion over Koha mailing list? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 20636] New: Add unit tests to verify borrowernumber columns are mapped for patron merging
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20636 Bug ID: 20636 Summary: Add unit tests to verify borrowernumber columns are mapped for patron merging 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 9302 We should add unit tests to check that: A) Automate checking that all borrowernumber fields that are foreign keys to borrowers.borrowernumber are in our mapping B) Automate testing all non-fk fields that are *named* borrowernumber are in our mapping. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9302 [Bug 9302] Add ability to merge patron records -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 20677] New: strict.t and valid-templates.t fail with Devel::Cover is used
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20677 Bug ID: 20677 Summary: strict.t and valid-templates.t fail with Devel::Cover is used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org koha_1 | t/db_dependent/00-strict.t (Wstat: 65280 Tests: 683 Failed: 0) koha_1 | Non-zero exit status: 255 koha_1 | Parse errors: Tests out of sequence. Found (1) but expected (2) koha_1 | Tests out of sequence. Found (2) but expected (3) koha_1 | Tests out of sequence. Found (3) but expected (4) koha_1 | Tests out of sequence. Found (2) but expected (5) koha_1 | Tests out of sequence. Found (4) but expected (6) koha_1 | Displayed the first 5 of 683 TAP syntax errors. koha_1 | Re-run prove with the -p option to see them all. koha_1 | xt/author/valid-templates.t (Wstat: 65280 Tests: 853 Failed: 0) koha_1 | Non-zero exit status: 255 koha_1 | Parse errors: Tests out of sequence. Found (1) but expected (3) koha_1 | Tests out of sequence. Found (3) but expected (4) koha_1 | Tests out of sequence. Found (4) but expected (5) koha_1 | Tests out of sequence. Found (5) but expected (6) koha_1 | Tests out of sequence. Found (2) but expected (7) -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 20713] New: Add Russian UNIMARC authority structures
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20713 Bug ID: 20713 Summary: Add Russian UNIMARC authority structures Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: synapse.ova(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Right now there is no russian UNIMARC authority structures. There is russian folder, but the structure is in ukrainian (partly in french). Steps to Reproduce: 1. Install ru-RU language 2. Run installer using ru-RU / Russian language 3. Select UNIMARC MARC flavour 4. Verify mandatory files are loaded without problems 5. Check adding of some authority type (for example, Name Personal — Имя лица) Actual Results: Installed structures in ukrainian language. Only default structure is mandatory. Expected Results: Installed russian structures without problems. All structures used in code are installed as mandatory Additional Information: C4\AuthoritiesMarc.pm (lines 396-409) checks for some specific authority types. These should be considered as mandatory for UNIMARC installations. Structures SAUT, SCO and STU have the same auth_tag_to_report as other structures and are not present in latest french structure → so could be safely removed All these structures (unlike french) have visible fields from unimarc 5th block (related access point). Because we can relate current record with any other authority type (for example Name Personal with Geographical Name). These authority structures can be added to almost any Koha version -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8