Feature #6416
Do not allow restrictive access control change to content with a DOI
Start date:
Due date:
% Done:
0%
Estimated time:
Bugzilla-Id:
History
#1 Updated by ben leinfelder over 6 years ago
- Assignee set to ben leinfelder
- Status changed from New to In Progress
Thinking about this more, we have only CN.setAccessPolicy() in the DataONE API. So any change in the access policy would be network-wide. Do we really want to prevent changing access to be non-public if the object has a DOI and enforce this rule for all of DataONE?
We could restrict the old Metacat API to fail when setting access on a docid that maps to a DOI, but that will be a small fraction of our API calls going forward since it is deprecated.
Thoughts?
#2 Updated by ben leinfelder about 5 years ago
- Target version changed from 2.5.0 to 2.5.1
#3 Updated by ben leinfelder about 5 years ago
- Target version changed from 2.5.1 to 2.x.y
#4 Updated by ben leinfelder about 5 years ago
- Target version changed from 2.x.y to 2.6.0
#5 Updated by ben leinfelder almost 5 years ago
- Target version changed from 2.6.0 to 2.x.y