Export Core Data Project Data as CSV

[jamiefolsom]

As an admin user, I want the ability to export my project data into CSV format. Much like the export configuration functionality, this should be available under project settings in the "Import/Export" tab.

Notes:

• uuid values will remain intact
• project_model_id values will remain intact
• project_model_relationship_id values will remain intact
• user-defined field uuid values will remain intact

[dleadbetter]

@jamiefolsom - A couple if thoughts that could make a data export feature non-trivial to implement:

• Each record has a uuid value used to uniquely identify it. When we export data to be imported into another project/instance, we don't want to duplicate the uuid (defeating the purpose). We should regenerate these uuid values for both the records and the relationships (which will be the trickier part)
• Hard-coded into the CSV files we import into Core Data are the id values of the project_model and project_model_relationship records for each record in the CSV file. At the time of export, we will not know the id values of the records in the target project. We could either:
  • Export placeholders instead of the id values. This would require someone to replace the values with the ids from the target project. It seems a little error prone, but would not require re-working the data import process (see below).
  • Update the export process to export the project schema and data in one package and use uuid instead of id for project_model and project_model_relationship records. This would allow us to generate new uuid values at the time of export, and update the records to reference those new values.

Estimate: 45-60 hours

[jamiefolsom]

As discussed, we'll handle this via pg_dump for now -- moving a copy of all staging data into the UQAM instance for now, then removing unrelated data/projects from that copy.