Dataverse: Dataset - View Dataset Versions button does not appear on page load

[sekmiller]

One of the things we did to improve performance was to not load the versions onto the Versions Tab until the user actually went to the Versions tab. A side effect of that was that the View Dataset Versions button was not available on page load because its rendering is dependent on the presence of multiple versions, either published or one published and one draft if the logged in user has the permission to view drafts. In order to return the button we probably have to lose those performance gains since the View Versions button has a drop-down list of versions which has to be populated by processing all of the dataset's versions.

[eaquigley]

Additionally, the versions tab says, "no records found" until it starts loading (which takes about a second I believe) and can be concerning to a user who has a dataset with a lot of versions as it comes across as data is missing.

[mheppler]

pdurbin commented on Apr 26 on issue #3092

"No records found." To navigate to the draft you have to leave the dataset page.

[mheppler]

The issue with the Version table on a deaccessioned dataset reading "No records found" has been fixed in #1267.

[mheppler]

I am adding this to 4.6.1 to be included as part of the development with #3241, as recommended by the UX Team based upon user feedback in usability testing of 4.6.

[mheppler]

Adding these recommendations on the file pg to this issue.

• File version differences - tune the current display of information format to work for files
• When there are no tags on a file, we need an indicator that tags are a possibility. Show “No tags” in the tags area if there are no tags.
• Need a success message after restricting access to a file.

Recommended by the UX Team based upon user feedback in usability testing of 4.6.

[djbrooke]

We discussed this in the planning meeting this afternoon. We identified the following items:

• [ ] Provide the list of links as part of the page load
• [ ] Determine the design of these (dropdown, button, list, other?)
• [ ] Implement the links on the page

[landreev]

@mheppler , I created a branch - 2782-show-versions-on-dataset-page - and added code to provide a list of other versions available (that the user is allowed to see). And added the links to the page; as a simple list:

please modify as you see fit - put them in a pulldown menu and/or style the links pretty, etc.

[landreev]

@mheppler - per our conversation, changed the list to include the current version; rendered as text, not a link. All yours.

[mheppler]

Much appreciated, @landreev.

[mheppler]

Pushing through new UI.

[pdurbin]

@mheppler I'm running the code in pull request #3580 (I'm on 077bd73) and there are a couple consistency things I'm wondering about.

First, on the "Versions" tab we show 1.0 and 2.0 but in the new widget we show v1.0 and v2.0 with a "v". Should these be the same?

Second, when 1.0 has been deaccessioned, as in the example screenshot below, "1.0" is not clickable in the "Versions" tab but it is clickable in the new widget. It seems inconsistent.

[mheppler]

@pdurbin -- it was decided these design questions would be pushed until we discuss file-versions. The deaccession link I will work to fix now.

[pdurbin]

@sekmiller said he's code review this one. Assigning.

[mheppler]

Thanks, @pdurbin and @sekmiller.

[mheppler]

Merged the latest and greatest from develop. 7fec06f472b3e8fbb72a756a2b3fb6d2b5f4e88a

[kcondon]

This works fine but may need some Design attention for cases where there are many versions in a dataset.

[djbrooke]

@kcondon - can you link up an example of a case of many datasets? Thanks!

[kcondon]

doi:10.7910/DVN/VIE1H has 306 versions, the largest.

Version count stats:
datasets with versions >1: 8895
-hdl:1902.1/21576 3 versions
datasets with versions >5: 193
-hdl:1902.1/12117 7 versions
datasets with versions >10: 25
-hdl:1902.1/RKYSWXPPAC 13 versions
datasets with versions >15: 8
-doi:10.7910/DVN/28075 17 versions
datasets with versions >20: 5
-hdl:1902.1/21219 25 versions
datasets with versions > 25: 1
-doi:10.7910/DVN/VIE1H 306 versions

[djbrooke]

Pulling this out of the current sprint and out of 4.6.1. The complexity has increased, the value provided by this is minimal, and this even has the potential to provide a worse experience for datasets with many versions.

We will transition to work defined on the roadmap instead of continuing to work on this issue at this time.

[pdurbin]

I think what would help unblock this issue is to get a screenshot of what the version labels look like when there are 25 versions of a dataset.

[pdurbin]

At https://groups.google.com/d/msg/dataverse-community/bGlCU2pbQpE/vAKtSAjxAwAJ @philippconzett from UiT, The Arctic University of Norway, wrote,

Actually, there are some more features which would make the curator's job easier

1. Include the version number in the submitting message, i.e. when a dataset is submitted for review, the message to the curator should state whether this is an entirely new dataset, or a new version of an existing dataset.

This was in the context of #3943 and I summarized all of his feedback (and some from @stevenmce ) at https://groups.google.com/d/msg/dataverse-community/bGlCU2pbQpE/10oSARygAQAJ

Here's the bit I wrote about version numbers:

My second observation is that curators are potentially confused about whether they are being to asked to curate an entirely new dataset that has never been published (a combination of the labels "Unpublished" and "Draft" indicates this brand new, never been published status) versus a dataset that has already been published as 1.0 or whatever but now has a post-publication draft (the label "Draft" is present but the label "Unpublished" is absent). It's probably too subtle to expect people to think this hard about the presence or absence of the "Unpublished" label. For now, I hope this helps explain the existing labels. If this isn't documented in the User Guide please do open a GitHub issue. :) Anyway, your proposed solution is to show the version number to the curator because the curator knows that "1.1" means the dataset has already been published and that the author needs review of a post-publication draft. It's a good idea. There's a related GitHub issue at https://github.com/IQSS/dataverse/issues/2782 about bringing back a version indicator on the dataset page that was lost when we made some performance improvements and I think this would help a ton. This is probably out of scope for https://github.com/IQSS/dataverse/issues/3943 but I can at least look into adding the version number to the notifications that are sent.

It all feels on-topic enough to mention here.

[mheppler]

After discussing with @scolapasta and @djbrooke last week, it was decided to just to simply remove this button from the page.

[mheppler]

There was a commented out line in the User Guide referencing the button in the UI, which was also removed.