Include tabular ingest failure reason in tooltip on dataset page file table

[jggautier]

What steps does it take to reproduce the issue?

• When does this issue occur?

  When reviewing the tabular ingest failure messages in the tooltips on a dataset's file table and in the tooltips on the file's pages.

• Which page(s) does it occurs on?

  The dataset page and the file page

• What happens?

  On the dataset page's file table, there's a tooltip with more information about tabular files that could not be ingested:
  

  As far as I can tell, that message always reads that "No further information is available," regardless of the dataset or file.

  But on the file's page, the tooltip might have more information:

  

  I was able to reproduce this on Demo Dataverse, and here are more datasets in Harvard's repository where you can see this:

  • https://doi.org/10.7910/DVN/SEGOVA
  • https://doi.org/10.7910/DVN/XT15Y0
  • https://doi.org/10.7910/DVN/QBRISH
  • https://doi.org/10.7910/DVN/LQW3CT

• To whom does it occur (all users, curators, superusers)?
  Curators, superusers, depositors (anyone who can edit a dataset with one or more tabular files that could not be ingested)

• What did you expect to happen?
  The details about why the ingest failed are also in the tooltips in the dataset file table. Otherwise, users who see the tooltip on the file table might think that the repository has no more information about why the ingest failed.

Which version of Dataverse are you using?
v5.13

[luddaniel]

Although I couldn't find the explanation via a commit in versions higher than v5.13; I was not able to reproduce on v5.14 and v6.2. Both tooltip are displaying the same message containing the ingest report error message.
This file was used for tests : https://dataverse.harvard.edu/file.xhtml?fileId=6525049&version=2.0


@jggautier Can you test and close the issue ?

[jggautier]

Hmm yeah I can't reproduce it either for any of the files I mentioned in this issue's original post.

Do you think the PR for the issue at #9570 fixed this? Or did you rule that out too when you looked through commits in versions higher than v5.13?

@stevenferey, you wrote that this GitHub issue was related to the one you opened at #9570? Did your PR resolve this issue with the tooltips?

[luddaniel]

@jggautier I mean : I checked the code, git blamed, checked 5.14 milestone I didn't find the bug fix. But it works so no need to overthink ^^

[jggautier]

Thanks yeah. I don't mean to overthink it. I guess generally I'm worried when things change and no one knows why.

Do you think it's not worth waiting to hear from @stevenferey?

Maybe that's the nature of software development or specifically development in open source software?

[luddaniel]

@stevenferey is in my team, his code didn't change anything related to this issue.
If you didn't had fork of v5.13 my best guess is this : there is a lot of JSF tag that can update datasetForm:filesTable; maybe the dynamic reloading was done somehow before ingest error was registered in database resulting in the display of default Bundle key file.ingestFailed=Ingest failed. No further information is available. instead of the actual real error. In this case, reloading the page would fix it...

Maybe that's the nature of software development or specifically development in open source software?

Most of my developper carrear I was able to find a code explanation really fast. But some times you need 3 days because it's a really complicated context. For this issue, as it seems fixed, I'll suggest to just move on :)