 |   | |
| HomePrev | Part VI. System Administration From the Staff Client | Next |
|---|
Table of Contents
Before floating groups copies could float or not. If they floated then they floated everywhere, with no restrictions.
After floating groups where a copy will float is defined by what group it has been assigned to.
Each floating group comes with a name and a manual flag, plus zero or more group members. The name is used solely for selection and display purposes.
The manual flag dictates whether or not the "Manual Floating Active" checkin modifier needs to be active for a copy to float. This allows for greater control over when items float. It also prevents automated checkins via SIP2 from triggering floats.
Each member of a floating group references an org unit and has a stop depth, an optional max depth, and an exclude flag.
The org unit and all descendants are included, unless max depth is set, in which case the tree is cut off at the max depth.
The stop depth is the highest point from the current copy circ library to the checkin library for the item that will be traversed. If the item has to go higher than the stop depth on the tree the member rule in question is ignored.
As mentioned with the org unit, the max depth is the furthest down on the tree from the org unit that gets included. This is based on the entire tree, not just off of the org unit. So in the default tree a max depth of 1 will stop at the system level no matter if org unit is set to CONS or SYS1.
Exclude
Exclude, if set, causes floating to not happen for the member. Excludes always take priority, so you can remove an org unit from floating without having to worry about other rules overriding it.
To report a problem with this documentation or provide feedback, please contact the DIG mailing list.
© 2008-2015 GPLS and others. The Evergreen Project is a member of the Software Freedom Conservancy.
