Meeting Details
Agenda
Item | Notes | |
---|---|---|
1 | Update on 2.1 pilot and support for Canvas data | CCC Data 2.1 in pilot. The release to include:
Canvas is configured at the root level, while some colleges have chosen to configure Canvas at the college level, most implementations are at the district and Canvas does not provide a way to segment to the college. We have been working with Canvas to identify how to identify colleges through the API and find that their system does not support this. This makes the process of segmenting the data to the college challenging, and while we believe we can segment some of the data, this will be a time consuming process. Instructure has indicated a possible October release date for Canvas 2 which will necessitate reworking these data pipelines and may resolve these issues. With this CCC Data 2.1 release, Canvas data will be supported through a direct connection to the DW, where the district or college elects to have their data stored in the DW; it will be available only at the district level, except where
We continue to speak with Instructure to understand the timing of Canvas 2, and we are working to identify CCC’s in the pilot so that we may start working in an upcoming release in preparation of colleges moving over to this new version. Post processing segmentation is possible, but given that a new version of Canvas is on the horizon all the work would have to be redone. We will do what we can with the pilot colleges and the API (direct connect), but we are approaching the work as a dual phased approach, with the next phase beginning around October 2021 with the release of Canvas 2, at that point we will either be able to take advantage of the new API or start investing in the post process segmentation of the data. South Orange Community College District expressed issues with a district implementation of Canvas so they are moving to separate their instances by college. North Orange Continuing Education reported that they were expecting to have to educate and communicate through multiple levels including faculty. Faculty would be key in moving things forward at the local (College) level. MIS codes are not inherent in Canvas data as most of the individual college Canvas data is stored in sub accounts at the college level and the CCCTC will need to map MIS codes to the sub account IDs. |
2 | Update on 2.2 release currently in development | The CCC Data 2.2 release, now in development, will include:
With the CCC Data 2.2 release we are also completing the segmentation of MIS data and will be seeking approval from the CO to make these data available to the colleges through the DW, direct connection and report server with ad hoc reporting available. We also plan to work on segmenting SCFF data within the Launchboard data in the DW, pending availability of analyst resources and CO approval. This release is tentatively scheduled for September 2021. The roadmap for FY 21/22 underway, we expect to update the DW Advisory group during the July meeting. |
3 | Update on Data Warehouse survey | We are holding off for the summer, looking to identify the best timing for feedback. There are some edits to be made before we do release this. |
4 | Discussion on student identifiers | Dustin J. Tamashiro from Pasadena The student ID was added to MIS, though not in the data dictionary. It is present as the 7th column in the SI file: https://webdata.cccco.edu/ded/si.pdf. He can discuss it as something the RP Group or someone should do a webinar on for researchers at colleges that are less familiar with the MIS tables How to navigate schemas or historical documentation for certain data fields, ie.”5 years ago we didn’t keep track of X” so if an IR is going back they will be able to navigate the data. Best practices for utilizing data base information? Navigating schemas, general information, would be helpful- how do we support all the colleges in a broader sense? How does the RP group support IRs now from a technical perspective? RP group has been helping with:
|
5 |
Issues/Questions Resolved
Issue/Question | Resolution/Answer | |
---|---|---|
1 | Date Issue/Question Raised: Is Data on Demand being retired? | Date Resolved/Answered: No formal answer at this time, but updates are anticipated in the near future. Owner: Alex J. |
2 | Date Issue/Question Raised: | Date Resolved/Answered: Owner: |
Issues/Questions Needing Resolution
Issue/Question | Resolution/Answer | |
---|---|---|
1 | Date Issue/Question Raised: | Date Resolved/Answered: Owner: |
2 | Date Issue/Question Raised: | Date Resolved/Answered: Owner: |
Action Items/Next Steps
Item | Notes |
---|---|