[Using Sakai] Adding Rosters --

Fri Mar 11 11:59:08 PST 2011

Hi Chris,

I am not too sure but I found the following at 
https://confluence.sakaiproject.org/display/SAKDEV/Course+Management+Integration,
 so you can try it or check on the dev list for other ideas.

The default implementation generates a provider ID string by concatenating all 
section EIDs with ""  signs. (For example, if a course site has been created and 
associated  with rosters from the sections "CHEM 101 LAB 002 F2007" and "CHEM 
101  DISC 002 F2007", then the site's provider ID will be set to "CHEM 101  LAB 
002 F2007+CHEM 101 DISC 002 F2007".) The only reason you'd have to  change this 
code is if section IDs at your institution include the "" character.

 Thanks,
Anand

________________________________
From: "Brandt, Chris M." <cmbrandt at ucdavis.edu>
To: Anand Mehta <anand.mehta at yahoo.com>; "sakai-user at collab.sakaiproject.org" 
<sakai-user at collab.sakaiproject.org>
Cc: "Fischbein, Scott A." <sfischbein at ucdavis.edu>
Sent: Fri, March 11, 2011 10:28:49 AM
Subject: RE: [Using Sakai] Adding Rosters --

Thanks Anand.

In the old message you reference, Steven Marquard said: 
“To associate a course site with a class list that your provider understands 
(i.e. to populate a course site with student membership from your SIS), you need 
to update the site's realm through the Admin tools - Sites to find the site id 
(if you don't already know it) and Realms to update the provider id for the 
respective /site/siteid realm. What you put in the provider id is dependent on 
how your local provider is written (e.g. we would have SUBJ101,2007).”

The Provider ID seems to be a single entry for us – ex: 
http://vetmed.ucdavis.edu/course/section/SPH/266/001/201103-- since I’m trying 
to combine 2 cross-listed courses into a single course worksite, how would I 
adjust this to allow multiple providers?

Thanks!
Chris
____________

Chris Brandt, DVM, MS
Instructional Media Development Specialist
Computing and Technology Services (CATS)
UC Davis School of Veterinary Medicine 
http://www.vetmed.ucdavis.edu
(530) 754-4452

From:Anand Mehta [mailto:anand.mehta at yahoo.com] 
Sent: Friday, March 11, 2011 7:34 AM
To: Brandt, Chris M.; sakai-user at collab.sakaiproject.org
Cc: Fischbein, Scott A.
Subject: Re: [Using Sakai] Adding Rosters --

Hi Chris,

Please take a look at http://article.gmane.org/gmane.comp.cms.sakai.devel/11697 
for the requested status issue. The roster link is probably disabled for 
instructors by unchecking site.upd.site.mbrshp or some other site permission in 
the course site's realm. The terms come from the cm_academic_session_t table and 
the ones with is_current set to true are displayed in the drop-down list.

Thanks,
Anand

________________________________

From:"Brandt, Chris M." <cmbrandt at ucdavis.edu>
To: "sakai-user at collab.sakaiproject.org" <sakai-user at collab.sakaiproject.org>
Cc: "Fischbein, Scott A." <sfischbein at ucdavis.edu>
Sent: Thu, March 10, 2011 1:34:04 PM
Subject: [Using Sakai] Adding Rosters --
A couple of quick questions:

When I’m an admin, I’m able to initiate the process of adding a roster to a 
course worksite, but it always comes out as ‘requested’. How does this get 
approved?

When I’m SU’ing as the instructor of record, the ‘Add Roster(s)’ link doesn’t 
appear. Which permission controls this?

if I add the instructor to the admin site (just for testing), and go to the same 
site, the link is available and I can see a dropdown for the term and a list of 
the courses in that term. What controls which terms are included in the 
dropdown?

Thanks!
Chris
____________

Chris Brandt, DVM, MS
Instructional Media Development Specialist
Computing and Technology Services (CATS)
UC Davis School of Veterinary Medicine 
http://www.vetmed.ucdavis.edu
(530) 754-4452

From:sakai-user-bounces at collab.sakaiproject.org 
[mailto:sakai-user-bounces at collab.sakaiproject.org] On Behalf Of Steve Swinsburg
Sent: Friday, March 04, 2011 3:30 PM
To: Chandrika Harathi
Cc: sakai-user at collab.sakaiproject.org
Subject: Re: [Using Sakai] More on DB

Hi,

There are some architecture documents in the source code at 
/reference/docs/architecture. Some are a bit dated though.
As for table naming conventions, developers are free to do what they like, 
however the adopted practice is that tools prefix their own tables. So the 
tables for Profile2 all start with PROFILE_. Site Stats all start with SST_ for 
example.

One thing to note is that if your app doesn't 'own' the table in your own 
tool/service, you shouldn't directly touch it. You should instead use the API 
that the app provides. This goes for the rest of the Sakai DB tables as well. 
Never directly modify the tables, use the API.

cheers,
Steve

On 05/03/2011, at 7:52 AM, Chandrika Harathi wrote:

We are evaluating sakai. We have installed sakai 2.7 to evaluate/test. Where can 
I find the more information on the DBschema : ER diagram ,  table naming 
convention or similar.
Thanks,
Chandrika

-- 
Chandrika Harathi
Programmer Analyst II
IST-AST
1 Worlds Fair Drive, Suite 3900, Somerset, NJ 08873
Ph: (732) 743-2554
Fax:(732) 745-4525

CONFIDENTIALITY NOTICE: This email communication may contain private, 
confidential, or legally privileged information intended for the sole use of the 
designated and/or duly authorized recipient(s). If you are not the intended 
recipient or have received this email in error, please notify the sender 
immediately by email and permanently delete all copies of this email including 
all attachments without reading them. If you are the intended recipient, secure 
the contents in a manner that conforms to all applicable state and/or federal 
requirements related to privacy and confidentiality of such information.

<harathch.vcf>_______________________________________________
sakai-user mailing list
sakai-user at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-user

TO UNSUBSCRIBE: send email to sakai-user-unsubscribe at collab.sakaiproject.org 
with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-user/attachments/20110311/c986a3d7/attachment-0001.html 