These dates are in addition to your regular weekly closed days. Both regular closed days and those entered in the Closed Dates Editor affect due dates and fines:

Closed dates do not affect the processing delays for Action/Triggers. 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.
2. Select Closed Dates Editor.
3. Select type of closure: typically Single Day or Multiple Day.
4. Click the Calendar gadget to select the All Day date or starting and ending dates.
5. Enter a Reason for closure (optional).

6. 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.

   Note

   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.

7. Click Save.

Now that your organizational structure is established, you can begin configuring permissions for the staff users of your Evergreen system.