An example XML hierarchy of metadata for a Microsoft Word document is shown below.
<?xml version="1.0"?>
<apm schema_version="1" xmlns="http://www.orchestria.com"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.orchestria.com xmleventattributes.xsd">
<event>
<file>
<host>UX-RIMMEL</host>
<filename}Sales_2007_Q1.doc</filename>
<path>\\UX-RIMMEL\Personal\Tips</path>
<created>2007-05-13T19:26:32</created>
<accessed>2007-05-17T08:12:44</accessed>
<modified>2007-05-16T21:05:54</modified>
<size>41984</size>
<title>Unipraxis Sales Q1 2007</title>
<subject>Sales Revenue</subject>
<author>Spencer Rimmel</author>
<property_set name="Summary">
<property prop_id="1" name="TotalEditingTime" type="xs:string">01:26:35</property>
<property prop_id="2" name="WordCount" type="xs:string">824</property>
<property prop_id="3" name="LastPrinted" type="xs:string">2007-05-17T08:14:36</property>
</property_set>
<property_set name="Custom">
<property prop_id="1" name="Security" type="xs:string">Confidential</property>
<property prop_id="2" name="Status" type="xs:string">Approved</property>
</property_set>
</file>
</event>
</apm>
As far as possible, CA DataMinder attempts to fully populate the file metadata with relevant attributes. However, the range of available metadata items will vary by file type and file source. For example, if a third-party application passes the file data to CA DataMinder in the form of a byte stream, rather than providing CA DataMinder with access to the original file, then policy triggers can test for file attributes included in the byte stream. That is, CA DataMinder cannot independently identify or determine any missing attributes.
|
Copyright © 2014 CA.
All rights reserved.
|
|