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

View File Versions #3241

Closed
3 tasks
djbrooke opened this issue Aug 5, 2016 · 12 comments
Closed
3 tasks

View File Versions #3241

djbrooke opened this issue Aug 5, 2016 · 12 comments
Assignees

Comments

@djbrooke
Copy link
Contributor

djbrooke commented Aug 5, 2016

The user may view the previous versions of a file, if they exist

  • via UI
    • Includes the versions tab on the Dataset page and the written description of differences between versions.
  • via API
@djbrooke djbrooke added this to the 4.6 - File Replace milestone Aug 5, 2016
@djbrooke
Copy link
Contributor Author

djbrooke commented Sep 2, 2016

@mheppler - can you link up the mockups here so that we can review and move to ready? Thanks!

@mheppler
Copy link
Contributor

mheppler commented Sep 7, 2016

@mheppler
Copy link
Contributor

mheppler commented Sep 7, 2016

Related to/duplicate of: Files: Ability to Replace a File Instead of Deleting #2290

@djbrooke
Copy link
Contributor Author

@mheppler - sending this your way, as you were going to update some wireframes - thanks!

@mheppler
Copy link
Contributor

Discussion on some outstanding issues was made in this File Pg - UI Review Google doc.

Updated mockup.

mockup-file-versions

@mheppler
Copy link
Contributor

mheppler commented Nov 21, 2016

Outline of features associated with this issue.

Notes from QA on #2465 to follow up on in development of this File Versions issue.

File Pg

Dataset Pg

Dataverse Pg

  • Result cards file name link should point to file pg, not dataset pg

My Data

API

  • Add wrapper to access this information

User Guide

  • ...of course this feature needs some docs!

@mheppler
Copy link
Contributor

Briefly discussed in today's status meeting past performance issues with displaying dataset version numbers and links (#2782) in the UI and it was determined that we can and should be able to add these back as part of this development on the file versions feature.

I have added this as part of the outline in my comment above, under the Browsing section. Both @raprasad and @scolapasta would be excellent resources on how best to approach this.

@sekmiller
Copy link
Contributor

The version numbers on the file page version tab refer to the dataset version. Or do we need two columns of version numbers one referring to the dataset version and the second referring to the file version.

I can envision a situation where version 1 of the file would correspond with version 2 of the dataset.

@mheppler
Copy link
Contributor

@sekmiller -- there is only one version number we track/display, and that is the dataset version. There is no "file version" number.

@mheppler
Copy link
Contributor

mheppler commented Jan 3, 2017

  • Versions tab:
    • Column names on versions table need to be clear - change “Version” to “Dataset Version”. “Description” to… TBD.
    • Automatically generated messages must be specific to the file, not dataset specific.
  • File version differences - tune the current display of information format to work for files

Make sure to deliver items as recommended by the UX Team based upon user feedback in usability testing of 4.6.

@djbrooke
Copy link
Contributor Author

djbrooke commented Jan 4, 2017

We discussed this in the planning meeting on 1/4 and there are some questions. The team agreed that a good first step would be to have a design workshop to discuss the different views over some paper prototypes instead of just talking it out.

I'll work with @TaniaSchlatter to schedule this.

@scolapasta
Copy link
Contributor

Closing; broken out into two smaller issues.

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

4 participants