When running safe_data, all the user permissions associated with a dataset are included in the output RO-Crate; however, this should exclude users with the 'auditor' and 'administrator' roles, as these are excluded when running safe_people. This results in RO-Crates with orphan permissions, as the permission links to a valid dataset, but to a non-existent user entity (see below):
The NA user represents an auditor account, for which no user entity exists in the RO-Crate. This should be fixed by removing the additional permission entity:
{
"@id": "#perm:1f09051d217d17c3e9b5ed92819ded26-admin-table",
"@type": "ControlAction",
"agent": {
"@id": "#person:a3bc19cc9c1269320cf2847c63a66a92"
},
"object": {
"@id": "#asset:fad6faf661584d53e58f9730b14c5aae"
},
"actionStatus": "PotentialActionStatus",
"description": "User has full administrative rights: view/edit dictionary and view/edit individual values."
}
When running
safe_data, all the user permissions associated with a dataset are included in the output RO-Crate; however, this should exclude users with the 'auditor' and 'administrator' roles, as these are excluded when runningsafe_people. This results in RO-Crates with orphan permissions, as the permission links to a valid dataset, but to a non-existent user entity (see below):The
NAuser represents an auditor account, for which no user entity exists in the RO-Crate. This should be fixed by removing the additional permission entity: