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

[Bug 31235] New: UseDaysMode is used for calculating the expiration date for waiting holds
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31235 Bug ID: 31235 Summary: UseDaysMode is used for calculating the expiration date for waiting holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This is also a confusing one: The UseDaysMode system preference, that can also be set in the circulation rules is described as: ... when calculating the date due. BUT: In set_waiting it's also used to calculate the expiration date for holds: my $max_pickup_delay = C4::Context->preference("ReservesMaxPickUpDelay"); my $cancel_on_holidays = C4::Context->preference('ExpireReservesOnHolidays'); my $expirationdate = $today->clone; $expirationdate->add(days => $max_pickup_delay); if ( C4::Context->preference("ExcludeHolidaysFromMaxPickUpDelay") ) { my $itemtype = $self->item ? $self->item->effective_itemtype : $self->biblio->itemtype; my $daysmode = Koha::CirculationRules->get_effective_daysmode( { categorycode => $self->borrower->categorycode, itemtype => $itemtype, branchcode => $self->branchcode, } ); my $calendar = Koha::Calendar->new( branchcode => $self->branchcode, days_mode => $daysmode ); $expirationdate = $calendar->days_forward( dt_from_string(), $max_pickup_delay ); } I feel like this is quite odd as you can set ExcludeHolidaysFromMaxPickUpDelay to ignore the calendar (and then it will be ignored). But if you set it to use the calendar, it can still be ignored when the UseDaysMode setting is set to ignore calendar. So it should probably be: Ignore the calendar | Use UseDaysMode setting ... If asked previously, I'd have said don't make this rely on UseDaysMode and just use calendar or not. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 30381] New: On order items still available for item level holds with TrapHoldsOnOrder
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30381 Bug ID: 30381 Summary: On order items still available for item level holds with TrapHoldsOnOrder Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When TrapHoldsOnOrder is set to not trap holds with negative not for loan status, it's still possible to place an item level hold on these items in the OPAC. To test: - Create an item with not for loan -1 = on order - Set OPAC item level holds to 'Force' for its itemtype in circulation conditions - Try to place a hold on it from the OPAC - Notice that a checkbox to select the item displays and you can place a hold -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 32246] New: Standardize start page layout between different modules
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32246 Bug ID: 32246 Summary: Standardize start page layout between different modules Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The reports, cataloguing and Koha start page all leave room to the left, but the circulation page does not. It would be nice to adapt it for more consistency :) Also makes me wonder how to use that space - we have the news on the start page, maybe we could make this the dedicated area for IntranetReportsHomeHTML etc.? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 24550] New: Books renewals triggers item loan policies to revert to branch renewing item
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24550 Bug ID: 24550 Summary: Books renewals triggers item loan policies to revert to branch renewing item Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: rrussell(a)pacificoaks.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 98192 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=98192&action=ed… Renewal changes item policies Since the new update, we've noticed issues with our items not following policies from their home branch, triggering overdue notices, causing issues with holds, not charging fines, and reverting to the default branch. Not certain if self renewal is triggering this as well. These were never issues before. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 31277] New: The LinkerOptions system preference should supply a list of available options
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31277 Bug ID: 31277 Summary: The LinkerOptions system preference should supply a list of available options Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Reading the code, it seems only 'broader_headings' is implemented. Are there other options? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 31340] New: Add record review and publish permission separate from edit (change edit_catalogue permission)
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31340 Bug ID: 31340 Summary: Add record review and publish permission separate from edit (change edit_catalogue permission) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be helpful for some bigger libraries to set up a cataloging workflow where some librarians have permissions to add bibliographic and item records to Koha but these are not visible immediately in the OPAC. This would be archived after they are reviewed by another librarian. Actually it is possible to mimick this workflow with some opac hide features present in Koha, but not on the permission side. That implies that it is a workflow that rests on the responsability of "data entry" cataloguers to not change records. This new feature would implicate to add to the current permission "edit_catalogue" two new permissions: "add_catalogue_records" and "review_and_publish_records". First permission "add_catalogue_records" would enable only to add new records, not to edit records. These records would be marked as hidden in the OPAC. Second permission "review_and_publish_records" would enable the record to be seen in the catalog. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 22773] New: Bulk Close invoices
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22773 Bug ID: 22773 Summary: Bulk Close invoices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The invoice screen shows all invoices and is not filtered by open and closed. We propose to: 1. Create a closed tab on the invoices view. 2. Move all closed invoices to a closed tab on the invoices view. All open invoices would remain in the open tab until closed. This would provide the filtering needed and clean up the display for users. 3. Allow users to select multiple invoices on the Open tab and then provide a button on the screen to 'close selected invoices' in bulk. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 79

[Bug 32191] New: Consistent upgrade messages
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32191 Bug ID: 32191 Summary: Consistent upgrade messages Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Our use of 'say $out' is not really consistent, and we need to tidy it for the release. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 24669] New: Editing circulation rule breaks holds when total holds unlimited
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24669 Bug ID: 24669 Summary: Editing circulation rule breaks holds when total holds unlimited Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 18936 Add a new rule, leave holds values empty and save. After saving, the values show in the table as 'unlimitd' Edit the rule, the editor shows the values not empty, but the string 'unlimited'. Saving the rule now without fixing this means you can no longer place holds. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18936 [Bug 18936] Convert issuingrules fields to circulation_rules -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 32063] New: Streamline importing of records
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32063 Bug ID: 32063 Summary: Streamline importing of records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Since bug 27421, importing records is managed in background jobs. I feel like this has added steps/clicks to something that was already click-heavy. Before (basing off of 22.05), to import a record file 1. Go to Tools > Stage MARC records for import 2. Click Browse and choose the file 3. Click Upload file 4. Choose the settings 5. Click Stage for import --> The summary of the file is presented 6. Click Manage staged records --> I am taken directly to manage my file 7. If needed, choose parameters, framework, etc. 8. Click Import this file into the catalog --> File is imported --> If needed, I can view/edit the records (for bibliographic records, this is almost always since I add items manually to add the barcodes) Now (based off master 22.06.?) 1. Go to Cataloging > Stage records for import 2. Click Browse and choose the file 3. Click Upload file 4. Choose the settings 5. Click Stage for import 6. Click View details of the enqueued job 7. Click View batch 8. If needed, choose parameters, framework, etc. 9. Click Import this file into the catalog Mine, for some reason, never works on the first try, so I have to go back and click Import this file into the catalog again, then it works. I hope this is just me... 10. Click Manage imported batch (if needed to see the records to add items for example) So it's not that many new clicks, but it's still two more steps than before, 10 vs 8 (or four more if the import doesn't work on the first try like mine!) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4