Release 3.7.0
Released: January 2829, 2016
The DuraCloud 3.7.0 release added the following features and updates to :
User experience improvements when snapshots are taken, providing more immediate information and snapshot detail.
Improved performance for downloading manifests of large spaces. Please note: manifests are no longer sorted by content-id by default. We improved the synctool's performance by reducing the frequency of checkpoints
Improved Sync Tool performance through checkpoint frequency reduction.
- Reduced Sync Tool download size and startup time.
- Users with USER role can now view streams on open spaces.The AWS SQS TaskQueue implementation now retries failed "puts".
- Improved error handling in queue deposit processing
- Improved bridge notifications
To see the full list of changes, or for more details on specific changes in release 3.7.0, see the JIRA issue tracker.
| Tip | ||
|---|---|---|
| ||
DuraCloud currently supports all of the major web browsers: Chrome, Safari, Firefox, and Microsoft Edge. As of version 3.7.0, DuraCloud no longer supports Microsoft Internet Explorer. This change is in response to Microsoft's recent end of support announcement for Internet Explorer. This shift allows development effort to be focused on delivering the highest quality user experience for the vast majority of our users. If you are still using Internet Explorer, we recommend you consider moving to one of the supported browsers mentioned above. |
Release 3.6.0
Released: November 23, 2015
The DuraCloud 3.6.0 release added the following features and updates to :
Administrators now see a "Request Restore" button on completed snapshots. Clicking this button sends DuraCloud staff an email and logs the event in the snapshot history.
All snapshots now have a "Preservation Network Member ID" field in the snapshot details, which captures the DPN Member ID.
When listing snapshots through the bridge REST API there are now several optional parameters to limit results.
Restore actions (requesting, initiating, completing, expiring) are automatically included in the snapshot history.
Non-administrative users can now view snapshots based on the permissions assigned to the associated space. So if a user has access to a space, they also have access to see the snapshots taken of that space.
- Performing multiple snapshots at once is now supported.
...