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

[Bug 7468] Add label to batch by barcode range
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '20

16 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7468 --- Comment #36 from Maryse Simard <maryse.simard(a)inlibro.com> --- Created attachment 97458 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=97458&action=ed… Bug 7468: (follow-up) Make sure only integers are accepted as from/to values -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7468] Add label to batch by barcode range
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '20

16 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7468 --- Comment #35 from Maryse Simard <maryse.simard(a)inlibro.com> --- Created attachment 97457 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=97457&action=ed… Bug 7468: Showing the error message according to the community interface patterns, fixing a javascript condition TEST PLAN++ 1) Apply all the patches 2) Connect to the intranet with an account with permissions to visit the "Tools" page 3) Go to /cgi-bin/koha/labels/label-home.pl . Either by entering the URL directly . OR, from the front page, by clicking "Tools", followed by the hyperlink "Label creator" under the "Catalog" section 4) Under the "+ New" button, a new option should be available: "Barcode range" 5) Fill the "From:" and the "To:" fields of the "Print barcode range" form . Keeping both fields at "0" should trigger a warning beside the first field: "*Cannot be smaller than 1" . If the value "From:" is greater the "To:" value, a warning should appear beside the second field: "*Cannot be smaller than the starting value" . Make sure the form doesn't let you enter non-numerical values . For a casual test, use "From: 1000" and "To: 1100" 6) After pressing the "Print Range" button, choose a template, a layout, and a starting position . The "DEFAULT TEMPLATE 01" has a page height of 5pt and a page width of 0pt, don't use it . All the default layouts should look alike, since we're only printing a barcode over a number, and not bibliographic information . Using a layout not defined as 'Barcode' will show a warning message 7) Clicking the "Export" button should lead to a second dialog window with a "Download as PDF" hyperlink. Clicking the link should prop up a download dialog box 8) Save the PDF locally, or simply open it, and make sure the options you used were taken into account -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7468] Add label to batch by barcode range
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '20

16 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7468 --- Comment #34 from Maryse Simard <maryse.simard(a)inlibro.com> --- Created attachment 97456 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=97456&action=ed… Bug 7468: Add warning when range has non-existent barcodes + Added a warning when the user selects a range with some non-existent barcodes, and a layout without barcodes. This allows the user to print barcodes of items not in the database if he so desires, but will warn him if he tries to print only biblios (which results in missing entries or a blank page). -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7468] Add label to batch by barcode range
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '20

16 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7468 --- Comment #33 from Maryse Simard <maryse.simard(a)inlibro.com> --- Created attachment 97455 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=97455&action=ed… Bug 7468: Fix 'false' message on Firefox It seems I was using an href to a javascript function in the 'Print Range' button, which Chrome didn't mind, but Firefox did understand. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7468] Add label to batch by barcode range
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '20

16 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7468 --- Comment #32 from Maryse Simard <maryse.simard(a)inlibro.com> --- Created attachment 97454 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=97454&action=ed… Bug 7468: Print barcodes by range Adds an option to the label creator to print a range of barcodes. Only allows printing to PDF. C4/Label.pm had to get minor changes to override database-based barcode generation. Same with labels/label-create-pdf.pl. By default, the barcode is fetched from the database using the itemnumber, but when printing ranges, you might not have a corresponding database entry. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 24273] New: It is possible to incorporate IIIF compatibility in Koha Bibliographic catalog
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '20

16 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24273 Bug ID: 24273 Summary: It is possible to incorporate IIIF compatibility in Koha Bibliographic catalog Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: urrape(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org IIIF is becoming a "de facto" standard for image interoperability. Many libraries and other institutions are aligning to the IIIF framework for image visualization. It will very usefull If we can incorporate to the OPAC bibliographic record, the visualization of images representing the documents using IIIF manifests or using images served in IIIF compatible image servers. Today you can upload images linked to bibliographic records and you can visualize those images as part of the bibliographic record detailed view. With IIIF compatibility, that option can be very open interoperating with images collections that represent the bibliographic record. That will give KOHA a natural connection with digital representations of documents in a descentralized and interoperable way. There are client side solutions as openseadragon and others. The digital representations of documents in images can be in any IIIF images server and collections of images can be linked trough the manifest standarized in the IIIF presentation API. Other LIS are incorporating IIIF interoperability. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 14792] Fix visibility check for 'place holds' link in OPAC result list
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '20

16 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14792 Patrick Robitaille <patrick.robitaille(a)collecto.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrick.robitaille@collecto | |.ca -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23089] New: Elasticsearch - cannot sort on non-text fields
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '20

16 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23089 Bug ID: 23089 Summary: Elasticsearch - cannot sort on non-text fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Target Milestone: --- issues is defined as an sum field, this is interpreted to ES as integer, however, the issues__sort field is stored as keyword. Attempting to order search results by 'popularity' fails from ES - because we can't use text fields, we have to use a 'keyword' field. In our biblio search indexes this is fine because our __sort fields all get a phrase keyword field We onyl set field__sort.phrase for text fields though, so issues__sort doesn't use the phrase field, even though it exists Adding a test to try to ilustrate what I am saying here To recreate: 1 - Enable and index ES 2 - Search on staff client or OPAC 3 - Attempt to sort by popularity 4 - It fails, check the error logs to see why -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 4234] Automatic transfer shouldn't take precedence over a hold transit
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '20

16 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4234 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|24299 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24299 [Bug 24299] Record if a transfer was triggered by 'rotating collections' -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 4234] Automatic transfer shouldn't take precedence over a hold transit
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '20

16 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4234 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|24298 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24298 [Bug 24298] Record if a transfer was triggered by 'return to homebranch' -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0