Replies posted by mheinze57

2 Replies

Elka Sierra
Seasoned Practitioner
Elka SierraSeasoned Practitioner

Data Model UI Updates - April Release

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.

971
M
Committed
25 days ago
N
Active
neel.boseActive
asked in Academy Discussions

Cognite Training on Flexible Data Modelling (Hands-on)

I’m also keen on learning how to best use the UI within CDF to do data modelling. Much of what is in the documentation is all based on YAML files and programmatically configuring everything. I’m much more of a visual person and I suspect many find it simpler to model their data in a more WYSIWYG fashion similar to many graphdb products like Neo4J. Even the basic lift station and pump example (which barely scratches the surface) is pretty intense to keep track of in your head, especially when you have to intentionally think about spaces, containers, instances, etc. If you had a way to visually convey the idea of spaces and containers as schemas and maybe even Right Click->New Node and then walk through a simple wizard that with a few choices would create all of the backend magic, that would be a much better user experience. In fact, what would be fantastic is to take the lift station/pump example and show how that is done within the Data Modelling section in CDF in a YouTube video. T

3
T
Practitioner
3 months ago

Badge winners

Show all badges
Terms & ConditionsCookie Settings