v0.7.2

RELEASE NOTES

1. Added support for a new User Group / Dataset folder structure.
2. Fixed compatibility issue with the Django 1.11 MyTardis branch (which uses newer
   django-tastypie).
3. Instead of allowing multiple SCP failures, MyData now stops its uploads after one failure
    (if max retries has been exceeded for that upload), because we don't want MyData to
    quickly create a large number of empty DataFile records due to "Disk quota exceeded"
    errors.
4. Added the ability to ignore new datasets (via MyData.cfg not via the GUI yet), which is
    useful when scanning a very large collection when you want to prioritize archiving older
    datasets which may be ready for deletion from the machine MyData is running on.
5. Implemented a workaround for a difficult-to-reproduce counting problem where MyData
    sometimes miscounts the number of DataFile lookups it has performed.  The root cause
    of the counting problem is still unknown, but the workaround ensures that MyData's
    upload threads shut down cleanly, even if it over-counts the number of DataFile lookups.
6. Fixed Issue #129 - MyData changes permission of top-level staging directory to 660 when
    DataFileObject URI is None.
7. Implemented a workaround for the "scheduled time is in the past" issue.
8. Setting isOwner to False in facility manager group ACLs created by MyData, to reduce
    the clutter in the "Owned" section of MyTardis's "My Data" page.