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
       ##*--> Determine userid from reference path (e.g. /content/user), 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
2. Save file given by ContentHostingService, and run quota extension check against current size of resource (e.g. byte length)
3. Handle errors (checked exceptions) at the Java level via: AFS errors bubble up from shell/perl script to Java level
4. No errors, no logging
5. If errors, log errors and either try again (e.g. quota extend), or fail and throw exception (e.g. AFS down)

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.

2. The path for storing content should be highly configurable via properties, or other variables.