The following diagram illustrates the primary architectural components
of the automatic classification subsystem and the steps involved using
the XML Classifier as the plug-in.
Classification flowchart that uses the XML Classifier
<BEGIN
TRANSACTION>
- The client checks in the target document with the automatic classification
flag set. The document's initial class security descriptor is set at this point.
Automatic classification has not yet taken place.
- Content Platform Engine saves
properties and content. The classification status on the document
is set to Pending.
- Content Platform Engine queues
a classification request. The request includes a reference to the
target document.
<END TRANSACTION>
<BEGIN TRANSACTION>
- The dequeueing thread dispatches the classification request to
Document Classification Manager.
- Document Classification Manager determines the MimeType from the
source document and queries the database for a Document Classification
Action with a MimeType of text/xml.
- Document Classification Manager invokes the XML Classifier, passing
it a reference to the target document.
- The XML Classifier parses the target document to determine its
XML document type and queries the catalog for an XML Property Mapping
Script that matches this type. (If the XML Classifier cannot determine
the XML document type, it fails with an appropriate error.) For more
information, see How
the classifier chooses a script.
- The XML Classifier applies the XSL script to the target document
to determine the property mappings.
- The XML Classifier changes the class of the target document and
updates its properties based on the property types and values determined
by the mapping script.
- Control returns to Document Classification Manager.
- Document Classification Manager sets the ClassificationStatus
on the target document to Complete or Failed, depending on the return
value from the XML Classifier.
<END TRANSACTION>