About Filtering

Filtering provides a mechanism for managing, controlling, and using XML attributes to conditionally process documents.

A system administrator must configure Astoria for filtering, then set up a filtering mechanism and make it available to users.

The Filtering method relies on two components: a defined set of filter constraints, and a set of filter rules.

Component Description
Filter Constraints A filter constraint is an XML attribute, and a list of values that are allowed for that attribute.

Customers who require a large taxonomy of attribute values can organize those values into a hierarchical structure, allowing users to navigate the hierarchy rather than scrolling an unwieldy list. See About Hierarchical Filter Constraint Values.

Filtering constraints can be defined globally, or at a cabinet or folder level. See Limiting the Scope of Filter Constraints.

An administrator can configure cabinet or folder-level filtering constraint values to concatenate with those defined at a higher level of the hierarchy or for the entire repository.

Filters A filter is a set of rules for filtering documents, based on the values of XML attributes. Each filter identifies criteria for one or more deliverables. A filter specifies one or more filter constraints, and defines which attribute values will cause either inclusion or exclusion of the element.

Once filtering constraints have been defined and filters created, an administrator specifies the filters that are available for which documents, based on the location in the repository or on the DTD used by the document.

Once filtering has been configured, users can implement filtering when editing or processing documents: