2019-31: Develop API for CCCApply Data Auto-Population

Request No.2019-31
Date of RequestJune 25, 2019
RequesterCCCTC - Tim Calhoon / Patty Donohue / Jennifer Coleman
Application(s)Standard / Noncredit
Section / Page

Full Application 

Steering Hearing DateTBD
Proposed Change to Download FileTBD (Not likely)
Proposed Change to Residency LogicTBD (Not likely)


Problem / Issue

Several statewide programs and organizations are requesting auto-population / data exchange collaborations between their apps and CCCApply, including CCGI (high school transfers) and Quottly.com (online course searches / course exchange with home colleges, etc.).  We are also sitting on a Promise Grant auto-population / pre-population change request (data exchange with Financial Aid programs, FAFSA, etc) .

Given our impacted schedule and un-approved funding level (unapproved workplan at this time) - we are challenged to prioritize these projects.  Discussions touched on developing a generic API that would be available to any legit org and/or project.


Proposed Solution

TBD - Placeholder - Work with Josh and the Apply dev team and ARC to design this API and estimate. 


Supporting Documentation

DescriptionFile TypeURLNotes
TBD







Dependencies, Risks and/or Reporting Requirements?


Question

Yes

No

Which data field(s)?

What/How?

Would this change affect an existing question or data field on the Standard Application?
  •  
  •  


Would this change affect an existing question or data field on the International Application?
  •  


  •  
  •  


Would this change affect an existing question or data field on the Promise Grant Application?
  •  
  •  




Would Account (OpenCCC) data be affected by this change?
  •  
  •  


Does the question or data field align to an MIS reporting requirement now?
  •  
  •  


Does this change affect any other state or federal regulations or requirements?

  •  
  •  


Would this change affect existing residency logic?
  •  
  •  


Would any other data fields be affected by this change?
  •  
  •  


Would students users be affected by this change?
  •  
  •  


Would colleges be affected by this change? 
  •  
  •  


Would the Download Client be affected by this change?
  •  
  •  


What other tech center web services will be affected by this change?
  •  
  •  

i.e., Glue staging table?  Multiple Measur
Other dependencies?



Other implementation considerations?