Generify /save params

[ghost]

When using the /save endpoint, several fields that are "required" reflect the old paradigm, eg type_id. We should update the params to be more generic. We should think about what values make sense in a generic context, eg do type_id, missing_code and capture_date makes sense? (Note, the answer may be yes!) This will also likely result in a database schema migration as these same params are also saved (maybe unnecessarily) in the database.