Make enum fields more visible to contributors

[mshadbolt]

Description

As a metadata team member I want to make it obvious to users who are completing metadata for the DCP that a particular field is an enum and if it is, what the available values are that they can use.

I don't have a good idea on how to implement this in practice. The enum options are currently present in the json schema but they are not visible to contributors nor the wrangler when they are filling in the metadata spreadsheet.

Acceptance Criteria

• A plan on how make enum fields more visible
• Enum fields are obvious to contributors

[ESapenaVentura]

The problem is that currently, when creating the spreadsheet, for every field it feeds on the "example" field inside that field. This is a string written by a human and it might not get updated every time a new field is added. Also, showing in row number 3, in light grey, might not get noticed.

To solve this, I think we should, if the field is an enum, add data validation with custom rules (https://openpyxl.readthedocs.io/en/2.5/validation.html) when creating the spreadsheet.