Home3.3 TrainingAdministration->Local AdministrationEntering Holidays: Closed Dates Editor

9.4. Entering Holidays: Closed Dates Editor

Set closed dates using the Closed Dates Editor.  This is a yearly task for people with LibAdmin Permissions.

Closed dates effect due dates and fine accrual policies.  It is important to set regular weekly closed days and holidays or special days that your location is closed.

Closed dates do not affect the processing delays for Action/Triggers or scheduled reports. For example, if your library has a trigger event that marks items as lost after 30 days, that 30 day period will include both open and closed dates.

Adding a closure

  1. Select Administration > Local Administration-->Closed Dates Editor.
  2. Choose Location from the dropdown menu Edit Closed Dates. 
  3. Add closing and complete the form (sample below) for your holiday.
  5. Click Apply to all of my libraries if your organizational unit has children units that will also be closed. This will add closed date entries to all of those child libraries.
    By default, creating a closed date in a parent organizational unit does not also close the child unit. For example, adding a system-level closure will not also close all of that system's branches, unless you check the Apply to all of my libraries box.

  6. Notice the option for Possible Emergency Closing?  This feature would be used if you needed to close on Short Notice, such as a weather event.  It pushes item due dates to the next day.  There are some minor bugs associated with the feature.

  7. Detailed closure is an option to use to close just part of a day, like for a half-day holiday.

Your result of successful Closed Dates entry will look a lot like this:


Supplemental Content:  See added thoughts on SPARK Support Plans for this feature in File Download.

Knowledge Tags


This page was: Helpful | Not Helpful