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
To avoid CSVs referencing data that isn't yet imported (say Teams from an institution before the institution), there should be a order in which we import CSVs. This should be well specified within the CSV-Importers repo.
The fields available in each CSV should be recognized, and all field names should be selectable (like for file names) to match our mapping. With a select, readable names can be used, and localized.
The text was updated successfully, but these errors were encountered:
To avoid CSVs referencing data that isn't yet imported (say Teams from an institution before the institution), there should be a order in which we import CSVs. This should be well specified within the CSV-Importers repo.
The fields available in each CSV should be recognized, and all field names should be selectable (like for file names) to match our mapping. With a select, readable names can be used, and localized.
The text was updated successfully, but these errors were encountered: