Dataset - File UI Improvements

[mheppler]

There have been many suggested features and reported bugs with relation to the display of files on the dataset pg. These mockups have been created for many new features, including facets and sorting to improve browsing.

The scope of this issue will cover all the new UI improvements needed for the dataset pg. Rather than tracking nearly a dozen other issues, they'll be closed in favor of this one.

Mockup

Consolidated Issues
- Better handling of dataset page with many files #2021
- Dataset Files: Selecting files in files tab is problematic can result in mistakes (delete, download, edit, etc). #2023
- Request Access for Files: Admin View Usability Issues #2285
- Use Solr for file listing on dataset page #2455
- Dataset Page: File Tab Sort Button #2506
- Dataset Page File Tab: Add Facets #2508
- Page printing: Messy printing of dataset #2584
- Dataset: Select > Edit Files > Delete, large number of files, page does not refresh #2591
- Files Tab: File count does not indicate how many files are currently displayed from total. #2681
- Dataset Files - DataTable LiveScroll w/ Duplicate Files #2699
- Dataset Files Table: Table Tries to Load More Files, When There Are No More #2701
- Add "View All" button for files on the dataset page #2705
- Files Tab: Tabular data tags are not sorted. #2808
- data files scrolling: users report Chrome not allowing to scroll past 25-50 files #2835
- File Page: Add Back to Top Option at Bottom of Page #2923
- sorting file by downloads: feature request by user from HKS #2947
- Request Access: According to mockups, there should be a request access popup. #2552
- Dataset Page: Download button for tabular file has dropdown but is cut off if near the bottom of the list of files #3835
- Dataset Page: Should lazy load thumbnails to better support slower storage media and improve page responsiveness. #4091
- Dataset Page HTML cleanup (W3 validator errors) #3750

These are related issues, which will remain open in order to track development of other projects which will impact this project.

Related Issues
- Dataset: File Hierarchy + Directory Structure #2249

• Initial ADA check: Primeface hidden checkboxes fail compatibility Initial ADA check: Primeface hidden checkboxes fail compatibility #2634
• Download Permissions: Remove business logic from Application fragments. Download Permissions: Remove business logic from Application fragments.  #2698
  - Edit File Metadata: Select All Files in Tab, Can't Edit Them All after clicking Edit Metadata Edit File Metadata: Select All Files in Tab, Can't Edit Them All after clicking Edit Metadata #2859
• UI Cleanup - Action Button + Metrics Block Layout UI Cleanup - Action Button + Metrics Block Layout #3341
  - Download button present for files in previous dataset versions when newest version is restricted Download button present for files in previous dataset versions when newest version is restricted #3576
  - Performance degradation investigation Performance degradation investigation #3631
  - File Download: Changing the list of selected files for a multipage file list results in bad download all behavior. File Download: Changing the list of selected files for a multipage file list results in bad download all behavior. #3711
• Improve visibility of buttons for data owners Improve visibility of buttons for data owners #3815
• UI to enable file tags to be searched UI to enable file tags to be searched #4122
• File Tags - Improve UI/UX and misc. bugs File Tags - Improve UI/UX and misc. bugs #6074
  - Dataset page: Page fails to load when it cannot understand an image file to generate thumbnail Dataset page: Page fails to load when it cannot understand an image file to generate thumbnail #4473
• Long (e.g. SHA-512) fixity checksums are too long for display Long (e.g. SHA-512) fixity checksums are too long for display #5210
• I'd like to be able to select and copy just the DOI from the citation block As a Dataverse user, I'd like to be able to select and copy just the DOI from the citation block #4994

[amberleahey]

Hi there, just wondering will file organization on the dataset landing pages be supported in a future release? We have had a few members interested in this for a while now as currently the pages get cluttered and disorganized quite easily when many files are uploaded. Some even contain hundreds of files and when this happens it is not easily accessible for people to get at or understand any structure. Thanks for considering this for a future release, btw really like the mockup!

[pdurbin]

@amberleahey do you have any sketches of how you'd like the file organization to look? Or maybe you can point us to a webapp that does this well.

[amberleahey]

the mock-up you have looks pretty nice for organization, but perhaps you could also add folder hierarchy or some structure to this? In some cases, we've had requests for this at the file level to support types of files, hierarchy of files, etc. It's difficult currently for files with more than 10 files, so anything will help! Thanks again maybe we will look into developing some mock-ups to support this development work.

[TaniaSchlatter]

@amberleahey Thanks for adding your comments. I agree that it makes sense to work the requests for file organization/hierarchy into these other file UI improvements that have been mocked up. We don't have a plan to address these in the next sprint, but continued requests for these refinements should help them get prioritized.

[TaniaSchlatter]

Note that the UI changes related to the citation block shown on this mock up are obsolete.

[pdurbin]

For some reason, I didn't receive the email

Huh, I finally got the email about six hours ago. Screenshot below. Sure enough, there's no way to tell who requested the file, just like @dconner3 said. That's not great.

@dconner3 do you feel like creating an issue for this? The fix should be relatively straightforward.

[dconner3]

Sorry for falling off this thread. Thank you for the additional information @pdurbin on how to see who the requester is through the web interface. @pdurbin, it looks like you added a screenshot to #2855. You don't need me to open an additional issue do you?

[pdurbin]

@dconner3 as long as you're fine with using #2855 to track the smaller chunk of providing a bit more information in the email, I'm fine with that.

The bigger feature is the whole "requestbook" concept in #2043. Please feel free to subscribe to both issues or create a new one if neither one quite captures what you want. Thanks!

[djbrooke]

Before we bring this to development, we need to

• Review Dataset Button options for scalability
  We decided on button options for user testing. Any further changes
• Is the checklist included here?
  Not in this round of testing. We should plan to support checklists, both of the sensitive data variety and for custom checklists developed for a specific installation.
• Review File list in File Table for scalability
  We are comfortable entering usability testing with what we have
• Determine Usability Testing strategy, scope, and plan
  We'll plan to test 5-10 people, with half being people familiar with dataverse and half not. @TaniaSchlatter will develop the user testing plan and @djbrooke and the team will help with recruitment and note taking. If needed, @djbrooke and perhaps @jggautier can run user tests as well.
• Recruit for Usability Testing
• Complete Usability Testing
• Analyze feedback
• Implement feedback from usability as part of coding effort, below
• Implement front end code and ensure accessibility (before sprint or in sprint)

[pdurbin]

This is a good issue to follow for updates:

• Dataset Page Redesign Dataset Page Redesign  #6605