as an end user, I'd like to upload a non-tabular file with a "tabular" file extension
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with this issue's relationship to #2199 and the reingest or uningest API behavior described in the report. Trace how uploads with tabular file extensions are handled when their contents are non-tabular, then clarify and test the intended behavior for Excel workbooks and similar ingest failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100