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

[Bug 23558] New: REST API: Get an ILL request
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '24

06 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23558 Bug ID: 23558 Summary: REST API: Get an ILL request Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com Method GET /ill_requests/{ill_request_id} https://wiki.koha-community.org/wiki/Illrequests_endpoint_RFC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 22440] New: ILL API response objects inconsistent with other endpoints
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '24

06 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22440 Bug ID: 22440 Summary: ILL API response objects inconsistent with other endpoints Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Target Milestone: --- The response object returned from the /api/vi/illrequest GET route isn't consistent with response objects supplied by other routes, such as the patrons route. We have an RFC for this route here: https://wiki.koha-community.org/wiki/Illrequests_endpoint_RFC Josef has made some initial recommendations on what the properties should be named to make them consistent with other routes. We could do with expanding this RFC to make it complete, including a spec on how object embedding should be done since, to date, this is the only route that does this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 66

[Bug 23557] New: REST API: Add ILL request
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '24

06 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23557 Bug ID: 23557 Summary: REST API: Add ILL request Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com Method POST /ill_requests https://wiki.koha-community.org/wiki/Illrequests_endpoint_RFC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 23984] New: Local cover 'thumbnail' size is bigger than 'imagefile' size in biblioimages table
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '24

04 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23984 Bug ID: 23984 Summary: Local cover 'thumbnail' size is bigger than 'imagefile' size in biblioimages table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: arouss1980(a)gmail.com, jonathan.druart(a)bugs.koha-community.org, lucas(a)bywatersolutions.com, magnus(a)libriotech.no, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, tomascohen(a)gmail.com Depends on: 21987 Blocks: 23963 The original resolution to this issue, bug 21987, caused a nasty regression and has since been reverted. Opening this bug so we may pursue a new route to goal. +++ This bug was initially created as a clone of Bug #21987 +++ We use local cover images in our setup, and also resize the covers we scan to a width of 160px before uploading and attaching them to a Koha bibliographic record (we upload one cover per biblio). While using phpMyAdmin to view the contents of the 'biblioimages' table (relevant screenshot here: https://imgur.com/a/cSEVLBI) we noticed that the size of the BLOBs for the 'thumbnail' column was in some cases twice as big as that of the 'imagefile' column. In fact, this happens for more than 50% of uploaded covers as you can see from the output of the SQL queries below: mysql> SELECT COUNT( * ) AS count FROM biblioimages WHERE LENGTH( thumbnail ) > ( LENGTH( imagefile ) * 2 ) ; +-------+ | count | +-------+ | 1356 | +-------+ mysql> SELECT COUNT( * ) AS count, SUM( LENGTH( imagefile ) ) AS images_size, SUM( LENGTH( thumbnail ) ) AS thumbnails_size FROM biblioimages ; +-------+-------------+-----------------+ | count | images_size | thumbnails_size | +-------+-------------+-----------------+ | 2347 | 68323933 | 115839686 | +-------+-------------+-----------------+ It would appear that for each 160px-wide JPG with 24-bit depth that we have uploaded, the 'imagefile' column has been populated with an PNG of 8-bit depth with the same dimensions as the uploaded file, whereas the 'thumbnail' column contains a 24-bit PNG image with a width reduced to 140 pixels. I've tracked down the creation of resized 24-bit PNGs to this code: https://github.com/Koha-Community/Koha/blob/master/C4/Images.pm#L182-L183 Do thumbnails for covers need to be true colour (24-bit) images? Also, why is it that _scale_image() returns an image of 8-bit depth if the source image's dimensions are less than 600x800? (i.e. when no resizing is performed) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21987 [Bug 21987] Local cover 'thumbnail' size is bigger than 'imagefile' size in biblioimages table https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23963 [Bug 23963] Visible reduction in image quality -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 19942] New: Children's search interface
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '24

04 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19942 Bug ID: 19942 Summary: Children's search interface Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Would like to see an alternative OPAC search for patrons geared towards children. Something like this: http://www2.hampton.lib.nh.us:8080/kids?config=default#/categories It would be easy enough to customize searches, but it would be great to be able to customize a background, and add big buttons to the search topics. You will notice that the general search bar at the top limits to children's materials, and the layout of the results is EXTREMELY kid friendly. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 23361] New: Status transfert is missing on item of a rotating collection
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23361 Bug ID: 23361 Summary: Status transfert is missing on item of a rotating collection 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: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 91742 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=91742&action=ed… dialog box transfert Hi, The transfert status is missing when a return is made on an item belonging to a rotating collection. Test plan: - Put an item on a rotating collection - check out item -Set branch to a different branch - check in item - alert message is displayed "Please transfert item to holding branch Y. This item is part of a rotating collection". There is not the usual question that appears when a return is made on a document to be transferred. - in detail page of biblio, status is available, item is not in transfert status like "in transit from homebranch to holding branch". Regards Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 19518] New: Document per-site .psgi files
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19518 Bug ID: 19518 Summary: Document per-site .psgi files Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: magnus(a)libriotech.no Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org koha-plack uses /etc/koha/plack.psgi by default, but it can also use /etc/koha/sites/${instancename}/plack.psgi if one is present. This should be documented in the manpage of koha-plack and the usage embedded in the script. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 21359] New: Add RDF support to OAI-PMH harvester
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '24

02 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21359 Bug ID: 21359 Summary: Add RDF support to OAI-PMH harvester Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The OAI-PMH harvester is set up to import only MARC records into Koha. The goal of this enhancement would be to allow RDF records to be imported into Koha as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 21893] New: Batch Modify button in report with itemnumber only includes titles in first page of results
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '24

29 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21893 Bug ID: 21893 Summary: Batch Modify button in report with itemnumber only includes titles in first page of results Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 19233 added the ability to push report results into item batch modification when the report includes a column of itemnumbers. However, only items on the first page of item results will be pushed to batch modification -- if the report results include 1200 items and the report page is set to display 1000 rows per page, only the first 1000 items will be batch modified. Koha is clear that it's only modifying those 1000 items, but it still creates extra work, especially since the Rows Per Page dropdown on report results doesn't include an option for All. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 21638] New: Allow reporting of holds cancelled by cancel_expired_holds.pl and ExpireReservesMaxPickUpDelay
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '24

26 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21638 Bug ID: 21638 Summary: Allow reporting of holds cancelled by cancel_expired_holds.pl and ExpireReservesMaxPickUpDelay Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When ExpireReservesMaxPickUpDelay is set to Allow, waiting holds are automatically cancelled by cancel_expired_holds.pl. But, generally, libraries still need to physically remove those items from their hold shelf and check them in to guarantee there are not pending holds or transfers to be triggered. A report to identify these items is imperfect and cannot definitively distinguish a hold cancelled by the cron from a hold cancelled by an employee. Bug 14134 established behavior that displays holds which *will* be cancelled by the next run of the cron on the "holds over" tab in Holds Awaiting Pickup, but doesn't allow staff to see which holds have already been cancelled. It'd be great if the cron could email a list of cancelled holds. Additionally, reporting would be improved by the introduction of a new value in old_reserves.found for items cancelled by the cron (maybe E for expired). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3