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
A lot of people use Excel to handle and store metadata. Whether rightly or wrongly, it is what it is. We will lower the bar for upload significantly if we can support Excel metadata uploads.
We would probably need to force people to set the dates into ISO still, unless Excel encodes whether dates are US format or not (which it well might) to avoid confusion of whether 04/07/2022 is 7 of April or 4 of July.
The text was updated successfully, but these errors were encountered:
Good point about the dates! I did the PoC now #3426 and looked into the docs of the library I used. It seems like excel internally stores date as an offset, the stuff seen in the UI is not actually stored in the file verbatim (source: SheetJS docs). The library seems to come with some date parsing support but I'm not sure which information you need to give it (i.e. which columns are dates?) -- would need to look into it more.
A technical note (already wrote here) - converting the file in the browser means we need to watch out for changes of the original file and then act on that (i.e. make the user re-submit the edited file).
A lot of people use Excel to handle and store metadata. Whether rightly or wrongly, it is what it is. We will lower the bar for upload significantly if we can support Excel metadata uploads.
We would probably need to force people to set the dates into ISO still, unless Excel encodes whether dates are US format or not (which it well might) to avoid confusion of whether
04/07/2022
is 7 of April or 4 of July.The text was updated successfully, but these errors were encountered: