UI IMPACT

As defined in the following mockup document.

Dataverse

• Render logic to hide Metrics block
• Render logic to hide Guestbook link in Edit dropdown

Dataset (view/no files)

• Render logic to hide Metrics block
• Render logic to hide Guestbook panel in Terms tab

Dataset (view/has file/success-upload)

• Render logic to hide Download count
• Render logic to hide Download button
• Help text with link to User Guide (/user/dataset-management.html#file-handling-and-uploading)
• Display (in place of Download button) "Local Access" path, "Download Access" rsync commands for various locations (with location name country in parentheses), "Verify Data" command
• Dynamic path for Local Access
• Dynamic paths for Download Access
• Dynamic command for Verify Data
• Tooltips for "Local Access", "Download Access", "Verify Data" labels
• Style code snippets as "black text, grey background" (already delivered in File Upload w/ Rsync UI/Workflow changes #3348)

Edit Dataset Terms

• Render logic to hide Guestbook panel

File

• Render logic to hide Metrics block
• Render logic to hide Download count
• Render logic to hide Download button
• New "Data Access" tab, displayed first, with help msg and labels/values to display "Local Access" path, "Download Access" rsync commands for various locations (with location name country in parentheses), "Verify Data" command
• Dynamic path for Local Access
• Dynamic paths for Download Access
• Dynamic command for Verify Data
• Help text with link to User Guide (/user/dataset-management.html#file-handling-and-uploading)
• Tooltips for "Local Access", "Download Access", "Verify Data" labels
• Style code snippets as "black text, grey background" (already delivered in File Upload w/ Rsync UI/Workflow changes #3348)

User Guide

• Rsync Download > File Handling + Uploading > Dataset + File Management

From another round of testing:

• hide "guestbook" block under terms tab; since "package files" and guestbooks are not intended to work together.

Wrote some new messaging for the rsync download pages, would love to get @pameyer's verification that everything is accurate. Here are some earlier mockups, followed by the revised instructional text.

Data Access tab at the bottom of the file page:

There will be gray help text at the top, and tooltips on each of the three blue headers.

Gray instructions at top: "This data can be accessed through your computer's Terminal using the commands below. For more information, see our User Guide." ("User Guide" links to a guide page with more info)

Local Access tooltip: "If this data is locally available, this is its file path."

Download Access tooltip: "Download this data by running this command from your preferred mirror."

Verify Data tooltip: "This command runs a checksum to verify the integrity of the data you've downloaded."

File table at the bottom of the dataset page:

This page will use the exact same help text as the other page. As discussed with @mheppler and @TaniaSchlatter, the gray general instructions should go on the right side of the file table, above "Local Access". The three headers will have the same tooltips as the headers on the file page.

Text styling

All red-on-pink text should be changed to highlighted black text, as in this earlier mockup:

@dlmurphy looks good to me

One update - these UI changes should be conditional on the downloadMethods setting that was previously added (for this purpose).

It doesn't say so in the checklist explicitly, but, there is no "Download" button on the page for a package file, correct? (just to confirm). I.e., that "Data Access" text on the dataset page, in the mockup above, replaces the current Download button - correct?

If so, the checklist really should say "render logic to hide download count AND download button"...

It sounds so far like this issue is mostly about changing the rendering of the dataset and other pages for "package" files.
So then, in order to work on it, you just need a file with the "package" mime type. One way of creating such a file - aside from actually running a successful DCM upload - would be to pick a dataset with a single file; find the file in the DataFile Postgres table; and change the ContentType field to application/vnd.dataverse.file-package.

(and, it sounds like, you don't need this Datafile to contain an actual physical package directory on the filesystem; at least not for the purposes of working on the page...)

@landreev - you are correct; there shouldn't be a "Download" button

I may have been able to fix that annoying "CSS blink after the page auto-refreshes" issue. (the "blink" itself was a Chrome-only issue; but the auto-refresh was also causing the files table to be resized incorrectly, and that was affecting all (or most) browsers. I've updated the checklist entry).

It was all caused by the "update=@ALL" in the autorefresh block. It's just that for whatever reason I couldn't get it to properly refresh all the affected page parts without resorting to "all", back when I was working on it for tabular ingest. (so, this was not anything introduced in these rsync branches; we've had this issue forever).

But, as I said, I think I got it to work, by updating just the affected components (the files table; the citation; the edit/publish/etc. buttons; and the message panel). But please re-test carefully. And see if I missed anything.

Wait, my commit with the message fix didn't seem to go through. Trying again.

@kcondon I've added a similar success message to file delete on the single file page as well.