Data Model UI Updates - April Release

Related products: Data Modeling
Data Model UI Updates - April 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 visualize the containers and views of your data model. 

 

Isolate a view or container

You can now isolate a view or container by clicking on an item, and choosing from the Quick Filter at the bottom right corner. You can decide between isolating the view or container by itself, or show all other views and containers related to the current selection.

ZJMlWmok4E_rrVjB5YLKJvXfxWBXdRfbCDHCMFfAHNy7tRo1vMpU3ATQER5qyVFLBVZ_4uybjCx8Y54EIC93icYLGmK2ClGLHCSDzxLNtB5wrT-d7yZDaZnE6HtB4vfI74_2_lLypsWAKJ4mBb2cfkI

 

You can then further decide which related views and containers to be visible for the selected view or container.

O0lwdrdzH_eNDpZQgeUMBDchCzA0A43axj_KUh73VzNdvto0RmUyckC-QDq8QI7P8T5i8lrJqoYsy_se-HM7JvbrpQxXuK74e55p4e-HiiXnM56kOHF9BbPwpBUevmS-7NZuPNqq90RENqF_eKBCuMI

You can click “Reset” at the top in the search bar when you want to go back to the original layout when the page first loaded.

 

Clearer relationships visualization

Visualizing relationships are clearer for self referencing relationships. As well, arrows clearly identify the direction of a relationship (circle indicating source, arrowhead indicating target)

qxKzv9iGBfOlsNqZ5JE_HnljGGy9gbQZvGeGFihGxYG4SkzW63jBWl-0cqOu18DU1RZ8o1dq1by9-xT0ud79sDEX5Zw6zRWWcDB_I9fQ7fR-WG_wk272RE7YnAFybWbobBbf0S0E-vZQEaTekUA-DoY

 

As well, there is a simple way to expand an item to just see the relational properties (edge or direct relations), without seeing all properties.

XFSoll2-lQ2P5lj665IJRJ2XEPp0b6t6IsUojAHpktfv34pH8iyPrS2JUkDAulZYRMLX0_FKPM0c0DOQwpR17Oz2eJJOji0QkldOoZFEKIm2idWeY8UT5sKFVqtQxOAPzhVz_BoZ-BnjUBlmNS7FhSE

 

Identifying all Views that is powered by a Container

When choosing to view containers within a space, the selected container will list all the views that use the selected container.

sWmkSudW-dBD5UGnwCfS9TC25P69Z2MYb35MPxWrVxzC2ukSUCLib3Hs7Mjpofe5NNSJbNYYxF1Lq87GfyjwW72tFO8Qp3X48MlomlEYH6SYWaE4amlkTLbP4pqCNTohYLh-HJAWr3w_WVetA1oCka4

 

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

  • Data management - displays data from reverse direct relations
  • General - all spaces, containers and views are displayed, instead of just the first 1000

While this is a small step in the right direction, I still feel that data modelers should not be exposed to the backend components or the code interface. This experience should be purely graphical and you should be able to have an experience like Bloom in Neo4J without having to worry about the backend. Effort should be put into figuring out how to best rationalize the containers/views/spaces, etc based off of what is modeled graphically by the data modeler. Having to have a data modeler consider how to structure their model based on CDF constructs adds additional burden in considering the design and should be eliminated.

Terms & ConditionsCookie Settings