Update pager to include +- 5 pages
Species is no longer a required field
Split each verification step into subjobs

It seems like the way django works it doesn't always release memory when
you might expect it to. By limiting the job size it keeps the memory
footprint small while also allowing multiple upload threads to be used.
Fix a race condition with celery

The celery worker would sometimes kick off before the ImportEvent had
been saved. When it was saved it would result in a duplicate key
error. To solve this we manually commit the transaction before calling
any celery tasks.
Fixed the 'Sign Up' URL.
Add status field
Add in better list view
Execute blocks of verification/commits

Instead of committing everything at the same time, work on blocks
"BLOCK_SIZE".

This should make it easier to run parallel updates
Update tests
Merge pull request #114 from ahinz/topic/more-importer

Topic/more importer
Support for additional species fields

In particular, a "family" field and a "other_part_of_name" field.

The other_part field contains any sort of text that the users want and
are used by the uploader to match species accordingly. For instance, if
someone wants to use a varietal or a sub-species this is the correct
place for it.
Use unicode escapes when processing species
Initial species error handling
"More Options" dialog for species fixing
Merge pull request #113 from shantanoo/patch-1

Fixed the 'Sign Up' URL.
Merge pull request #115 from ahinz/topic/species-fields

Support for additional species fields
Add new app for woodland polygons

This is the start of a feature that will allow users to specify the
number, species and dbh of trees in a given area
Merge pull request #116 from ahinz/topic/polygon-fields

Add new app for woodland polygons
Fix Ban/Activate links that contain duplicate DOM ids

This bug was reported as occurring when the the ban/activate links are
clicked after sorting or filtering:

""" On the users page (http://treezilla.org/users/), administrators
can use the ban? button to the far right of a user name to ban the
person from logging into OTM. If you click the ban button, it becomes
an activate button. If you click the activate button, it makes the
person's inactive account (meaning they never clicked the activation
link in the email) become active.

The problem is that the ban/activate button isn't working if you do
any type of sorting or filtering. It will work on the first page of
user results but any action to change the search results (clicking on
a column header), changing pages, etc makes the button no longer work.
"""

However, it looks like the problem was actually that for some, but not
all users, the DOM element that their data and links lived inside of
contained IDs that also occurred in the species list. jQuery selection
was not working because this was causing invalid HTML. This problem is
fixed by changing the user DOM element to have a class and a data-id
instead of an id attribute.
Fix Ban/Activate displayed option for user edits

The problem was that for users who were labeled "Inactive", a "Ban?"
link was displaying, even though it should have said "Activate?" -
banning is only a valid option for users that are labeled
"Active". The admin was required to first click "Ban?", which would
save the user object without changing it, then click "Activate?" to
produce the desired result.

This is fixed by changing how the initial html template is rendered.