Page Comparison

...

1. Determine bodypath for file storage, from ContentHostingService
   • Determine if bodypath exists via ContentHostingService. If exists, try toFind site To/when determining existence, find:
     • Site type from a Sakai reference object (that ContentHostingService uses) if site type is:
     • Depending upon which type of site, find the appropriate volume relative to the bodypath that should be created
   1. User Workspace Sites
      • Determine userid from reference path (e.g. /content/user)
      • From userid, determine user AFS home root from firstname, lastname algorithm. This is AFS HOME ROOT
      • Create bodypath as /afs/home.ucdavis.edu/home/AFS HOME ROOT/.sakai/INSTANCE
      • Save bodypath in file system, and run quota extension check against current size of resource (e.g. byte length)
   2. Personal Project Sites
   3. Course Sites
   4. Other Site Types (e.g. Institutional Project Sites)
   • else if bodypath doesn't exist.. try to run volume create script based on volume previously determined

Things to consider

1. There will be need to be a mechanism (tool?) to display how much user's space is taken by Sakai, etc. This will reduce the amount of support calls, and be consistent with the current CourseManagement tools available for MySpace. The tool ideally would be part of the user's resource area, integrated in their message of the day, etc.

...