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
That list of concepts looks to me a laundry list... With that approach it takes significant time to users to learn the dependencies and hierarchy.
I think we should have a more structured/hierarchical list of concepts, kind of a hierarchical taxonomy of concepts in that page showing in a clear image 1:1 or 1:many relationships between assets, etc.
Something like:
Workspace
---Experiment
-----Runs
-------Parent Run
----------Child Run
-------Models
etc.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 134791cd-db3b-b729-607e-22be8dcddf9a
Version Independent ID: bed88b29-334f-6a9a-912f-1487da4afa14
Hi @CESARDELATORRE Thanks for your feedback. We had a taxonomy based approach for this document originally, and I believe it was changed to the current arrangement after feedback from customers and discussion with the engineering team.
I'll open a work item to revisit this decision and see if it's something we want to change.
That list of concepts looks to me a laundry list... With that approach it takes significant time to users to learn the dependencies and hierarchy.
I think we should have a more structured/hierarchical list of concepts, kind of a hierarchical taxonomy of concepts in that page showing in a clear image 1:1 or 1:many relationships between assets, etc.
Something like:
---Experiment
-----Runs
-------Parent Run
----------Child Run
-------Models
etc.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: