May 2021 - Koha-bugs - lists.koha-community.org

[Bug 20676] New: svc/barcode should allow barcode to be printed without text
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '23

28 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20676 Bug ID: 20676 Summary: svc/barcode should allow barcode to be printed without text Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org svc/barcode currently generates the barcode using $image = GD::Barcode->new( $type, $barcode )->plot()->png(); >From perldoc GD::Barcode plot() $oGd = $oGdBar->plot([Height => $iHeight, NoText => 0 | 1]); creates GD object with barcode image for the $sTxt specified at new method. $iHeight is height of the image. If NoText is 1, the image has no text image of $sTxt. ex. my $oGdB = GD::Barcode->new('EAN13', '123456789012'); my $oGD = $oGdB->plot(NoText=>1, Height => 20); # $sGD is a GD image with Height=>20 pixels, with no text. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 20894] New: Feature request: pass barcode width and height as parameters to /svc/barcode
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '23

28 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20894 Bug ID: 20894 Summary: Feature request: pass barcode width and height as parameters to /svc/barcode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org /svc/barcode does not currently accept width and height parameters, even though GD::Barcode does. We should allow these to be passed in. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 27013] New: Display an image of barcode on slips
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '23

28 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27013 Bug ID: 27013 Summary: Display an image of barcode on slips Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org It could be great if, on printed slips, we could display an image of the barcode. Especially useful when a barcode is filled in Koha but not physically present on the book (lost, etc.) or just unreadable because of its condition. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 28440] New: Inventory tool tries to put a time into DateLastSeen
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '23

28 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28440 Bug ID: 28440 Summary: Inventory tool tries to put a time into DateLastSeen Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using the inventory tool, Koha attempts to write a date and time into the datelastseen field. Since that's a date field, the update fails and the item ends up with 0000-00-00 for the date. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 28402] New: Add ability to view/edit MARC Modification Templates from the Batch Record Modification screen
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '23

27 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28402 Bug ID: 28402 Summary: Add ability to view/edit MARC Modification Templates from the Batch Record Modification screen Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org It would be nice to be able to view, and possibly edit, MARC Modification Templates from the Batch Record Modification screen. When selecting the template to use sometimes I realize I need to verify the settings in the template prior to using it. This means I have to exit the batch modification screen or open another window so that I can go to Tools and view the template settings. It would be more efficient to be able to access the templates from the batch mod screen and it would provide an extra level of confidence that the correct modification template is being used. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 24129] New: Add ability to configure some indexes to not autotruncate
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '23

27 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24129 Bug ID: 24129 Summary: Add ability to configure some indexes to not autotruncate 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: andrew(a)bywatersolutions.com To Test: - Set QueryAutoTruncate to Automatically - Set search engine to Zebra - search for sn:1 - Confirm you only get biblionumber 1 in your results - Set search engine to Elastic - search for sn:1 - confirm you get bibs 1, 10, 11, 100, etc Zebra apparently knows to ignore autotruncate for some instances. We should at least maintain that behavior. It would probably be good to go a step further and make it configurable per index in our search engine config. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 28474] New: Pass process_message_queue.pl params to before_send_messages plugin hooks
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '23

26 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28474 Bug ID: 28474 Summary: Pass process_message_queue.pl params to before_send_messages plugin hooks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be useful to send most of the process_message_queue.pl script parameters to any plugin before_send_messages hooks. For example, the Twilio Voice plugin uses before_send_messages to send phone messages, but if the script is called with "-t email", it doesn't know and will make phone calls! If that info were passed in, the plugin could be made aware of it and only make calls if no "-t" or a "-t phone" were set in the parameters. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 23059] New: reserves_stats.pl needs overhaul
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '23

26 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23059 Bug ID: 23059 Summary: reserves_stats.pl needs overhaul Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement 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 Target Milestone: --- This bug is sort of a catch-all for changes that need to be made to the holds statistic wizard, reserves_stats.pl Two big issues: - By default, the wizard sets a value for items.homebranch and items.holdingbranch. That means it unexpectedly cuts out all bib-level holds and gives no clear indication that it's done so. You *can* change home and holding branch to not limit, but it's not intuitive. - The wizard splits holds into 5 statuses (Placed, Processed, Pending, Satisfied, and Cancelled) that aren't used anywhere else in Koha. These statuses aren't explained without diving into the code and don't match how we otherwise divide and talk about holds. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 28205] New: Less important hold trapped before or no hold trapped in some cases (race condition)
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '23

25 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28205 Bug ID: 28205 Summary: Less important hold trapped before or no hold trapped in some cases (race condition) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com So our libraries ran into a strange hold problem which turned out to be a race condition: if you change priority of holds and return an item and build_holds_queue.pl cron is not yet run again the priority is not updated and you fill hold with less importance! After build_holds_queue.pl the priorities are OK because hold_fill_targets gets updated according to the right hold priority. Similar race condition also happens when you have already some items for the biblio in hold_fill_targets and add a new item to the biblio and try to return it it doesn't attach to any waiting holds until the build_holds_queue.pl is ran. To better understand the issue I think it is easier to look the code in C4::Reserves::_Findgroupreserve(). Explaining with words is bit difficult... Basically in that function the SQL selects > my $title_level_target_query = qq{ > my $query = qq{ should be UNION'ed to fix the case when adding new item which could potentially fill the hold. This might cause unoptimal logistic route to be used but still would follow the hold priority. To fix the issue of changing hold priorities we need to update hold_fill_targets table by calling C4::HoldsQueue::CreateQueue() every time staff member updates hold priorities in a biblio. But even with these improvements wouldn't this be buggy when deleting items from the biblio record? Not sure how to solve that case. Added major bug priority for this but if you feel like it doesn't deserve it feel free to change to normal. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 27873] New: Make display of patron restrictions, charges, notes, etc. consistent for check out and patron details screens
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '23

25 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27873 Bug ID: 27873 Summary: Make display of patron restrictions, charges, notes, etc. consistent for check out and patron details screens Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On the check out screen (circulation.pl) info about the patron’s account displays in the following order: expiration, restrictions, charges, notes, messages. But on the patron details screen (moremember.pl) the info displays in a different order: charges, messages, notes, restrictions, expiration. For consistency it seems like the info should display in the same order on both screens. Additionally it would help when training new staff members and when working a busy information desk to be able to rely on finding the information in the same place on both screens. Our Library prefers the sort order that displays on the check out screen because it puts the expiration date, restrictions and then charges at the top of the screen so that staff can quickly see the status of the account and handle them. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35