Sakai Data Storage - Campus Installations

Sakai Data Storage - Campus Installations

Existing File System - AFS

Currently, UC Davis people have home directories in AFS space, and that CourseManagement also utilizes this space.

1. User's AFS Space Allocation
2. User space in AFS is in the form of the directory stucture below:
   /afs/home.ucdavis.edu/home/sn/samerson
   Above, sn is the first initial of firstname, and last initial of lastname.

1. Course AFS Space Allocation
   AFS space for courses is allocated via CRN, and CourseManagement in MyUCDavis writes data to this directory. The ACL is the MyUCDavis user.

Problem Statement

Here are some of the questions we need to answer:

1. How do we integrate Sakai's resources and our current AFS file system?
2. When user's create worksites, how does this get mapped?
3. What location does it get mapped?
4. Do course type of worksites get stored in existing AFS CourseManagement space?
5. Where do project/research/ or any other non-user and non-course Sakai sites get stored?

How Sakai stores content

Current Sakai architecture supports storing course and user content both inside/outside of a database. The content path can be mapped to any given path one gives it in the sakai.properties configuration file.

Proposed solution(s)

a. user's space

b. courses
Use the ACL associated with the current MyUCDavis user, however make the reference now the Sakai user.