Data migration to populate new database columns for existing
VOEvents. We have to read the files in and try to extract the
parameter data, handling all of the changes to the file format
which have occurred over time.

I did a lot of testing by copying over the production database
and associated VOEvent files for all non-Test, non-MDC events
and superevents to make sure we are accounting for all changes
in VOEvent (file) schema that have happened over time.

We can change a few things about how the VOEvent file building
works now that all of the relevant parameters are stored in the
database.

There are several fields that the user provides to create a
VOEvent through the API, which are used in generating the VOEvent
file, but are not stored in the database. Let's fix this!!

GroupObjectPermission and data directory cleanup should only happen
*after* the event or superevent row is removed from the relevant
table.

There were problematic non-backwards compatible API changes from
2.3.0 to 2.3.1... nice, pyparsing.  Didn't catch this previously.

This was a known requirement, but got flubbed when a few changes
were made recently.

Duncan Macleod authored 5 years ago and Tanner Prestegard committed 5 years ago

the former is available for python3, the latter is not