Main Nav

Hi, I wanted to know how other schools are making course enrollment data available to applications. What policy/procedure do you have in place for requesting access to course enrollment data? I'd appreciate any links you could share to your school's policy/procedures. How do you make course enrollment data available to applications? Do you use Active Directory to publish course enrollment data? It would be especially helpful to hear from other PeopleSoft schools. Thanks, Dave ---

Comments

We do not publish enrollment data into Active Directory. And we are not a PeopleSoft school. But we do publish enrollment data into a directory which is then used to control authorization to services.

We have used the eduCourse object class to populate enrollment data in our directory service since fall 2007. We also created a uscEduCourse object class to extend it (schema listing at <http://www.usc.edu/org/iamsc/gds/docs/schema/ldif/uscEduCourse/94uscEduCourse.ldif>). This allows us to have a richer vocabulary for roles than the standard allows. The IMS standard is documented here: <http://www.imsproject.org/enterprise/entv1p1/imsent_infov1p1.html#1426006> with the Group Membership Roletypes (4.3.4.2) being the ones used by eduCourse.

We populate the following attributes in our person and account entries:

eduCourseOffering
eduCourseMember

uscCourseOfferingCurrentTerm
uscCourseOfferingNextTerm
uscCourseOfferingPriorTerm
uscCourseMemberCurrentTerm
uscCourseMemberNextTerm
uscCourseMemberPriorTerm

We use URL's that link into our Online Schedule of Classes rather than URN's.  And we append a status indicator (D, A, W) onto the member attributes to indicate drop, add, and withdrawn. The Offering attributes do not include dropped and withdrawn courses.

So eduCourseOffering looks like this:

http://usc.edu/courses/TERM/COURSE_ID/SECTION_ID

And eduCourseMember looks like one of these:

role@http://usc.edu/courses/TERM/COURSE_ID/SECTION_ID#D
role@http://usc.edu/courses/TERM/COURSE_ID/SECTION_ID#A
role@http://usc.edu/courses/TERM/COURSE_ID/SECTION_ID#W

USC has roles (overseer, grader, approver) that are not part of the IMS standard, so we map our roles to the IMS roles and use those in the edu attributes, and our own roles in the usc attributes. If a role doesn't map to an IMS role well, then we leave that role out of the edu attributes. Because the combination of term+course+section is unique over time, the eduCourse attributes contain the students entire enrollment history. Because some applications only want term enrollment information for current or prior or next term we populate the usc...CurrenTerm, usc...PriorTerm, and usc...NextTerm attributes.

All requests for data from the directory service go through a formal approval process documented here: <http://www.usc.edu/its/iam/aar>.

Regards,

Brendan Bellina
University of Southern California
Information Technology Services
IAM Manager

windows-hied@lists.stanford.edu so it can be noted on both lists> I'll try to be brief but these are broad questions. We've generally got what we call a Student Web Services (SWS), a RESTful web service, which provides a variety of student specific resources including course enrollment and grades. Access to SWS is granted after following an access agreement from our Registrar and agreement to the terms of a memo of understanding about how you'll use the data. We track your agreement centrally to enable/authorize student data access via other services in other use cases. The web service approach is part of our larger enterprise architecture redesign, moving to loosely coupled systems that are broadly re-usable in multiple scenarios. We also translate course enrollment data into our enterprise Groups Service (also a RESTful web service), with multiple "affiliate" systems that represent those groups which today include Active Directory, a legacy OpenLDAP groups directory, and Google Apps for Education. The web service and the 3 affiliated systems all reflect/restrict the data access controls that the Registrar has defined for this course data. I could say more about how we implement those controls, but I'm trying to be brief here. With the Groups Service, we don't limit ourselves to just 1:1 course to group representations, but also have groups by major, groups by curriculum code enrollment, and different time slices of those variations. I believe we also still support data feeds, i.e. flat file dumps of data, but given the variety of better options available, I believe that is discouraged. In terms of links for the access policy, this is probably useful: https://wiki.cac.washington.edu/display/SWS/Getting+Access+to+SWS. There's a slight variation for directory access (i.e. the group affiliate systems) but it's pretty much comparable. >
Notre Dame's approach is very similar to OSU. This would be considered restricted data except as used by our supported LMS system(s) and interfaces -- currently Blackboard Vista and soon to be Sakai and other provisioned course/class support systems such as provisioned class folders, possibly Box.com in the future. ODS/DW is considered our authoritative source for reporting purposes and we require data steward/custodian approval for all data use outside the aforementioned systems. -- Pat Miller
Close
Close


Annual Conference
September 29–October 2
Register Now!

Events for all Levels and Interests

Whether you're looking for a conference to attend face-to-face to connect with peers, or for an online event for team professional development, see what's upcoming.

Close

Digital Badges
Member recognition effort
Earn yours >

Career Center


Leadership and Management Programs

EDUCAUSE Institute
Project Management

 

 

Jump Start Your Career Growth

Explore EDUCAUSE professional development opportunities that match your career aspirations and desired level of time investment through our interactive online guide.

 

Close
EDUCAUSE organizes its efforts around three IT Focus Areas

 

 

Join These Programs If Your Focus Is

Close

Get on the Higher Ed IT Map

Employees of EDUCAUSE member institutions and organizations are invited to create individual profiles.
 

 

Close

2014 Strategic Priorities

  • Building the Profession
  • IT as a Game Changer
  • Foundations


Learn More >

Uncommon Thinking for the Common Good™

EDUCAUSE is the foremost community of higher education IT leaders and professionals.