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

[Bug 21510] New: Authority search always jumps back to the first search tab no matter what was searched for
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21510 Bug ID: 21510 Summary: Authority search always jumps back to the first search tab no matter what was searched for Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor 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 Go to: - Authorities module - Select not the first tab for searching - Search - Notice with reloading the page, search jumps to the first tab -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 21496] New: install.pl: DBD::mysql::st execute failed: Index column size too large. The maximum column size is 767 bytes. at /usr/share/perl5/DBIx/RunSQL.pm line 273.
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '23

08 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21496 Bug ID: 21496 Summary: install.pl: DBD::mysql::st execute failed: Index column size too large. The maximum column size is 767 bytes. at /usr/share/perl5/DBIx/RunSQL.pm line 273. Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: migraciones(a)grupoisv.com QA Contact: testopia(a)bugs.koha-community.org Hi, I found the next error when I am installing Koha install.pl: DBD::mysql::st execute failed: Index column size too large. The maximum column size is 767 bytes. at /usr/share/perl5/DBIx/RunSQL.pm line 273. The opertive system is Debian 8 Database is 10.0.32-MariaDB-0+deb8u1 Koha version is Koha 18.05 I need help please Thank you -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 21452] New: Items available for hold or loan must have an item type
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '23

07 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21452 Bug ID: 21452 Summary: Items available for hold or loan must have an item type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Because items may be created during cataloging or acquisitions before we know the item type, it's not practical to set a database constraint where items.itype is not NULL. However, if an item without an item type is checked out or a hold is placed on the item, either items.itype or biblioitems.itemtype (if we're using biblio level items) *must* be populated, or we'll trigger an internal server error. We should be checking for this when we set the notforloan status. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 21445] New: Report - having two date ranges in query creates a formatting issue when running report
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '23

07 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21445 Bug ID: 21445 Summary: Report - having two date ranges in query creates a formatting issue when running report 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: tgoatley(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When the report is run like the following query, the second half of the second date range does not display. SELECT borrowers.cardnumber, borrowers.surname, borrowers.firstname, borrowers.dateofbirth, borrowers.dateenrolled FROM borrowers WHERE dateofbirth BETWEEN <<Date of Birth BETWEEN (yyyy-mm-dd)|date>> AND << AND (yyyy-mm-dd)|date>> AND dateenrolled BETWEEN <<Enrollment Date BETWEEN (yyyy-mm-dd)|date>> AND <<and (yyyy-mm-dd)|date>> AND branchcode=<<Branch|branches>> ORDER BY borrowers.surname ASC Reformatting the query as follows all dates ranges display correctly. SELECT borrowers.cardnumber, borrowers.surname, borrowers.firstname, borrowers.dateofbirth, borrowers.dateenrolled FROM borrowers WHERE dateofbirth BETWEEN <<Date of Birth BETWEEN (yyyy-mm-dd)|date>> AND << AND (yyyy-mm-dd)|date>> AND dateenrolled BETWEEN <<Enrollment Date BETWEEN (yyyy-mm-dd)|date>> AND <<and (yyyy-mm-dd)|date>> AND branchcode=<<Branch|branches>> ORDER BY borrowers.surname ASC -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 21414] New: view_borrower_infos_from_any_libraries can't be used with IndependentBranches
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '23

07 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21414 Bug ID: 21414 Summary: view_borrower_infos_from_any_libraries can't be used with IndependentBranches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When IndependentBranches is turned on, library filter on 'Patrons' menu page ('cgi-bin/koha/members/members-home.pl') only allows the current user site. In spite of the use of the 'view_borrower_infos_from_any_libraries permission', it's not possible to search for patrons from other libraries, even if we're part of the same group of libraries. We can access patron account using the url. No modifications are allowed whether we set IndependentBranchesPatronModifications to 'yes' or 'no'. See also Bug 12599 - IndependentBranches Holes -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 17868] New: Improve display of authors in cart and list emails
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17868 Bug ID: 17868 Summary: Improve display of authors in cart and list emails Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The cart and list emails display a lot of subfields for the author. Example: Author: Seemann, Christian --Bearb. --adp $a $e $4 It would be nice to not display $4 (relator code) if there is $e (relator term). -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 23134] New: Having an "internal notes" field which would be available throughout the suggestion process
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23134 Bug ID: 23134 Summary: Having an "internal notes" field which would be available throughout the suggestion process Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.thornton(a)educampus.ie QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When editing a Purchase Suggestion there is no field to allow staff communicate or add internal notes for other staff. Due to the workflow relating to Purchase Suggestions a suggestion is often passed to another member of staff for approval. Having an "internal notes" field which would be available throughout the suggestion process, would help to facilitate this communication. Staff are currently relying on coded text to communicate using the Notes field e.g. "Lot 1.1 1 X NCM-ML; 1 X NCSL-SL". They also set the reason in the drop-down menu. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 22590] New: Allow batch printing of routing lists
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22590 Bug ID: 22590 Summary: Allow batch printing of routing lists 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Target Milestone: --- For libraries dealing with lots of routing lists it would be nice if they could be printed in batch on demand after receiving several issues. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 22362] New: Make item column in cart sortable in OPAC
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22362 Bug ID: 22362 Summary: Make item column in cart sortable in OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- While the items column in the staff client is sortable, the same is not true for the cart view in the OPAC. I know that the most we could do is sort on the first callnumber available in the list, but I think this would still be helpful in some setups. For example for libraries with only one branch it would be really helpful if the column was sortable as it would help to generate a list that can be used at the library to efficiently get the books from the shelves. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 23235] New: Rename Koha::Biblio->metadata with ->marc_xml to avoid ambiguity
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '23

05 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23235 Bug ID: 23235 Summary: Rename Koha::Biblio->metadata with ->marc_xml to avoid ambiguity 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 22700 What about renaming the method in Koha::S::R::Biblio to ->marc_xml_metadata (adding the conditions in it) and Koha::Biblio->metadata to ->marc_xml (make it returns the MARX XML directly)? See bug 22700 for the discussion. However it will break (again) the reports people already have. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22700 [Bug 22700] Make biblio_metadata prefetchable from Koha::Biblio -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3