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
Researches of catalysis are using semicolon ";" as a separator within .csv files, what is not supported during ingest of tabular files, where only comma "," is currently supported (because of "Comma Separated Values"). Based on Wikipedia, a .csv files can have also a different separators, not only a comma.
Also we have to check, if "additional empty spaces" and "multiple-underscores" are interpreted properly, especially when all issues above are solved. With proper .csv with commas it is ok now, use test-file-spaces-underscores.csv as an example.
The text was updated successfully, but these errors were encountered:
vkush
added
external
This is an external issue (e.g. on Dataverse itself), we will not work on it but only monitor it
repo4cat
NFDI4Cat Central Data Repository
labels
Dec 5, 2024
German researchers with not much data background may create files with ; as separator (and , as decimal separator). But it should be avoided!
The ; is unfortunately created by Excel with German locale setting. I also saw problems with date and time formats in the past when German locale is used.
Instead of adapting to such problematic csv files I would prefer a validator that rejects or at least flags incompatible csv files. Do the BasCat validation tools maybe address this? @khatamirad
Researches of catalysis are using semicolon ";" as a separator within .csv files, what is not supported during ingest of tabular files, where only comma "," is currently supported (because of "Comma Separated Values"). Based on Wikipedia, a .csv files can have also a different separators, not only a comma.
Issues are known and under discussion:
The text was updated successfully, but these errors were encountered: