Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This solution should be targeted for Fall Quarter 2006. However, in the meantime a proposed solution is to use /afs/ as the root path for file content storage so that a common file system can be utilized. Until the AFS solution can be fully implemented, we are to utilize this strategy.

See current AFS file Mappings documentation for further specific details about the AFS file mappings for each one of the spaces below:

a. user's space
Create a .sakai directory within the user's AFS space that the Sakai user account has access to write to. User's will not be allowed to browse this directory, since it is only pertinent to Sakai.

b. course space
Utilize University of Michigan's current mapping (see above for format of file path) of course content. This will be a new directory structure from what is currently being used for MyUCDavis CourseManagement.

c. projects/research space
Sakai has many types of sites, and each install can configure these. There will be sites related to projects and research that can be expected. User's space, and possibly another space in AFS, will be utilized for these types of sites. Content stored in user's AFS space will count against the user's AFS quota, specifically the user who owns the site.

...