Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Members
Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

CDEs loaded into target metadata repository Deliverable Template

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Under construction.png
This article is currently Under Construction. It is undergoing major changes as it is in the early stages of development. Users should help contribute to this article to get it to the point where is ready for a Peer Review.
This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.

The Common Data Elements provide the atomic set of building blocks for building CMM Subjects and CMM Messages by reference. The key aspects related to the creation of the Common Data Elements are as follows:

  • Multiple sources may be used to seed the library of CDEs. Examples of typical sources include operational systems, information systems or even existing messaging standards. The first step is to identify the key sources and define a normalised model to be loaded into the target repository.
  • CDE input is prepared by using an input metadata file. Input structures can include data models or files put through a pre-processor. The metadata file will be the input to the CDE Builder application that will build the Common Data Elements repository.
  • Logically the CDE will be a list of hierarchical data elements in XSD format. Physically the CDE will be represented by a file system directory structure which will contain XSD files for each data element type/class. A CDE Builder utility is used to create this directory structure and to populate it with XSD files and CDEs are stored centrally in a metadata repository.

After CDEs have been loaded to the central metadata repository, they are reviewed by the Information Development team. Population of CDEs is an iterative process and new sources will be added over time.

= Examples

Example for CDEs loaded into a target metadata repository

comparer forfait rio sosh portabilité calcul IMC rio orange

CDE Creation – Work Instruction Overview

This solution will outline the process for the administration of the CDE and CMM. It is proposed that the solution will be as flexible and automated as possible to allow for the addition & modification of attributes.

The proposed CDE creation process is as follows:

Center

Step 1 – Meta-data file creation

- The meta-data file can come from two sources. Exporting an ERWin data model or a section of a data model to a delimited file, or output from a preprocessor such as the XSD Preprocessor. This will be a delimited file.

Step 2 – Standardizing the delimited file

- This is to make sure that all the elements names are standardized and that the structure of the file is acceptable by the CDE building program

Step 3 – CDE creation

- The meta-data file will be the input to the CDE Building application that will build the Common Data Elements repository. Logically the CDE will be a list of hierarchical data elements in XSD format. Physically the CDE will be represented by a file system directory structure which will contain XSD files for each data element type/class. It will be the responsibility of the CDE Building program to create this directory structure and to populate it with XSD files.

Step 4 – CDE upload

- Once the CDE files have been created they will be stored centrally in the XML Canon repository. To upload the XSD files into the repository Turbo XML will be used.

Wiki Contributors
Collapse Expand Close