Open marikapop opened 8 months ago
Imho better would be to split the field into "sensitivity" (sensitive/non-sensitive) and (re)-identifiability (identifiable, re-identifiable and non-re-identifiable).
But it also clashes with de-identification status attribute of data declaration. So more analyses is needed.
Is your feature request related to a problem? Please describe. Some projects use SMASCH to keep correspondence table. This dataset is identifiable and non-sensitive. DAISY does not have such class of sensitivity.
Describe the solution requested Add "identifiable non-sensitive" to sensitivity classes.
Other info context It is related to data classification procedure in general.