You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most CSV files are identified as "text/csv". But we also accept "text/comma-separated-values" (as an ingestable format).
However, we only keep a "pretty", display type for "text/csv". (the mime display type properties bundle needs to be updated).
Also, we don't have a file extension mapping for this type. (this means if you download the original, or uningest, the filename extension "csv" will be lost).
Alternatively we can change "text/comma-separated-values" to "text/csv" when saving the original file info in the db.
The text was updated successfully, but these errors were encountered:
Updating this for @landreev, as text/comma-separated-values=Comma Separated Values was added to MimeTypeDisplay.properties in commit 5a19537 on May 2, 2019 as part of #2202, released in 4.15.
I think he's right. text/csv seem much more common than text/comma-separated-values (1 million vs. 35k hits on Google respectively). Plus the specs above and https://en.wikipedia.org/wiki/Comma-separated_values all seem to point to text/csv being the preferred type.
To focus on the most important features and bugs, we are closing issues created before 2020 (version 5.0) that are not new feature requests with the label 'Type: Feature'.
If you created this issue and you feel the team should revisit this decision, please reopen the issue and leave a comment.
This is a 1-2 issue.
Most CSV files are identified as "text/csv". But we also accept "text/comma-separated-values" (as an ingestable format).
However, we only keep a "pretty", display type for "text/csv". (the mime display type properties bundle needs to be updated).
Also, we don't have a file extension mapping for this type. (this means if you download the original, or uningest, the filename extension "csv" will be lost).
Alternatively we can change "text/comma-separated-values" to "text/csv" when saving the original file info in the db.
The text was updated successfully, but these errors were encountered: