-
Notifications
You must be signed in to change notification settings - Fork 488
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
More specificity about the meaning of "dataset" on delete #5517
Comments
From the tweet above, it's probably worth considering the rest of the feedback about multiple buttons. Here's a screenshot:
That said, this was estimated as a "1" last week when I wasn't here so I don't know what the plan is. |
The plan is to make the text change(s) only. @dlmurphy you said you would include some suggested text here? |
The Delete Dataset message looks great to me. For the Delete Draft Version message, I suggest just adding the words "most recently" to make it a little more clear: "Files will be reverted to the most recently published version." I'd also like to tackle the "Delete Dataverse" message that Mike pointed out. Let's rephrase to: "Are you sure you want to delete this dataverse and all of its datasets and files? You cannot undelete this dataverse." I'll make these changes to the bundle and pass this on to QA. |
@dlmurphy I don't think you can delete a dataverse if it has contents. This should be confirmed, but If I recall correctly you only see the delete dataverse option if your dataverse is empty. |
Whoops, good call! I'll check on this and make sure. |
Yup, @scolapasta is right. Dataverses can only be deleted if they're not yet published and they contain no draft datasets. I'll leave the existing Delete Dataverse message as is. |
Added "most recently" to help clarify which version the dataset will revert to when a draft is deleted.
"Dataset" can mean different things in different repositories. On delete, we should add some brief additional text to clarify what is about to be deleted. See:
https://twitter.com/KSchultz3580/status/1092851050971709440
The text was updated successfully, but these errors were encountered: