Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Model access conditions with DDI #3352

Open
AndyDaniel1 opened this issue Jun 28, 2024 · 0 comments
Open

Model access conditions with DDI #3352

AndyDaniel1 opened this issue Jun 28, 2024 · 0 comments

Comments

@AndyDaniel1
Copy link
Member

AndyDaniel1 commented Jun 28, 2024

@UteH came up with the idea of modeling the access conditions of our data packages with DDI (among other things, the purposes of use). This is a very good idea, as it would considerably exceed the information of the availability type field of the da|ra schema.

Maybe this should to be considered for all elements in the MDM as the access conditions vary for the elements of the data package (data sets, DMR, instruments etc).

EDIT: The conditions described below only apply to datasets, not to the data package as a whole. This is another strong argument for assigning a PID (doi or other) to the datasets and assigning them access conditions . EDIT2: Regardless of the assignment of pid to datasets, the access condition should in any case be implemented at the level of datasets. With this we can ignore the "subdatasets" as they in fact represent accessways and this would be covered by describing the access conditions for the object dataset.

Restrictions / AccessConditions:
grafik
grafik

CitationRequirement:
grafik

AccessPermission: Hint on the data use agreement

AccessRestrictionDate: #3216

https://ddialliance.github.io/ddimodel-web/DDI-L-3.3/composite-types/AccessType/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant