Page Comparison

Discussion: Policies and Procedures for making Student records available via the data warehouse

• Presenter: Mark Cohen with discussion from all

• 1) Related to AB705, as students attend other schools and

• 2) Where are students going who live in my district (are they going to somewhere else).

• Will need policies and permissions (from both students and colleges)

• Denise: 4 multi college districts in Orange County. Could use the DW to share. Outcomes should be a consistent dataset. Want to make sure there is a MOU in place, strong WF program, it’s specific about what data is being shared so thus one MOU did not work but instead one for each project, so the need is to have one consistent set of data (Orange Coast, Rancho)Interest in sharing student enrollment data across colleges to see where students are taking classes (are students living in my district going somewhere else?). Could potentially help with AB1705 Implementation.

• Discussed data sharing agreements and MOUs between colleges.

• Privacy concerns around FERPA and sharing student records. FERPA allows some data sharing from college A to B.

• Students should have the ability to opt out, and the CO does not collect that. The closest they get is the application where student checks the box to share.

• The National Clearing House, they create a set to send… a FERPA level, directory information. So she knows there is a setting that says the student says blanket “do not share”. Denise to look for data element dictionary.

• Jake suggests to use CO CCCID and not the SSN. Challenge with student key, is that it is by college, so even a multi college district would have challenges.

• Denise shared : Here is the information on the National Student Clearinghouse Privacy Block Setting - https://help.studentclearinghouse.org/compliancecentral/knowledge-base/privacy-block-setting/ thus suppress records for students with privacy blocks; need to determine appropriate data elements and aggregation level.

• This group to work on suggesting policies and permissions for accessing these records moving forward.

Update on Canvas Data 2 in CCC Data Warehouse

• Presenter: Mark Cohen

Support for CD2, richer data set. Pilot successful introducing data, had a bump with Instructure, they then provided instructions on how to call the API, so we reconfigured it, and now preparing to launch it. Multi college districts implemented with a district office at the root instead of a college at the root, we expect to announce that we can offer segmentation at college level that we can bring in the data and break it out by college. If district level and then college identified at the sub account.

Most multi-college district IVC: first implemented at district, then reconfigured at college level. North Orange also implemented at institution level.

• Canvas Data 2 API integration is nearing completion, will include learning outcomes data. Broad interest expected.

• Will also include multi-college district segmentation at college level, sub account.

• Working on associating unsubmitted applications to a term to make them easier to analyze.

• There would be messaging communication coming out as the pilot date gets closer.

Discussion: Exploring API access support for connecting to the CCC Data Warehouse

• Presenter: Mark Cohen

• ODBC connection was previous, now looking at an API connection. There was interest but have not heard from the college, can you comment?

• Denise The data warehouse may soon offer API connection as an option instead of only ODBC.

• There was little feedback on the preferences, so more conversations at technical levels will inform this decision. Input from Denise, she shared that IVC is a pilot. It took time to configure the API.

• Mark to be at CISOA to get more feedback.

Follow up on high priority data sets to be added to CCC Data Warehouse

• Presenter: Mark Cohen

• The group discussed the previously identified top data priorities.

• VAR data will come into MIS and the DW after 2025.

• EDD Wage files are of high interest, if data sharing agreements could be amended.

• Discussion that CSU data may have more value over that from UC.

Agenda items for next meeting? Policies language

• Send agenda items for May meeting to Erik or Mark.

• Come back with policy suggestions for accessing student records across colleges (for students and colleges sharing data

• ). May use some language from NSC

• .

• Mark to give update on API vs ODBC preferences from conference.

• Finalize details and communicate availability of college-level Canvas data.

• Consider modifications to data sharing agreements that could enable inclusion of high-priority datasets in the future, like EDD wage files.

Questions and Feedback

Next Meeting: May 14th.