Page Comparison

...

1. Determine bodypath for file storage, from ContentHostingService
   • Determine if bodypath exists via ContentHostingService. In order to determine 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
       
   User Workspace Sites
   • • ##*--> Determine userid from reference path (e.g. /content/user)
2. From userid, determine user AFS home root from firstname, lastname algorithm. This is AFS HOME ROOT
3. Create bodypath as /afs/home.ucdavis.edu/home/AFS HOME ROOT/.sakai/INSTANCE
4. Save bodypath in file system, and run quota extension check against current size of resource (e.g. byte length)
5. Personal Project Sites
6. Course Sites
Other Site Types (e.g. Institutional Project Sites
• • , or other pertinent information from reference depending on site type (e.g. siteid, etc)
• else if bodypath doesn't exist.. try to run volume create script based on volume previously determined
7. Save file given by ContentHostingService, and run quota extension check against current size of resource (e.g. byte length)
8. Handle errors (checked exceptions) at the Java level via: AFS errors bubble up from shell/perl script to Java level
9. No errors, no logging
10. If errors, log errors and either try again (e.g. quota extend), or fail and throw exception (e.g. AFS down)

...