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

More specificity about the meaning of "dataset" on delete #5517

Closed
djbrooke opened this issue Feb 6, 2019 · 9 comments
Closed

More specificity about the meaning of "dataset" on delete #5517

djbrooke opened this issue Feb 6, 2019 · 9 comments
Assignees

Comments

@djbrooke
Copy link
Contributor

djbrooke commented Feb 6, 2019

"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

screen shot 2019-02-05 at 7 37 34 pm

@mheppler
Copy link
Contributor

mheppler commented Feb 6, 2019

"Delete Draft Version" confirmation msg'n should also be considered here.

screen shot 2019-02-06 at 12 08 26 pm

@mheppler
Copy link
Contributor

mheppler commented Feb 6, 2019

And while we're piling on... "Delete Dataverse" confirmation msg'n follows the same format of vagueness.

screen shot 2019-02-06 at 12 10 01 pm

@pdurbin
Copy link
Member

pdurbin commented Feb 12, 2019

From the tweet above, it's probably worth considering the rest of the feedback about multiple buttons. Here's a screenshot:

screen shot 2019-02-12 at 11 03 58 am

  • "PSA: the term dataset can either refer to a single data file or to a collection of data files and associated code. So when Dataverse asks if you really want to delete the selected dataset, make sure you know which meaning it is using."
  • "PS. In retrospect what messed me up is that when you select a file, there are two edit buttons, one which will let you delete the file, the other (higher up) that will delete the entire dataset. I didn’t see the former until it was too late."

That said, this was estimated as a "1" last week when I wasn't here so I don't know what the plan is.

@djbrooke
Copy link
Contributor Author

The plan is to make the text change(s) only.

@dlmurphy you said you would include some suggested text here?

@pdurbin
Copy link
Member

pdurbin commented Feb 13, 2019

I just created pull request #5536 with some tweaks to the wording. Here are some screenshots:

screen shot 2019-02-13 at 3 27 45 pm

screen shot 2019-02-13 at 3 28 01 pm

I'm reminded that we never did create a glossary (#4274) of terms and "dataset" should definitely be in there since as the tweet points out, to many people it can mean a single file.

@dlmurphy
Copy link
Contributor

dlmurphy commented Feb 13, 2019

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.

@scolapasta
Copy link
Contributor

scolapasta commented Feb 13, 2019

@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.

@dlmurphy
Copy link
Contributor

Whoops, good call! I'll check on this and make sure.

@dlmurphy
Copy link
Contributor

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.

dlmurphy added a commit that referenced this issue Feb 13, 2019
Added "most recently" to help clarify which version the dataset will revert to when a draft is deleted.
@dlmurphy dlmurphy removed their assignment Feb 13, 2019
@kcondon kcondon self-assigned this Feb 14, 2019
@kcondon kcondon closed this as completed Feb 14, 2019
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

6 participants