You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the primary paradoxes with manually creating data (this POC) and/or using the Python API (rename pending) via a REST service (this POC is unreleased at this time) was that an end user needed to understand the hierarchical/encapsulation structure of the ontology in order to properly create the CASE data. This problem still existed during the development of this DC3DD/CLI POC. To improve this, a front-end GUI or back-end data model that allowed the user to get feedback would be useful.
Note that this same issue fundamentally exists in the Python API example, except that it gives the user feedback at runtime that a parent concept is missing.
The text was updated successfully, but these errors were encountered:
One of the primary paradoxes with manually creating data (this POC) and/or using the Python API (rename pending) via a REST service (this POC is unreleased at this time) was that an end user needed to understand the hierarchical/encapsulation structure of the ontology in order to properly create the CASE data. This problem still existed during the development of this DC3DD/CLI POC. To improve this, a front-end GUI or back-end data model that allowed the user to get feedback would be useful.
Something like this would allow for a user to get instant feedback and not have to worry with weird custom encapsulation syntax (at the time used to get the POC to completion fast):
https://angular-ui-tree.github.io/angular-ui-tree/#/basic-example
Note that this same issue fundamentally exists in the Python API example, except that it gives the user feedback at runtime that a parent concept is missing.
The text was updated successfully, but these errors were encountered: