Feature: Allow a user to save a mapping for csv import + UserPreference model class idea

[whatisgalen]

The main UX issue this would address is: you're a frontend user, you know your mapping for your csv, but you have to re-enter it manually each time you import a csv. It would be better to save a mapping and be able to select it again in the future, returning some kind of warning if any column saved in the mapping isn't present in the current csv.

There's a larger question regarding user architecture here; specifically, if a user can create a mapping, perhaps they should be able to share it on the local Arches instance. This means that instead of saving this property to the user profile (easiest solution), it might make more sense to spin it out as an instance of, say, a UserPreference model class. That way different things could also be saved along with their relevant context, e.g. map preferences, other etl module preferences, notification preferences, translation preferences, etc.