You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
We have identified an issue with the default setting for access rights when they are sourced from Fairdatapoint. Currently, the system automatically assigns a default access status of "This resource has no access restriction" to data, implying that it is publicly accessible. This behavior occurs regardless of the actual intended restrictions for the data.
Expected Behavior:
The expected behavior is that there should be no default access restriction set automatically. Access rights should explicitly reflect the settings configured in Fairdatapoint without assuming a default public status. For example by using a NULL Flavour
Relevant log output
For example https://catalog-test.healthdata.nl/datasets/da1934bc-a45f-4864-baec-4c65641eb9db
Access right has url: https://staging-fdp.gdi.nbis.se/dataset/87495812-3201-4099-9478-1c60c9ef8c85#accessRights
The text was updated successfully, but these errors were encountered:
hcvdwerf
changed the title
Bug appears
Access Rights default is public. Most data is not public
Apr 25, 2024
What components are related to the issue?
No response
Which FDP are you using?
FDP managed by someone else
Version
What happened?
Description:
We have identified an issue with the default setting for access rights when they are sourced from Fairdatapoint. Currently, the system automatically assigns a default access status of "This resource has no access restriction" to data, implying that it is publicly accessible. This behavior occurs regardless of the actual intended restrictions for the data.
Expected Behavior:
The expected behavior is that there should be no default access restriction set automatically. Access rights should explicitly reflect the settings configured in Fairdatapoint without assuming a default public status. For example by using a NULL Flavour
Relevant log output
The text was updated successfully, but these errors were encountered: