Feature Suggestion: Config Persistence

[alexdryden]

Issue:

The interface involves a lot of very detailed manual configuration that can be error prone, particularly with new users who are learning the system. When an error happens, they have to do all of the configuration all over again from scratch, which can be tiresome and can introduce new errors.

Solution:

I propose a feature where users can select a previous import to "use these import settings". This will help with error recovery because it will allow users to interrogate the interface and see where they may have gone wrong, and it will also make repeated attempts less tiresome.

Implementation Overview:

Because the module already reports out and stores an array with the configuration used, I suggest this array be used to auto-fill the upload form. If the number of columns or column names changes, it could produce an error message.

Other methods:

A complimentary, and possibly more useful, method would be to allow users to also upload a config file (e.g., a json with config parameters in the same shape as the config array reported by the module for past imports).

[flamsens]

I think this is an essential missing feature. Import configuration is often an iterative process. It would be nice to be able to start a new import based on a previous configuration.