A list of superevents which need operator signoff will appear
on the home page if the user signs in from an IFO control room.

Adding some optimization in search forms by using select_related
and prefetch_related.  Some of this is on the Superevent model
within the get_internal_events and get_external_events methods.

Show group, pipeline, search by default for event searches,
hide link to files.

New /latest/ page includes events and superevents. We also
move the old events 'latest' page to /events/latest/, changed the
view name, and fixed reverses to that page appropriately.

Adding view functions, templates, and full nasty javascript
to get a more complete and (hopefully) temporary implementation
of the superevent detail view ready. This includes buttons for
allowing/removing LV-EM access and forms for signoffs.

Using new create_versioned_file utility in create_log functions,
adding ability to provide queryset to get_superevent_by_date_id_or_404,
changing a few comments for autogenerated log messages

Added some utilities for handling signoffs for superevents,
including alerts, labels, logs, etc.

Small update to methods which build VOEvent files for events
to match superevents and play nicely with changes to
gracedb-client.

Adding API resource for creating and getting VOEvents from superevents.

New CommaSeparatedOrListField type which accepts a comma-separated
string (and splits it into a list) or a list input.  Useful for
handling input from the web interface as well as from the Python
client in either form.

Changing \d+ to \d{6} in superevent date ID regex.  This prevents
ValueErrors from occurring when people try to go to URLs like
/superevents/view/S0001.

Adding ability to create_emobservation to handle comma-separated
strings as input rather than lists, which is necessary for handling
input from the web form on the event pages.

Updating create_emobservation to work for new
gracedb-client method of uploading emobservation
parameters.

Adding EMObservation creation and alerts for superevents.
Note that this required a change to gracedb-client.

Allow EMObservation fields ra, dec, raWidth, and decWidth to be
blank in forms, resulting in a null database entry.

Modified events.view_utils.reverse to return an absolute url using
core.urls.build_absolute_uri.  This is helpful for when we issue
alerts without a request object available to construct the absolute
url.  Also updated the corresponding *toDict methods so as to
take advantage of this.

Changing from ISO format to another more readable format for
serialization functions in events/view_utils.py.  Changes for
things like EMObservations, EventLogs, etc.

Added a namespace to include() of superevents part of API. This fixes
an issue where reverse('api-root') was NOT returning the root of the
API but was rather returning /api/superevents/.

We currently aren't filtering superevents for the user in the
request for the web interface search, so we are removing the
(very minor) filtering in the API for the time being.  In the near
future, we will add the full permissions framework in.

We added exception handling for certain create/destroy methods which
involve multiple object creation (log messages and/or tags) and which
may commonly raise errors, like tag creation with invalid characters.
This was done within the superevent viewsets and in the events api.

Adding an optional "purge" for superevent deletion which removes
GroupObjectPermissions and deletes the data.

Adding try/except blocks to destroy views to handle errors in
perform_destroy

If a tag's name has some "uncommon" characters in it, like
parentheses (or probably others), it will cause errors for the
javascript which renders the event pages, since it tries to use
the tag name in the element id for the delete button.  We now require
that tags only use 0-9a-zA-Z_\- in their names. May have to go through
and delete some tags which use them.

First pass at implementing alerts for superevent creation,
update, annotation, labeling, etc.

Prevent users from removing a superevent's preferred event.
They will have to update the superevent to set a new preferred
event instead, then remove the event.

Changes to the eventlog API caused issues for calls to that resource
from within the javascript which populates the event log on the web
view for an event, since the issuer is no longer a dict containing
'username' and 'display_name' keys, but rather just a string
corresponding to the username.