The constraints page layout is inconsistent across the Resource and Metadata sections. Could this please just appear blank and then the user can just select what they want.
Current State:
Preferred State (when the page is first opened, it would show this):
Preferred State (after selecting a constraint, it would appear like this):
The intention for these constraints is about granting permission. I would expect the default to show/default to "license" instead of "Copyright".
Ideally the application scope would be consistent with what it is describing. For example, for our purposes, I would expect the "Constraint Application Scope" for "Resource constraint" to default to "Dataset" and for "Metadata constraint" the same would default to "Metadata."
This is all about usage, so there's no need to include access.
The constraints page layout is inconsistent across the Resource and Metadata sections. Could this please just appear blank and then the user can just select what they want.
Current State:
Preferred State (when the page is first opened, it would show this):
Preferred State (after selecting a constraint, it would appear like this):
The intention for these constraints is about granting permission. I would expect the default to show/default to "license" instead of "Copyright".
Ideally the application scope would be consistent with what it is describing. For example, for our purposes, I would expect the "Constraint Application Scope" for "Resource constraint" to default to "Dataset" and for "Metadata constraint" the same would default to "Metadata."
This is all about usage, so there's no need to include access.