Emergency Closing documentation update

Bug #1871692 reported by Lindsay Stratton
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

I just discovered today that if emergency closed dates need to be extended, editing the end date does not push out due dates falling after the original end date. A second emergency closed date, it can encompass the original date, needs to be added.

Example: Library has emergency closures March 16 - April 1, which need to be extended to April 26. If the closure is edited, items due after April 1 will not be updated. A second emergency closed date of March 16 - April 26 needs to be added and processed.

Lindsay Stratton
Systems Librarian
Westchester Library System

Tags: admin-pages
Changed in evergreen:
status: New → Confirmed
importance: Undecided → Medium
tags: added: admin-pages
Revision history for this message
Terran McCanna (tmccanna) wrote :

This has been very confusing for our libraries. The most reliable way I have found to make sure that the emergency processing completes and there aren't any conflicts with other closed dates is to delete the previous entries (in this case, the March 16-April 1 entry) and re-enter the full, longer date range (in this case, March 16 - April 26).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.