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
Without a dataset being published on dataverse (not just uploaded as a draft), any file can be removed with the click of a button. It would make sense to configure any and all now siblings with untrusted.
If we happen to start supporting finalizing a dataset (un-draft it), we could then reconfigure the trust level.
However, any new upload and therefore re-drafting would bring us back to untrusted.
So maybe #101 is a better approach. If and only if a particular version is identified for data retrieval it would make sense to label it trusted. This would then likely happen on-clone.
The text was updated successfully, but these errors were encountered:
Without a dataset being published on dataverse (not just uploaded as a draft), any file can be removed with the click of a button. It would make sense to configure any and all now siblings with
untrusted
.If we happen to start supporting finalizing a dataset (un-draft it), we could then reconfigure the trust level.
However, any new upload and therefore re-drafting would bring us back to
untrusted
.So maybe #101 is a better approach. If and only if a particular version is identified for data retrieval it would make sense to label it
trusted
. This would then likely happen on-clone.The text was updated successfully, but these errors were encountered: