manuelma
commented
1 year ago So the metadata and description won't depend on the alternative. Each entity will have a single description and a single metadata, and multiple alternatives. That means that showing entities, alternatives, metadata and description will lead to duplicating the two latter for each row in the table. That would be awkward in my opinion.
We already have an entity metadata pane which is quite capable, have you tried it @DillonJ ? Maybe we can extend it to also handle description (or maybe the description itself should go into the metadata)?
Anyways, what I think we need is a new pane to show and edit entities and their alternatives exclusively. This could allow us to prune some of the stuff we don't want to see in the entity tree, like the node__temporal_block class.
DillonJ
jkiviluo
Currently we have parameter value and parameter definition tabs. The scope of what they display is controlled via selection in the tree. E.g. if an object class is selected, in the parameter value pane, we see only parameter values for those object classes.
However, objects/entities themselves have properties, like a description, meta data. We currently have no nice way of seeing this information, all at once. The idea here is to add a third tab that would show objects and their descriptive properties, like their description, metadata etc. This pane would work similarly to the parameter value pane where what the objects it displays is driven by selection in the tree. This pane could be used to easily create new objects/entities by simply copying and pasting into it.
We have also been discussing the issue of alternatives defined for entities and this new object/entity pane could be the place to display and manage what alternatives are associated with an object/entity, so you can have alternative "versions" of objects that each have different descriptions etc.
This new object/entity pane could also be used to display and manage "special" parameter/relationships as discussed here This. For example, the temporal structure of an entity (for example) as discussed below... but that might need more thinking through since this is not something generic and temporal structures don't apply to all entities. My feeling is that this object/entity pane should only show was is universal to all entities. and not be entity specific, which is what relationships and parameters are for.