Once you have your mdrCore Database installed and deployed to a server as indicated in the mdrCore Install wiki page, you can access the homepage using http://serverHostURL:port
Example: http://localhost:8080 or http://mdr.triadcommunity.org:8080
- Log in as "admin" user
- After logging in, there are 4 different options/buttons available for the user on the top left hand side of the screen.
Shows contents in the openMDR Core metadata registry. The user can click on "data element", "value domain", "data element concept", "object class", "property", "conceptual domain" in order to view registry contents. Another way to browse through the repository is to click on alphabets abc...xyz. Registry contents starting with specific alphabets will be displayed on the page.
A user can search the contents of metadata registry using a keyword and filtering by the type of component in the registry.
All reference documents uploaded by administrators can be seen on this page, and users can search documents using keyword.
All semantically annotated model files can be uploaded and stored by the users for future reference.
Link to help and reference material on openMDR wiki site.
Maintenance of the metadata registry is allowed only to the administrators. There are 3 tabs available and the actions include:
Users can create new content: organization, context, conceptual domain, object class, property, value domain, data element concept, data element, reference document, datatypes and unit of measure.
An Organization can play one or more roles with respect to a Metadata Registry. The roles currently recognized in this part of ISO/IEC 11179 are: Registration Authority, reference organization, or steward of an Administered Item.
Each Administered Item is named and defined within one or more Contexts. A Context defines the scope within which the subject data has meaning. A Context may be a business domain, an information subject area, an information system, a database, file, data model, standard document, or any other environment determined by the owner of the registry. Each Context is itself managed as an Administered Item within the registry and is given a name and a definition.
A Conceptual Domain is a set of Value Meanings, which may either be enumerated or expressed via a
description. An Enumerated Conceptual Domain contains a finite allowed inventory of notions that can be enumerated. A Conceptual Domain that cannot be expressed as a finite set of Value Meanings is called a Non-enumerated Conceptual Domain. It may be expressed via a description or specification.
An Object Class is a set of ideas, abstractions, or things in the real world that can be identified with explicit boundaries and meaning and whose properties and behavior follow the same rules. It may be either a single or a group of associated concepts, abstractions, or things.
A Property is a characteristic common to all members of an Object Class. It may be any feature that humans naturally use to distinguish one individual object from another.
A Value Domain provides representation, but has no implication as to what Data Element Concept the values are associated nor what the values mean. A Value Domain is associated with a Conceptual Domain and provides a representation for the Conceptual Domain. An Enumerated Value Domain is one where the Value Domain is expressed as an explicit set of two or more
Permissible Values. A Permissible Value is an expression of a Value Meaning within an Enumerated Value Domain. It is one of a set of such values that comprises an Enumerated Value Domain. Each Permissible Value is associated with a Value Meaning. A Value Domain may be expressed via a description or specification, such as a rule, a procedure, or a range (i.e., interval), rather than as an explicit set of Permissible Values. Such a Value Domain is call a Nonenumerated Value Domain.
A Data Element Concept is a concept that can be represented in the form of a data element, described independently of any particular representation. A Data Element Concept may have zero or one Object Class and zero or one Property. A Data Element Concept thus has a Definition independent from the Definition of the Object Class or the Property.
A Data Element is considered to be a basic unit of data of interest to an organization. It is a unit of data for which the definition, identification, representation, and permissible values are specified by means of a set of attributes. A Data Element is the association among a Data Element Concept, a Value Domain and optionally a Representation Class. A Data Element is formed when a Data Element Concept is assigned a representation. One of the key components of a representation is the Value Domain, i.e., restricted valid values.
An Administered Item may be described by one or more Reference Documents.
An Annotated Model is an information model that has been created using Enterprise Architect and has been annotated using openMDR EA Plugin with Data Elements existing in local or remote openMDR and caDSR. These annotated models can be exported from EA tool in as .xmi file and can be stored in openMDR for future use.
A Value Domain is associated with a Datatype — a set of distinct values, characterized by properties of those values and by operations on those values, for example the category used for the collection of letters, digits,
A Value Domain may be associated with a Unit of Measure — the unit in which any associated
Data Element values are specified. The unit is designated by a unit of measure name.
- The system allows for checking on errors and inconsistencies in the metadata registry via 3 different reports:
4.ii) a) Report on broken Links
4.ii) b) Report on Duplicate Id's
4.ii) c) Report on inconsistent Id's
The 4th report is the schema report.
The Administration tab allows actions for managing:
4.iii) a) Organizations - You can click to view all the listed organizations and can edit them if required
4.iii) b) System Status - One can view the status of server on which mdrCore is running on.
4.iii) c) Manage Users
mdrCore Database allow you to manage users assigned different roles. A user can exist in one of the following three different roles :
(1). dba: The user with dba role has administration level privileges like adding, editing and removing a user.
(2). user: With this role a registered account comes in the general category of usage of the openMDR and is restricted to access the Manage Users page.
(3). guest: A guest user is very limited privileges and is not allowed to even access the Maintenance page.
After appropriate login to the openMDR, you can view the User Management page(if you are logged in as a admin/dba) by clicking on the hyperlink "Manage Users" under the Maintenance page.
(1). "Admin" is the superuser with dba role and has got all the privileges. Any other user with dba role cannot Edit or Remove Admin user.
(2). Current Logged in user cannot be removed.
(3). Admin or dba can only change the password of "users" group
- Creating New Users : A dba / admin can create a new user by clicking the "New User" button on the User Management page. A form will appear where the required information for the user may be entered to create the user.
- Editing Existing Users : An existing may be edited by a dba / admin by selecting the desired user and clicking the "Edit" button. A form will appear where the required information to be edited for the user may be entered.
- Removing User : A user may be removed by selecting the desired user and clicking the "Remove" button.