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

[Bug 24531] New: OAI-PMH sets only consider first field with a given tag
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '21

29 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24531 Bug ID: 24531 Summary: OAI-PMH sets only consider first field with a given tag Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no 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 19821] New: Run tests on a separate database
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '21

29 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19821 Bug ID: 19821 Summary: Run tests on a separate database Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Running the tests on the same database as the one used for dev has some drawbacks: - Everybody has different data, so we cannot make any assumptions about data in tests and it can make tests fail for non-obvious reasons. - Tests have to clean up every change to the database using SQL transactions, so we cannot write testable code that use transactions (AFAIK) - Transactions in tests happen to be committed sometimes, resulting in garbage data added to the dev database I'll send a patch that allows to run tests in a separate database in order to address these issues. -- You are receiving this mail because: You are watching all bug changes.

1 106

[Bug 24814] New: HTML forms set a minimal width for dropdown combo with empty set.
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '21

29 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24814 Bug ID: 24814 Summary: HTML forms set a minimal width for dropdown combo with empty set. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, If there's no item, dropdown message "No matches found" is hard to read. Affect: koha-tmpl/intranet-tmpl/prog/en/modules/authorities/authorities.tt koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/addbiblio.tt koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/additem.tt koha-tmpl/intranet-tmpl/prog/en/modules/tools/batchMod-edit.tt To test: - Select a catalogue notice in Koha intranet. - Open add item form. - Choose a dropdown combo with an empty set, 'j - Shelving control number' is a good candidate. - Apply the patch. - Re select the compo in open add item form. It's a bandaid, a proper solution would be to compute container width on actuel message size. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 22466] New: TT methods must not be escaped
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '21

28 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22466 Bug ID: 22466 Summary: TT methods must not be escaped Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Templates 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: 21576 Target Milestone: --- They could (it will not break anything) but it does not make sense. So far the QA script is failing if they are not. For instance: [% my_array.push(a_var) %] Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21576 [Bug 21576] Add a developer script to automatically fix missing filters -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 26493] New: Add missing FK constraints to aqbudgets
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '21

28 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26493 Bug ID: 26493 Summary: Add missing FK constraints to aqbudgets Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 18050 There are several column in aqbudgets that should have FK constraints on them: budget_branchcode => branches.branchcode budget_owner_id => borrowers.borrowernumber sort1_authcat sort2_authcat => authorised_value_categories.category_name Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18050 [Bug 18050] Missing constraint on aqbudgets.budget_period_id in aqbudgets -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 27245] New: bulkmarcimport.pl error 'Already in a transaction'
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '21

26 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27245 Bug ID: 27245 Summary: bulkmarcimport.pl error 'Already in a transaction' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz When using script to import records misc/migration_tools/bulkmarcimport.pl, I get the error : .DBD::mysql::db begin_work failed: Already in a transaction at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1588, <GEN45> line 1. I thinks it is because of transaction in the script : $dbh->{AutoCommit} = 0; And C4::Biblio::AddBiblio launches a transation : $schema->txn_do(sub { Records are imported well but its a scary error :/ -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 24545] New: Replace Franklin Street by gnu.org/licenses in copyright
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '21

26 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24545 Bug ID: 24545 Summary: Replace Franklin Street by gnu.org/licenses in copyright Change sponsored?: --- Product: Koha Version: master 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org No big deal but inconsistent: git grep -l "gnu.org/licenses"| wc -l 1156 git grep -l "Franklin Street"| wc -l 471 It seems easier to me to go to gnu.org than writing to Boston ? Even in newer files sometimes the older copyright is copied. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 47

[Bug 20277] New: Link to host item doesn't work in analytical records if 773$a is present
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '21

26 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20277 Bug ID: 20277 Summary: Link to host item doesn't work in analytical records if 773$a is present Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org A lot of analytical records are made for serials. And for most of them the title is their primary access point. The OPAC and intranet link in the analytical record to the host item works well in these cases. But if you have a 1XX field in your host item, this information goes in your 773$a subfield but the OPAC and intranet link in the analytical record to the host item includes 773$a and 773$t data but searches only in the title index. In this situation you can't retrieve the host item record. Test: - Create an analytical record for a (host)record with a 1XX field. - Use the link in the analytical ("In" note) to retrieve the host record in the intranet client and the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 24698] New: UNIMARC authorities leader plugin
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '21

26 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24698 Bug ID: 24698 Summary: UNIMARC authorities leader plugin Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: vitorfernandes87(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The leader for authority record is different than for bibliographic record. We need a plugin for UNIMARC Authorities leader. Page 27 - https://www.ifla.org/files/assets/uca/unimarc-authorities-format.pdf -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 57

[Bug 27155] New: Biblio and Item hooks should pass a deleted object on record deletion
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '21

26 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27155 Bug ID: 27155 Summary: Biblio and Item hooks should pass a deleted object on record deletion Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org The biblio and item hooks now look up a record which is deleted already. We could pass the deletedbiblio or deleteditem? Especially on item deletion I am interested in receiving the biblionumber. The code for items differs between 19.11 and master. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20