Data Modeling UI Updates - March Release

Related products: Product Releases Data Modeling
Data Modeling UI Updates - March Release

Data Modeling provides you with the flexibility to define your own Industrial Knowledge Graphs based on relevant industry standards, your organization’s own data structures and use cases, or a combination of all of these. Large, and often complex, Industrial Knowledge Graphs might be needed to represent the full extent of your industrial data across disciplines. An important aspect of these knowledge graphs is being able to explore and iterate on both its data and its structure.

With this release, we are enhancing the Data Modeling user interface in Cognite Data Fusion to better display the underlying concepts that power your industrial knowledge graph. With this increased visibility into your models, you can have higher understanding and confidence in iterating the structure of your data model.

Space centric exploration of containers and views

Explore the structures that powers your data model by looking at the space they reside in.

KvyYUvNOn0ctIAgj2rLkwnijpIgHOYsRtA1wgZ5YnS8zTaAoW86tW6boFLgcu_JOmHDOA4awwyp8vgMQUp4h17SD8JHC86J5mycRV_p-0kfC1UX-qBAUkEmitayh1qaJtLfsTVfmrtcWVnv19TlUXeQ

When in a space, you can choose the container and view to explore their structure, and the data within.

h3r9q5dqSFkW0vzAgClDgKejqTSog23oMAN_tpOM6DFVPskZJeGF_5abBqhjmYvrcqickZwtKJzQx6fY35IlOYIbd_uwYD-m9e2X1xnlni-ANS-OCZDlwuCwiamfZeO3JKx9KwKbqK1F1S7AlHsI-ww

 

Explore containers and view information for the data model.

Within the visualizer and the data model editor, you can now explore the definition of the view, and explore the containers that power them.

iXxmua8UGYp1Z1TKr72CeRvTTUPfC0f4-c_D34bBB0REOH-6kYmd9I1omoUMTK9dv1angegsXwM7BQ3zmL-8PjL8yycICzkWYtHdhetDzhJF6eXwC6Tpwu_3TyI2eVOlHyr84iqMLS3H6Hfvb20JWz0

Beside just the raw configuration, you can also explore them more in a more relational manner via the data model visualizer.

EHKJ3joARxRfliS3e7B8Ct0xEJjwbcveBpgy_IK-3fbk7Sqexeh6mp5xITquvjw9bdxghV9I6fY7M02c0yR9W0xlb09jNk32rwJAF3zavxSBGoDdb8QEw_HL78n7r1WGT1zFlNRMQxnwXi7Z3a-XAPU

 

Data management summary + sidebar

In the data management tab, you can explore data easier with the new sidebar functionality that let’s you look through each instance and their relationship (via double clicking on the property you want to delve deeper into)

rK6vKjx19iE96OGfNlBHYE9xzJxKTJfKbkRAWvrbMrtvOlitz7omCBYXyBIa2io6brPC1q3uQO6lep6ThDDb9HRHanT0v1GSww9QYFpgPJwtvi2RQz17WWkc_2tJddkIbvNW0H3x7ND0IOIH-6O3eaM

Additionally, a new profile view enables you to better understand the totality of your data. Get an aggregated summary of the data, grouping by whichever property you would like.

8UBGzDCe9HXZ2EW59KJD4roVgsQSfLxduRT_44osuQmG8QHXAFzxxiCBFBCrGVpB4jqKC6Is0sJsA71zE_sMTL8rNyn16Cu90Q1H8bl-3RD6RroVNzq0VLU9XGnHgiJYihKCv-gEQU5cVZJkz-2mRY4

 

As part of the release, we have also added or fixed the following:

  • Data model statistics - fixed progress bar in summary not showing correct amount of nodes and edges
  • Data modeling - unit directive support
  • Data model visualization - inverse relationships not rendered correctly
  • Data management - instances not visible for views that inherited properties from another view
  • Data management - filters with dates, timestamps and sorting are working as expected
  • Data connection - new excel connection string option via “Connection” panel

Let us know if you have any questions or feature requests regarding the release below!

Can someone explain about the unit directive support?

Great question Akash,

Yes, we have recently added unit support in CDF. You can read about in more details at https://developer.cognite.com/dev/concepts/resource_types/units

In short one can assign a unit from CDF Unit Catalog (API Docs, GitHub) to a container-property. In addition to providing a unified and a structured way to represent units across CDF, values stored in this property can now be queried in a specific target unit. Documentation and examples on how to query data in a given unit.

Back to the @unit directive in GraphQL DML question; one can set a unit on a field when defining a Type in GraphQL the same way we can define default values with @default directive, this will correctly be applied to underlying container-property.
Example:

type Room {
  name: String
  area: Float64 @unit(externalId: ”area:m2”)
  temperature: Float @unit(externalId: ”temperature:deg_c”, sourceUnit: “Celsius”)
}

GraphQL DML Directives documentation

​In the example above we create a type Room. We set the unit on the field area to be square meter by setting the externalId of the @unit directive to be “area:m2”. In addition too setting the externalId for the unit of the temperature field to “temperature:deg_c” we set sourceUnit to free text “Celsius”, providing unit information from in the source system.
 

Unit external Ids come from the CDF Unit catalog, see API Docs. However if you are using UI, it will assist you with a drop down list of valid externalId values.
 

 

@Dimitry Hoff thanks for the detailed explanation. Will utilize this in our models.

Terms & ConditionsCookie Settings