Emergency Closing documentation update
Bug #1871692 reported by
Lindsay Stratton
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned |
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
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: admin-pages |
tags: | added: documentation |
Changed in evergreen: | |
assignee: | nobody → Susan Morrison (smorrison425) |
Changed in evergreen: | |
assignee: | nobody → Andrea Neiman (aneiman) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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).