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
The import process was designed to ignore columns that are not named in the config. This allows us to ignore data that isn't relevant.
However, since the importer is only looking for specific names (e.g. "Kingdom" and not "kingdom"), this can cause the taxonomy to be incomplete (see #99) yet the import still appears successful.
This issue should be improved. The columns may need to be case-insensitive, or perhaps display a warning if all of the taxonomy represented by the config file is not found.
The text was updated successfully, but these errors were encountered:
There are also issues where traits don't get imported and no warning is displayed. For example, Begonia.csv has a column for 'Sexual System (hermaphrodite,monoecy,dioecy,...)'. 'Sexual System' is listed in the import config but doesn't get imported.
Perhaps a simple warning step: These columns will not be imported
The import process was designed to ignore columns that are not named in the config. This allows us to ignore data that isn't relevant.
However, since the importer is only looking for specific names (e.g. "Kingdom" and not "kingdom"), this can cause the taxonomy to be incomplete (see #99) yet the import still appears successful.
This issue should be improved. The columns may need to be case-insensitive, or perhaps display a warning if all of the taxonomy represented by the config file is not found.
The text was updated successfully, but these errors were encountered: