Currently in the ProjectInfo schema we have separate fields / slots for each role:
project_developer
project_verifier
project_monitor
And for Terrasos we additionally have:
project_owner
project_operator
Rather than supporting each of these with a different field, we could instead have a single project_roles slot (multivalued) where the values each had an Enum field which detailed which role the given individual or organization was being assigned to.
This was something @S4mmyb brought up during our recent Framework WG call, but we should speak w/ the rest of the dev team to get input as we may need to refactor our existing anchored project metadata documents.
Currently in the
ProjectInfoschema we have separate fields / slots for each role:And for Terrasos we additionally have:
Rather than supporting each of these with a different field, we could instead have a single
project_rolesslot (multivalued) where the values each had an Enum field which detailed which role the given individual or organization was being assigned to.This was something @S4mmyb brought up during our recent Framework WG call, but we should speak w/ the rest of the dev team to get input as we may need to refactor our existing anchored project metadata documents.