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

[Bug 14233] Add logging support to notices and slips management
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '20

30 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14233 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=26207 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14233] Add logging support to notices and slips management
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '20

30 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14233 --- Comment #1 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- This would also be a great use case for the compare prefs patch that Owen has worked on: Bug 26207 - Compare values of system preference log entries -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14233] Add logging support to notices and slips management
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '20

30 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14233 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=25776 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14233] Add logging support to notices and slips management
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '20

30 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14233 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Add logging support to |Add logging support to |notices' management |notices and slips | |management -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 5561] Help on summary field in authority type editor
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '20

30 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5561 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alex.arnaud(a)biblibre.com, | |julian.maurice(a)biblibre.com --- Comment #6 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Can some of our UNIMARC devs help out here? I am looking for verification of comment#1 and an example that we could put in the manual. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 14941] Subfield defaults: Add information about substitutable values
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '20

30 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14941 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=24134 --- Comment #6 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Submitted a merge request to the manual: https://gitlab.com/koha-community/koha-manual/-/merge_requests/388 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 24134] New: improve 008 framework flexibility (autogenerate date)
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '20

30 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24134 Bug ID: 24134 Summary: improve 008 framework flexibility (autogenerate date) Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: philip.bertling(a)rbg.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When creating a framework for a form type other than book, it does not seem possible to autogenerate the date correctly. The 00-05 ‘date entered on file’ in the 008 field, can almost be auto-filled by using the code <<YYYY>><<MM>><<DD>>. However it doesn’t quite work because the 008 field expects a 6 digit date [YYMMDD] – this code inserts an 8 digit date [YYYYMMDD]. e.g. <<YY>><<MM>><<DD>> b at |||p |||||00| eng d = entered on the date <<29>><<11>><<25>> This creates the following data in a record: <<YY>>1125 b at |||p |||||00| eng d Is it possible to make this date code work to insert a date comprising 6 digits? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 14941] Subfield defaults: Add information about substitutable values
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '20

30 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14941 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|chris(a)bigballofwax.co.nz |katrin.fischer(a)bsz-bw.de -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 21504] New: enumchron shows as 0 in pdf
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '20

30 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21504 Bug ID: 21504 Summary: enumchron shows as 0 in pdf Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 80141 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=80141&action=ed… bibrecord for testing enumchron issue When printing a spine label with itemcallnumber and enumchron, the pdf shows the one or two digit enumchron value as 0, but the CSV and XML formats show the correct enumchron value. Have replicated in 18.05. Changing item type, bib record, enumchron value, etc all result in same scenario. To replicate, create a template and layout: Template: US inches Page height 11 Page width 8.5 Label width 1.625 Label height 1 Top page margin .5 Left page margin .25 Top text margin .3 Left text margin 1.25 Number of columns 5 Number of rows 10 Gap col 0 Gap row 0 No profile Layout: Biblio 1 itemcallnumber 2 enumchron Split call numbers Text: center Font: Times-Bold Font size 12 Create a label batch with an enumchron, marc file for the record I was using is attached. View the pdf and see the enumchron shows 0. View the CSV and XML and see the correct enumchron shows. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 25878] New: Schema incorrectly describes course_items fields
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '20

30 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25878 Bug ID: 25878 Summary: Schema incorrectly describes course_items fields 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On the schema page for the course_items table we include this comment on course_items.itype: "new itemtype for the item to have while on reserve (optional)" We have comparable notes for ccode, holdingbranch, and location. That comment is not strictly correct. While a course is active, these fields in course_items will hold the items original values. If the course is marked inactive and the item's original values are returned to the items table, then the fields in course_items will hold the values that this item had while on reserve. At this time I do not have alternate wording that explains this succinctly enough to put into the schema comment. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2