'EM_Superseded ' -> 'EM_Superseded'. This has been fixed manually on
all servers.  Note that it wasn't a problem on the production
server because that migration was "reworked" within the last year
and was not actually applied in production (it was 'faked').

New mixin for doing some kind of validation on the request data
or the instance before destroying it.

Want to see what is triggering this functionality, if it is
being triggered at all.

Fixing a bug in superevent queries by creation time:
using Combine on the expression resulted in incorrect args
being passed to construct a datetime object.

* Consolidated *all* of the search stuff into the search app
  (previously the flexigrid stuff was in events/superevents)
* Completely removed the old events-only search and latest views,
  templates, etc.
* Removed some old unit tests which tested the events-only search

Prevent the function for generating search results for the flexigrid
table from being accessed except by AJAX. This prevents users from
overriding the expected parameters and generating server errors.

Instruments should be read from the coinc_inspiral table,
not the coinc_event table.  Fix this for all CBC pipelines and
for Omega, too.

Remove handling for .gwf event files for MBTA submissions.
Comments indicate that this was deprecated in 2014 and could be
removed in 2015.

Add ordering for nested views for a superevent: events, voevents,
and EMObservations.

Create generalized methods for nested viewsets. There is now a
default get_queryset method which finds the nested model queryset
through the parent object; the user can specify filtering parameters
as well.  We also added a order_by filter for list views; parameters
can be specified on the class.

Use text input for event graceid in web browsable API form for
adding an event to a superevent.

silk was slowing things quite a bit so we won't use it by default,
even in development instances.

The serializers for logs and emobservations (for both events and
superevents) now give the user's full name for web views (unless
it's blank; then fallback to username) and the username otherwise.
We check for web view 'status' by seeing whether it is an AJAX
request. This matches the previous behavior before the development
of the superevents features.

Rename config/settings/test.py -> config/settings/dev.py to prevent
the file from being picked up by the test runner during unit testing.

Use DelimitedOrListField for tag names and tag display names
in the web API form for superevent log creation.

CommaSeparatedOrListField is now called DelimitedOrListField.
Default delimiter is ',', but the user can specify anything.
Some improvements to not show [] in web forms by default and
properly handle empty inputs.

Changing superevents serializer to use text input fields for
'preferred_event' and 'events'.  The 'events' field also will now
accept a comma-separated list.  This prevents timeout errors when
trying to render all the options for events in the form and speeds
up page load times significantly for this view.

Fixed case where external user creates a log message with no
tags so that add_tag permission is not incorrectly required.

Switch over to new phone alert code (somewhat improved compared
to the old code).  Made a few more updates and bugfixes.

Removing old alert code in alerts.old_alert.  Finished migration
to new code by updating the phone stuff.

More informative error message when posting a log message from
the superevent detail web page.

We normally require permissions to add tags to log messages or to
create logs with tags attached, but we want to apply the
'analyst_comments' tag to log messages posted from the web form
no matter what, so we add a check where that doesn't require
special permission if the request is AJAX.

Fix "parent" object serialization for event alerts where the
"object" is also an event.  Now provide the subclass for
serialization rather than the base class.

Now require version 2.0.0 of the client and won't allow old
versions without the client header.

New unit tests which check what information is shown to different
user classes on the 'search' and 'latest' pages.