Data Model Details: Difference between revisions
No edit summary |
mNo edit summary |
||
| (4 intermediate revisions by one other user not shown) | |||
| Line 8: | Line 8: | ||
** When the element was last modified and by whom | ** When the element was last modified and by whom | ||
** The model the element belongs to | ** The model the element belongs to | ||
** The [[ | ** The [[Changesets]] selected | ||
[[File:Phenom-data model-details.png|1000px|border]] | [[File:Phenom-data model-details.png|1000px|border]] | ||
Most details pages also allow the user to edit/view the tags applied to the element | |||
[[File:Phenom-data model-details entity tags.png|border]] | |||
== [[Constraint]] == | == [[Constraint]] == | ||
| Line 38: | Line 42: | ||
== [[Semantic Matches]] == | == [[Semantic Matches]] == | ||
Semantic matching of documented view attribute paths is the process that matches message fields of same or similar semantic meaning to each other to facilitate and, ultimately, automate the process of message set integration. | Semantic matching of documented view attribute paths is the process that matches message fields of same or similar semantic meaning to each other to facilitate and, ultimately, automate the process of message set integration. | ||
== [[View]] == | == [[View]] == | ||
| Line 50: | Line 48: | ||
== [[View Attribute]] == | == [[View Attribute]] == | ||
View attributes represent the data fields of a particular message and are used to document the contents of the same. | View attributes represent the data fields of a particular message and are used to document the contents of the same. | ||
[[Category:UserGuide|008_Data_Model_Details]] | |||
Latest revision as of 12:44, 22 October 2025
From the Details tab, users can review detailed information about model nodes, create new nodes, and edit or delete existing nodes. Not all of types of nodes can be created, edited, or deleted, and there are some nodes which will not appear in this user interface. The nodes accessible through the details tab and their available user interactions are summarized below. Note that from anywhere in PHENOM, if the user double clicks on a node, she/he will be redirected to the details page of the selected node.
Page format
All details pages are built in the same way:
- All the action buttons (Save, Reset, Delete) are located in the sub-tab bar in the top right corner.
- The top right corner of the page provides indications about
- When the element was last modified and by whom
- The model the element belongs to
- The Changesets selected
Most details pages also allow the user to edit/view the tags applied to the element
Constraints limit the possible values of a view attribute to which they are applied. The nature of the constraint is based on the primitive type employed by the view attribute.
Entities and associations are the basic building blocks of a Domain Specific Data Model (DSDM); they represent the different real-world entities and relationships present in the domain as well as those entities' and relationship's properties.
Measurements are a part of the Logical Data Model (LDM) and their properties can be edited within PHENOM.
LDM level systems determine the properties of measurements used in the project and direct the conversion between them.
Observables are part of the Shared Data (SDM) and cannot be created or deleted.
PHENOM's Packages function like folders that help users organize components of the project as well as their own files and content.
Platform Types are used to relate a View Attribute to an LDM Measurement. Platform Enumerations are Platform Types that have Platform Enumeration Literals relating to the realized Measurement's LDM Enumeration Labels.
Reference Point is used to provide a basis for locating and/or orienting a Measurement System.
Semantic matching of documented view attribute paths is the process that matches message fields of same or similar semantic meaning to each other to facilitate and, ultimately, automate the process of message set integration.
Platform Data Model (PDM) views represent collections of data fields which are collected and transmitted in a defined message interface.
View attributes represent the data fields of a particular message and are used to document the contents of the same.