as an end user, I'd like to upload a non-tabular file with a "tabular" file extension

[donsizemore]

At the risk of duplicating #2199 but with a different use case:

Odum has a user who was unable to upload an Excel workbook since it wasn't tabular data and therefore failed ingest.

In #2199 @djbrooke responded: "I think we don't want to provide a feature to opt out of this, as ingest provides the data in multiple formats for easier data sharing and additionally provides a more preservation-friendly format. These are some of the core functionalities of the platform. There is an option to "uningest" via an API"

Our temporary solution was to have the user upload with a .txt file extension, but given the "reingest" API I think disallowing ingest may address end users facing ingest failures in general?

[valentinapasquale]

Hi! We also encountered a similar use case, in which the user wished to upload a CSV file containing a numeric square matrix (representing a signal intensity in region-of-interests over an image), and not tabular data.
In that case, ingestion failed (as the system tried to parse the first row to find column headers and did not find any), and authors were notified about the error.
However, we would like to have the possibility to disable ingest for data files/datasets that contain CSV files not representing tabular data (but just numeric matrices).
As a workaround, we could use TXT, but I do not think this is a correct choice.

[pdurbin]

In that case, ingestion failed (as the system tried to parse the first row to find column headers and did not find any), and authors were notified about the error.

In #7386 an Excel file didn't have a header and in the end the user added one.

[qqmyers]

I think this also ties to #8096 - if the warning about ingest failure isn't so dire, it's less important to stop it from happening and/or to be able to 'uningest' to fully remove the messages.

[pdurbin]

Related:

• Optional tabular ingest skipping  #8525