An example XML hierarchy of metadata for a printed 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>130.119.46.229</host>
<device type="printer" local="false" server="UK-PRINTSVR"
location="Taunton, Mezzanine">PrintMaster 2000</device>
<application>WINWORD.EXE</application>
<created>2010-04-19T10:54:42.237</created>
<size>30276</size>
<subject>Microsoft Word - Q2 Strategy.docx </subject>
<property_set name="Print">
<property name="Pages" type="xs:unsignedInt">1</property>
<property name="Comment" type="xs:string"/>
<property name="Paper" type="xs:string">Letter 8 1/2 x 11 in</property>
</property_set>
<stream name="Page 1.emf">
<size>30276</size>
<type>data</type>
</stream>
<hash type="sha-256">7EBFC9D20069500208FD5B144B9F73F58A3705F
F5C293B1943E35C852BD683AD</hash>
</file>
</event>
</apm>
As far as possible, CA DataMinder attempts to fully populate the event metadata with relevant attributes. However, the range of available metadata items will vary. For example, location details may not have been configured for the printer.
|
Copyright © 2014 CA.
All rights reserved.
|
|