Archive, Delete and Restore Use Cases

This page is meant to assemble a set of short (1 paragraph) use cases around the issues of Sakai site archive, delete, and restore. Please be as specific as possible in defining the user expectations.

David Haines (U-M)

From a support request: One of our film classes has put 100 hours of raw footage for their group project on a project site. The final film is done and most of that footage will likely never be seen again, but it might be invaluable in the law suits we are expecting. We would like to a) have the site archived so the footage is removed from Sakai (but can be recovered if necessary) and b) have a copy of the site exported and delivered to us so that an archival copy can be kept off site.

Goals:

• A recoverable archive - does this archive need to be fully restorable?
• An exportable archival copy of the site - how complete does the export need to be? does it need to be restorable? what should be in it (e.g., the film footage) and what can be left out (e.g., permissions, user list)?

David Haines (U-M)

To manage disk and database space, Support archives a site with a large number of resources that has had no apparent activity in the last X months. The archive process removes the site and the resources from Sakai.

David Haines (U-M)

A researcher's project site was removed due to lack of activity, but the user considers the resources valuable research material and requests that the deleted site be restored.

Steve Swinsburg

An individual site needs to be moved from one Sakai server to another, or duplicated across many servers. A complete and full archive of a site should be able to be created that can be moved around as a single entity and imported into any number of Sakai servers.
Our use case is we need to move a site from one server to another.