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

Support special remote trust level setting #179

Open
mih opened this issue Feb 28, 2023 · 1 comment
Open

Support special remote trust level setting #179

mih opened this issue Feb 28, 2023 · 1 comment
Milestone

Comments

@mih
Copy link
Member

mih commented Feb 28, 2023

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.

@adswa
Copy link
Member

adswa commented Mar 16, 2023

So that would mean setting the local config remote.<name>.annex-trustlevel to untrusted, even outside of export mode?

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

No branches or pull requests

2 participants