Software tier should be part of the indicator schema

[vuillaut]

The csv file https://github.com/EVERSE-ResearchSoftware/indicators/blob/main/docs/consensus_summary.csv adds an extra layer of maintainability that will break over time when we add or modify indicators as json files (and don't modify the CSV file).

In my opinion, the software tier recommendation should be part of the indicator schema to keep information in a single source of truth.

[dgarijo]

This is a good point, but I would like to keep separate the metadata of each indicator with the recommendations for each tier.

So we may model it in the schema (I will look into this), but the data, I would keep separate. Why? Because you could have recommendations that don't go for the tiers, they could be community specific.

This is not a super priority at the moment, as we have more pressing issues.

[vuillaut]

but the data, I would keep separate. Why? Because you could have recommendations that don't go for the tiers, they could be community specific.

Ok, this is a good point I did not foresee...
Maybe a simple test would do the trick then.