Dataset Tabular File Ingest - Displaying both "success" and "ingest in process" message is confusing/wrong

[sbarbosadataverse]

There should maybe be no "success" message until the files completes ingest

[pdurbin]

@oscardssmith have you noticed this while working on #3767?

[mheppler]

Closed the issue Tabular File Ingest: No message indicating page will refresh on its own, or if user needs to manually refresh #1798 as a duplicate of this issue.

Recently saw this issue in my localhost develop branch, build d317d23, and agree that is confusing and should be clearer in the UI what the process will be for the end user.

The "Ingest in progess..." message will automatically be removed from the page, but the disabled state for the Publish, Edit and Upload buttons remains. In addition to the buttons, there is other functionality on the page that is broken when the page doesn't refresh properly, including the Explore button being added to the file table row, as well as the "Upload Completed with Errors" hover popover linked to the warning icon not working, as reported in issue #3491.

Recently, we have developed "workflows" for publish, that use the warning message block to inform the user about the dataset lock status. We should apply similar messaging to the file ingest workflow, explaining why those buttons are disable and for how long. We should also fix the page refresh to properly update everything on the page.

[djbrooke]

• Improve messaging on the page (top of page and on ingesting files, possible lock messaging). The files are there and available for download, but the ingest process is not yet complete. Expectations setting is important.
• Verify that the auto-page refresh is working as expected (work with @sbarbosadataverse on this one).

[TaniaSchlatter]

Issues #3491 and #3794 are also page-refresh related, and might be able to be addressed with this issue.

[kcondon]

@mheppler @sekmiller Issues found, testing with Chrome:
-The explore button still needs a manual refresh to appear, at least when a configure button is also configured. Happens with 50by1000 .dta and collier-1740.csv but not some very small .csv files. #3491 is not only about upload with errors but displaying explore on ingest.
-Getting weird upload failures for some larger files, eg. feaironlaitin.dta
Upload unsuccessful (400: Bad Request). (2MB): other failures say network error for 3MB zip files. Would someone try there against dataverse-internal?
Retested on dvn-build, works. This appears to be a server issue.
-Sometimes the configure/explore buttons appear immediately, while ingest is in progress. Noticed during multiple upload/delete/upload.

[mheppler]

Coordinated with @kcondon to try and replicate some of the issues he saw. Here is what I confirmed locally in the 2709-ingest-warning-messaging branch.

• fearonLaitainData.dta uploaded and ingested with no trouble, expect when the page refreshed when ingest completed, there was no success msg or Explore btn displayed -- the Explore btn appears if you manually refresh
• 50by1000.dta had a completely different successful ingest... the Explore btn appears while "ingest in progress..." and "Dataset Lock" warning msg are displayed... the page never refreshes, no blue spinner checking on the ingest status... and you have manually refresh the page to remove the "ingest in progress..." msg and unlock the edit + upload btns... again, no success msg

Screenshot of the empty Dataset Lock warning msg, as well as Explore btn displaying before ingest completes.

[sekmiller]

The fix I put in to display the explore button when ingest completes wipes out the success message (you see it for a moment and then it goes away.) This is because the explore button is rendered based on the fileDownloadhelper which is injected into the DatasetPage bean. In order to refresh the "helper" you have to reload the whole page. I'll see if there's a tricky way to repost the success message after reloading the page.

[sekmiller]

I fixed the ingest success message so that it will appear after the page reloads any explore buttons.

I haven't seen an empty locked message. Are there any tricky steps needed to recreate?

[mheppler]

@sekmiller -- that could be due to a local dev setup error on my part, by not copying over the new bundle in this branch over to my local properties files directory that I configured for internationalization.