4.6. Data Context Example (3XLU)
This section provides a usage example for the Data Context standardization area. It is based on an existing implementation of the DRM at DOI, for the Recreation One Stop initiative. One or more contexts for an entity may be conveyed by creating an association between the entity and a context item that is part of a classification scheme. For example, an exam may be given at a university for different purposes. One purpose may be to evaluate the student’s ability to meet the requirements of a course, as with a midterm or final exam for a given semester. Another purpose may be that of a comprehensive exam for a graduate program, in which the exam is intended to evaluate the student’s capabilities as an expert in their primary field of graduate study. In each of these cases, the “exam” entity has a different context because it is associated with a different context item – one context item relating to a semester, another relating to a graduate program. Each of these context items can be considered to be part of a classification scheme involving types of exams. (3XLL)
Figure 4-3 DOI DRM Classification Schemes (3YQ1)
Figure 4-3 depicts examples of five different classification schemes as applied to a single entity within the DOI DRM implementation: (3XLM)
The entity in this example is a data entity called RECREATION-AREA. Classification scheme (1), which provides subject area and information class context, represents part of a high-level data architecture listing subject areas and information classes. Two topics (more precisely, a topic and a subtopic) from this classification scheme are shown, and a “subclass-of” relationship exists between the parent topic RECREATION and the child topic RECREATION INVENTORY. This conveys that the RECREATION-AREA is part of the RECREATION INVENTORY. (3XLN)
Classification scheme (2), which provides organization context, represents part of an organization hierarchy for a federal department. One topic from this classification scheme is shown, and relating the RECREATION-AREA entity this topic (“National Park Service”) indicates that a recreation area is used or processed by the organization known as National Park Service. This categorization capability also provides a mechanism to identity common data across organizations. (3XLO)
Classification scheme (3), which provided business context using the FEA BRM, represents part of the FEA BRM taxonomy. One particular sub-function topic (“Recreational Resource”) is shown, along with the its parent hierarchy topics for LoB (“Natural Resources”) and Business Area (“Service for Citizens”). The RECREATION-AREA entity is related to the FEA BRM sub-function of “Recreational Resource”, which establishes the business context for this entity. This indicates that data about a RECREATION-AREA is typically created, updated, processed or deleted by systems that support the Recreational Resource sub-function. (3XLP)
Classification scheme (4), which provides service context, indicates specific services related to the processing of RECREATION-AREA data. One topic from this classification scheme is shown, which represents the specific purpose of a given service. Relating the RECREATION-AREA entity this topic (“Service: Get Recreation Inventory”) indicates that the entity RECREATION-AREA is part of the information model associated with this service – that is, it is a key piece of data that is provided when this service is invoked, and indicates the exact recreation area for which an inventory of recreation assets should be obtained. (3XLQ)
Classification scheme (5), which provides data asset context, indicates specific systems, applications, or physical data stores that process data related to RECREATION-AREAs. One topic from this classification scheme is shown, and relating the RECREATION-AREA entity to this topic (“Recreation Information Database (RIDB)”) indicates that instances of RECREATION-AREA data exist as records in the Recreation Information Database (RIDB). This type of context may also describe the process method that a particular system may apply to an entity, such as creating instances of the entity, updating instances, deleting instances, or simply referencing instances. (3XLR)