Within the ECM, the content is organized into repositories. Within each repository, the content is further broken down into various types of objects (for example, invoices, pay checks, and wiring diagrams) with each type of object having a set of properties (for example, invoice number, employee number, and pay date) that can be used to search for relevant content. Before Advantage can correctly store content in the ECM in the correct type of object with an appropriate set of property values, a relationship needs to be established between the ECM’s classification system and Advantage’s tables and data attributes. The following pages are used to establish that mapping:
ECM Type (ECMTYP) defines the types of objects stored in the repository to which Advantage will be connected.
ECM Metadata (ECMDATA) defines the properties of each object type in the repository to which Advantage will be connected.
CGI Advantage Metadata (ADVDATA) is automatically populated by a batch utility to make the attributes of Advantage tables and transaction components available for mapping to ECM object types and properties.
ECM Metadata Mapping (ECMDM) defines the individual mapping of Advantage metadata exposed in the ADVDATA table to ECM metadata exposed in the ECMDATA table.