OW2 MRL issueshttps://gitlab.ow2.org/ow2/mrl/-/issues2021-05-17T13:33:14Zhttps://gitlab.ow2.org/ow2/mrl/-/issues/97description for of key/label name2021-05-17T13:33:14ZMartin Hamantdescription for of key/label nameIn the screenshot below the label `act_bugs` seems to come from the database (table `Aggregate`, field `AggregateName`).
In this example, `act_bugs` is the label for the human-readable `Bug Handling` aggregate as documented in [MRL's Sta...In the screenshot below the label `act_bugs` seems to come from the database (table `Aggregate`, field `AggregateName`).
In this example, `act_bugs` is the label for the human-readable `Bug Handling` aggregate as documented in [MRL's Stage 2](https://www.ow2.org/view/MRL/Stage2-ProjectAttributes#HComputation).
At some point we might want to be able to display a human readable "full name" to the end user rather than a system-like key/label
![image](/uploads/2af2bd27f597990c083589ac8d0a16dd/image.png)
![image](/uploads/fb2f81808cc78d6852472752d618cc6f/image.png)
When could leverage the `Description` field for this, and get it exposed by the API then get it displayed somehow in the dendrogram