Feature Request: Better handling of file selection on dataset page

[qqmyers]

In the context of #10451 and #10336, we discussed how complex the code has become for handling cases where the user selects some set of files from the dataset page file table and then selects an action (Download, Restrict, etc.) where not all of the files are eligible. It would be great if some way to simplify the logic and/or improve the clarity of messaging could be done in the SPA.

In the case of Download, a given file may not be accessible for download because 1) it is restricted and the user has not been granted access, 2) it is embargoed, 3) it has a retention period that has expired, 4) it exists on a Globus endpoint that does not support HTTP(S) download, or a combination of these. There is also a case where all of the files are accessible, but the zip size limit is such that not all files will be included in the zip. For Restrict, it is simpler - restricted files can't be restricted a second time.

In the current UI, we put up a warning dialog that indicates some files are ineligible and this warning is specific to the action, has historically indicated which condition(s) prohibit the file action on some/all files, and lists the affected files. We also change the wording/dialog content to indicate whether all/some/non of the files are a problem. (The zip limit case is handled by adding a note in the zip that some files were excluded.) With Download having so many possible cases, we're moving to a strategy of just saying "Inaccessible Files Selected" as the title and including a description that lists all possible reasons that might be the case. The list of files does not indicate which condition(s) affect an individual file.

In the discussion we considered options such as having one static dialog to indicate that ineligible files were selected and using highlighting in the table to indicate which files had which problem, or perhaps flipping the logic to have users select an action first and then only allowing eligible files to be selected. There could be other options. This issue is a placeholder to flag that we might want to consider such options before re-implementing the current less-than-ideal and complex UI.