-
Notifications
You must be signed in to change notification settings - Fork 7
Description
Is there an existing issue for this?
- I have searched the existing issues
Description
This is a follow up to #173.
The extra_gated_fields field is poorly documented and it has implications for whether or not we can include the dataset in our catalog.
My understanding is that this field is used to prevent access to a dataset and its metadata unless and until a terms of use form has been signed by the user. On the face of it, this means the dataset is not truly "open" in our usual sense and therefore should be excluded, by default.
However, there is a grey area where a dataset is mostly free to use, but the creator of it wants to prevent some uses (e.g., commercial purposes) or ensure the user is aware of limitations.
Therefore, we should decide how to handle these cases, whether or not we think they should be excluded (the easiest thing to do) or included in some way.
Affected Areas
- Documentation files (docs/)
- Website content (website/)
Proposed Changes
- Decide if any restrictions are acceptable.
- If they are, decide which possible restrictions are acceptable.
- Determine how to represent those datasets in our catalog.
Additional Context
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status