5.2.3.1. Data Supplier-to-Consumer Matrix Overview
Data are managed and stored in ways to optimize their use. The Data Supplier-to-Consumer Matrix is organized by the typical optimization patterns, and can be used for identifying the use of a data repository (from the perspective of a COI), the information exchange methods appropriate for these uses, and the services that should be provisioned for each use. Note that these repositories are Data Assets within the DRM abstract model. The Matrix is comprised of four quadrants, each related to the primary use of an underlying data repository. Figure 5-1 below depicts the FEA DRM Supplier-to-Consumer Matrix: (3XM9)

• Quadrant I - Transactional Databases: These databases contain structured data objects that support business process and workflow. These structured databases, when well designed, tend to be highly normalized and optimized for transactional performance. Quadrant I repositories include the databases supporting On-Line Transaction Processing (OLTP) Systems, Enterprise Resource Management Systems (ERPs), and other “back-office” systems that implement core business processes and workflows. The data within these repositories tend not to be directly accessible to create, read, update, and delete (CRUD) operations, except through services usually in the form of application program interfaces (APIs) because of the need to enforce business logic and referential integrity within the database. (3XME)

• Quadrant II – Analytical Databases: These databases contain structured data objects that support query and analysis. These structured databases tend to be purposefully de-normalized and optimized for query ease and performance. The data in these repositories are typically obtained from one or more Quadrant I databases and structured to support answering of specific questions of business and/or mission interest. Quadrant II repositories include On-Line Analytical Processing (OLAP) systems, data warehouses, and data marts. Quadrant II also includes directories (e.g., repositories that support the Light Weight Directory Access Protocol (LDAP) or X.500). Data in these repositories tend to be directly accessible for query and read. Create, update and delete operations are typically performed more indirectly than in transactional databases through an extract, transform, and load (ETL) process. (3XMA)

• Quadrant III – Authoring Systems Repositories: The term “document” within the DRM context is broadly defined to encompass a wide range of information objects. These objects may be in any of a variety of formats: multimedia, text documents with embedded graphics, XML Schema or DTD instances. Generically, in this context, the term “authoring system” is equally broad in scope. At one extreme, an “authoring system” may be a digital camera. At the other, an authoring system may implement a complex workflow used for the production of a formal publication. In either extreme, the products of an authoring system are documents. The underlying repositories used by authoring systems may also be of any of a variety of constructs to store data objects, file systems and relational databases being the most common. In general, as in Quadrant I repositories, direct data-level access to the repositories underlying enterprise-level authoring systems is not prudent. Bypassing the business logic within the authoring system may affect the integrity of the data (e.g., version control of documents). (3XMB)

• Quadrant IV – Document Repositories: Like Quadrant II repositories, document repositories store data objects so as to optimize discovery, search and retrieval. These repositories include the file systems underlying websites, relational databases underlying content management systems, XML registries and repositories. In general, as in Quadrant II repositories, data tend to be directly accessible to query. Create, update and delete operations are not generally available to end users, but are provided through a publication function performed through an authoring system. (3XMC)