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

[Bug 5103] Dates in MARC details not formatted correctly
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '20

26 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5103 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #99627|0 |1 is obsolete| | --- Comment #3 from David Nind <david(a)davidnind.com> --- Created attachment 99671 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=99671&action=ed… Bug 5103: Format dates in MARC detail using dateformat syspref This patch fixes the formatting of dates on the following pages: - catalogue/MARCdetail.pl (staff) - cataloguing/additem.pl (staff) - opac-MARCdetail.pl (opac) To test: 1) Ensure that the following fields are visible in the opac, intranet and editor. You may need to edit the subfields in your default bibliographic framework 952$d date accessioned 952$q date due/on loan 952$r date last seen 952$s date last borrowed 952$w replacement price date Also ensure you have dateformat system preference set 2) Go to cataloguing/additem.pl for a biblio. Fill in the fields above if required. Save 3) Remain on cataloguing/additem.pl. Notice the items table at the top of the page, the dates are in the generic yyyy-mm-dd format 4) Go to catalogue/MARCdetail.pl for that biblio. Notice dates in wrong format 5) View this biblio in the opac opac-MARCdetail.pl. Scroll to bottom to items table. Notice dates in wrong format. 6) Apply patch, restart memcached and plack and refresh pages 7) Dates should now be formatted according to dateformat preference 8) Confirm that changing the preference changes the format of the dates Sponsored-by: Catalyst IT -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 5103] Dates in MARC details not formatted correctly
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '20

26 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5103 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 24737] New: unreal
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '20

26 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24737 Bug ID: 24737 Summary: unreal Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: pmarceloy(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org not a real bug -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 13775] Set main headings to mandatory in authority frameworks
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '20

26 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13775 Jon Knight <J.P.Knight(a)lboro.ac.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |J.P.Knight(a)lboro.ac.uk --- Comment #16 from Jon Knight <J.P.Knight(a)lboro.ac.uk> --- I've just looked at this to sign it off and applied it on the Bywater Solutions sandbox. The patch applied OK, but when I create a new authority it doesn't seem to enforce the main heading restriction. For example I just created a new Corporate Name authority with no 110 field: Authority #1709 (Corporate Name) This authority is not used in any records. 0 000 - LEADER @ 00188nz a2200097n 4500 001 - CONTROL NUMBER @ 1709 003 - CONTROL NUMBER IDENTIFIER @ OSt 005 - DATE AND TIME OF LATEST TRANSACTION @ 20200226170818.0 008 - FIXED-LENGTH DATA ELEMENTS @ 200226|| aca||aabn | a|a d 040 ## - CATALOGING SOURCE a Original cataloging OSt Same with a new Chronological Term and Personal Name authorities. I've checked that the patch is applied (by trying to apply it again and getting the error that it is already applied) and restarted all the service just in case, but the same behaviour. Is there a configuration option that needs to be set first (which should probably be in the test plan)? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23344] New: Branch Transfer Limits - Warn if sysprefs are not set
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '20

26 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23344 Bug ID: 23344 Summary: Branch Transfer Limits - Warn if sysprefs are not set 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: olli-antti.kivilahti(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The admin-menu branch_transfer_limits.pl is available but doesn't say anything about sysprefs that need setting. Testing and finding out the limits don't work is confusing. It would be more intuitive to just use the feature in the background without having to mess with any extra sysprefs. Or set the aforementioned sysprefs in the branch_transfer_limits.pl -page. This patch adds a simple warning if syspref 'UseBranchTransferLimits' is not activated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 8628] Add digital signs to the OPAC
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '20

26 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8628 --- Comment #88 from Owen Leonard <oleonard(a)myacpl.org> --- I'm getting this error: Template process failed: undef error - DBIC result _type isn't of the _type SavedSql at /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/modules/tools/signs.tt line 419. at /kohadevbox/koha/C4/Templates.pm line 122 Did I miss a step in the setup? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 24729] New: 008 Enhancement
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '20

26 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24729 Bug ID: 24729 Summary: 008 Enhancement 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I've noticed a hole in cataloging that some library might not deal with, and others do, but it is certainly a hole for our libraries. We found that the advanced search subtype limits (Audience, content, format, additional content types), rely on the 008 field. However, our libraries have chosen not to fill those in, and the sources they download these records from have chosen not to fill them in either. I'm wondering if it would be a smart idea, that since these search fields rely on this information, if it is not filled in for a bib record, there should be some sort of warning on the bib record/item records in cataloging, so catalogers are aware that these records are not complete. In fact, any other field that any search limit could rely on could have a similar warning for catalogers. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 9239] Koha should share Evergreen's QueryParser module for parsing queries
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '20

26 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9239 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |24735 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24735 [Bug 24735] Remove QueryParser-related code -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12742] Omnibus: QueryParser
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '20

26 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12742 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |24735 CC| |jonathan.druart(a)bugs.koha-c | |ommunity.org Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #1 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- Code will be removed by bug 24735. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24735 [Bug 24735] Remove QueryParser-related code -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12430] Search truncation disables relevance ranking
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '20

26 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12430 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Search truncation disables |Search truncation disables |relevance ranking when not |relevance ranking |using QueryParser | -- You are receiving this mail because: You are watching all bug changes.

1 0