Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Request No.2016-41
Date of Request8.06.16
RequesterPatty Donohue;
Mike Caruso 
Application(s)CCC SSO Proxy
Approval

APPROVED

Proposed Change to Download ClientNO
Proposed Change to Residency LogicNO


Problem / Issue

To support CCC web applications using the SSO Proxy to create OpenCCC accounts, a download or transfer process is needed to return the new Account data fields and CCCID back to the college for upload to their SIS.  

Currently, existing college students who do not have an OpenCCC Account but are using a CCC web application (such as Assess, Course Exchange, or MyPath) or approved vendor application (such as Canvas, Hobsons), create an Account when they hit the SSO Proxy for the first time signing in to the application. Colleges need to know who these students are and want to store their Account data in their SIS systems. 

More understanding is needed to determine exactly what use cases need tthis account data, but multiple colleges have reuested this and the project has been approved by the Tech Center (Lou) and will be managed by Patty Donohue (OpenCCC PM) and Mike Caruso (MyPath PM).  


Proposed Solution

See "Comparison of Options to Share CCCIDs" -developed by Josh Helmer of Unicon. 
Meeting on 9.09.16 with the ARC team (Lou, John Scanlon, etc) reviewed the options and approved two options moving forward:

Best Long-Term Approach: Project Glue would provide the best real-time, long term approach for this requirement; however, due to amount of time reqiored to implement a single college with the College Adapter (Project Glue) it would not be feasible to implement the C.A. in the short term. Projects and colleges agree that  we need a short-term solution, but will ultimately implement Glue for this process.

Best Short-Term Approach:Develop mechanism/process to download Account data /Student Profile data via the Report Center. More details are needed before functional requirements are copmleted and technical specifications are completed. 


Action Items

  1. Need designated developer resource (Unicon or Tech Center?)
  2. Need technical and functional requirements drafted and approved;
  3. Budget needs to be approved;
  4. College implementation, training, and support documentation 
  5. Environment and 


Supporting Documentation


  • No labels