MDR Component - Metadata Registry

Datum: Designation whose concept is a value.

 Designation: Designation whose concept is a value.  

Value: Designation whose concept is a value.

Metadata is defined as follows:  Descriptive data about an object

In essence this metadata will tell us how the data is stored, what it's context is, what it is related to, and ideally how and where we can use it. It doesn't actually tell us what the data is, for instance the metadata may well tell us that a company holds information about it's employees in a particular format in a) a MySQL database and in b) an HR department spreadsheet.  It can also tell us that the database may store a value for the employees telephone number, but that the HR spreadsheet does not, however it doesn't tell us the details of the employees held on these two data-sets.

Why do you need a Metadata Registry?

A Metadata Registry provide the ability to :

• Administer and manage diverse data-sets by centrally controlling the content and versioning of data-sets.
• Ensure data consistency between different platforms and systems
• Ensure data interoperability between systems
• Compare & analyse different data-sets from different legacy projects
• Automatically ensure data consistency in new applications and projects

The Metadata Registry built into the Model Catalogue will provide all these features, and make them available through REST interfaces to other Model Catalogue components as well as to external systems.

With every small department in an enterprise holding data in many diverse databases and systems a metadata registry is the most convenient means of identifying what data is held where.