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

Not obvious how we were getting this installed previously,
but we have to fix the version. 2.4.0 was being installed in some
instances which was causing parts of the search to break.

A search for S190404 or GW190412 Now returns the first superevent from
that date which matches the other requirements based on the date ID
string.  Should make the user interface a little nice.

A web view has been created which allows EM advocates to disable
or enable pipeline submissions. This is to prevent misbehaving
pipelines from submitting bad information. The mechanism works by
preventing events from being submitted to a given pipeline, not
by revoking certificates or removing user account permissions.

Create a group for the RAVEN pipeline, add users, and give the group
specific permissions. Right now, they are just allowed to populate
the Fermi, SNEWS, and Swift pipelines for uploading external events.