When batch importing atofms data from CSV files, if an error occurs, the user is notified that something was written to an error file, and the importation process stops.
At the very least, the user should be given more information about the error (either specifically where the file is, or information about the actual problematic files), and it may even be a good idea to not allow errors to short-circuit the implementation; that is, if a batch import is initiated, and a problematic file in the batch turns up, it should be skipped (the user should be informed of this of course) and the rest of the files in the batch should be imported.
We could alternatively give the user the option to continue with the import when an error is detected, because perhaps it is not useful to import the data at all unless all of it is there and intact.
Log in to post a comment.
