...
- Type: course website
--Academic Term: Summer 2006. We need to handle this better, in that the term will appear when the user selects the Site Info tool. We need to sync the properties data with Banner at some point, and Sakai 2.2 handles this properly with the site manage tool. - Title: BIS 001A 001 (appears in the tab)
--Note, this will create a site with the format "SUBJ COURSEID SECTION". Based on what academic term was selected previously, the tab will show a Quarter that is not synced up directly with what will be used in the batch provisioning process at a later date. The batch process uses the format SUBJ COURSEID SECTION TERMABBREV TERMYR - Roster: Choose I want to give access to a roster not listed above
- Authorizer's name: account that authorizes this site to be created. E.g. sitemaker
- Short Description: some short description of the course
- Description: some description of the course
- Appearance(icon): default
- Contact, Contact email information
- Tool Set: Email Archive, etc. Whatever tools you want to have in site. Is there a default set?
- Publish site?: yes
- Role to assign to joiners: (e.g. Student, Instructor, etc.) Course sites will have default of "Student" role assigned.
- Select "Request site" upon confirmation of details.
Site is then created for you.
Adding tools to the site
- Default tools to use are:
- Home Schedule(already enabled)
- Announcements (already enabled)
- Assignments (first one w/ Gradebook)Resources
- Chat Room
- Drop Box
- Email Archive
- Gradebook
- Message Center
- Modules
- WikiResources
- Email ArchiveSchedule
- Site Info (built-in)
- Syllabus
- Test & Quizzes
- Message Center
- Help (built-in)
- Web Content (blank) (I was told this is difficult to implement on the auto-generated sites, so we're leaving it out now)
- Web Content (Support & Training, with this URL: https://sakai2.ucdavis.edu:8443/access/content/group/4141a796-68f5-498e-8049-be120b6d9e59/support_training.html)
- Wiki
Making your site joinable
...
List of kerberos names that you are adding to the site. If you don't have a list of kerberos logins, you can convert their UC Davis email address into their associated login IDs using this tool: Script to Acquire K-IDs Bulk Email to ID Converter
- Log in as the Sakai account that created the above site (if already still as this user, go to next step)
- Select "Worksite Setup" from left hand menu item
- Select the site you want to add members to, and click the "Revise" link at center, top of screen
- Select the "Add Participants" link at center,top of page
- When given the textarea to add participants, add the given kerberos names with a hard enter after each name
- Check to see if the kerberos names were added correctly. If any of the names have a "UCD: " in front of them, then they are incorrect. You probably entered the first part of their email address. They should be listed in the "roster" of the site
- Define whether or not you want to give roles to the members independently, or as a group. For example, if I wanted to add 5 members as all having access I can give all members the access role at once.
- Give appropriate members their respective roles in the site, and check the member list.
- Save the site
- Exit site
**See attachment screenshot of Update Site Participants for more information.
Fixing Message Center permissions
The permissions are blank on newly created sites. This must be fixed by clicking "Return to Sites List" (if you are still in the "Worksite Setup" area and revising a site.
- You may have to type in part of the name of the site to bring it up on the current page
- Click on the site name you created
- Click Message Center (left hand side)
- Click Template Settings
- Click the Revise button
- Click the arrow next to Permissions to expand them
- Permissions are as follows:
- Student: Contributor
- Instructor: Owner
- Teaching Assistant: Author
Adding site to list for programmers (Automatically pulling rosters from Banner)
- Go to the following URL:
- https://confluence.ucdavis.edu:8443/confluence/display/UCDSAKAI/SiteMaker+Sites
- Add the required information to the bottom (CRNs, date SmartSite was created, etc.)