[FEATURE] customisation of data classification terms selector
Is your feature request related to a problem? Please describe.
At WUR we have a different data classification terms in our security policy: Public -> ‘Negligible’ Basic -> ‘Some’ Sensitive -> ‘Serious’ Critical -> ‘Disruptive’
Therefore, we would like to be able to apply these terms instead of the default Yoda terms. It would be nice to be able to have customised set of data classification terms for use during group creation and metadata editing.
Describe alternatives you've considered
It would be possible to adjust the metadata.json afterwards to fill in a custom value, but this is user unfriendly and a lot of work.
To change the data classification terms in the group manager the theming functionality can be used to change this for your Yoda instance. You can change the labels without any problem if you do not change the values: https://github.com/UtrechtUniversity/yoda-portal/blob/6640ec8ea22f4856130621813c4bd8b5c2ab901f/group_manager/templates/group_manager/index.html#L124-L127
To change the data classification terms in the metadata schemas you can extend the "optionsDataClassification" enumeration with the desired data classification terms:
"optionsDataClassification": {
"type": "string",
"enum": [
"Public",
"Basic",
"Sensitive",
"Critical"
],
"enumNames": [
"Negligible",
"Some",
"Serious",
"Disruptive"
]
},
We have the same problem, and also use our own terms. I didn't realise I could extend the enumeration, I've tried that and it works.
We will lose this modification if the default schema is upgraded, so it might be a good idea to not put the enumNames in metadata.json itself (the same goes for the default value of affiliation).
And we will need to discuss with SURF how to manage changes to the theming.
Ideally it would be nice if UVN (Universiteiten van Nederland) would jointly come together to find a common vocabulary to be used within universities so that classification terminology and meaning doesn't change form university to university.