Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Meeting Details

Page Properties

Meeting Date:

14 Jun

Purpose:

Data Warehouse Advisory Group

Zoom Recording:

Zoom recording link

Participants:

Mark Cohen

, Alex Jackl

, Jon Fanucchi,

Dustin Tamashiro, Mano Stefanakos

Denice Iciong, John Sills, Steve Klein,

Bridget Herrin, Craig Hayward, Denice Iciong, Dulce Delgadillo, Jake Kevari,

Virginia Moran, Jenni Allen,

John Sills

Z Reisz, Valerie Lundy-Wagner,

Z Reisz

Agenda

2

Update on CCC Data 2.2 (currently in development)

The CCC Data 2.2 release, now in development, will include: 

  • Updates to how user accounts are managed, including: 

    • SSO support (login access to existing college accounts)

    • Keycloak integration 

    • self-service password reset for the DW Report Server 

  • Support for Student Success Suite products, including: 

    • MyPath reporting in the DW Report Server, and 

    • OpenCCC 2.0 Schema Changes

  • Technical debt, including: 

    • updates to reflect changes in data sources as necessary, and 

    • Pipeline refactoring to AWS recommendations 

With the CCC Data 2.2 release we will also be 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 is 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 started the discussion regarding support for accessing MIS data.

It was discussed as whether the RP Group or someone could support with a webinar for researchers at colleges that are less familiar with the MIS tables.

It was discussed how the RP group can support IRs from a technical perspective.

RP group has been helping with:

  • Develop new metrics,

  • Methodology,

  • training,

  • supplemental documentation

  • SQL Training

It was discussed that the RP conferences could include support for IRs in using tools to access CO data.

5

Item

Notes

1

Update on CCC Data 2.1 release and piloting access to Canvas data with two colleges.

CCC Data 2.1 production release. The release includes:

  • Data Warehouse Report Server upgrade to Jaspersoft 7.8

  • COCI and C-ID data in the Data Warehouse and DW Report Server

  • Support for MIS, NOVA, and Launchboard data in the Data Warehouse (Limited to authorized CO accounts)

  • Canvas data in the DW

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 the Canvas data API does segment by college. We have discussed with Instructure how to identify colleges through the API and haven’t yet found a solution.

Instructure has indicated a possible October release date for Canvas Data 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

  • the district is made up of a single college, or

  • the district has configured their Canvas system at the college level. which will allow the data to be made available to the district and college. 

We continue to speak with Instructure to understand the timing of Canvas Data 2, and we are working to identify CCC’s in the Canvas Data 2 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 two 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 Data 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.

Welcome

  • Brief welcome

  • Overview of history, personal connections to project, and high level goals

2

Level-setting & quick updates

  • 2.2 still underway, SSO focused

3

DW value for the system

  • SCFF

  • How do we validate data?

    • Some colleges have been doing self checks with people familiar with data that are uploading

4

Maximizing the DW

  • Time to explore and better understand tool and DW capabilities seems to be at a premium- common uses and static reports were vocalized to be potentially helpful

  • Training would be a huge factor in updating knowledge about the tools and capabilities of the DW

  • CVC would be the appropriate vehicle for helping to align training across the statewide system

  • What can Ellucian and Peoplesoft do to help

5

Goals for AY21-22

  • Merge MIS and 320 reports?

  • Static reports that will help most every college if possible

    • Validate MIS information? SCFF metrics?

    • Program Award recipients?

    • Financial Aide?

    • Dual Enrollment?

    • Calendar

  • Group to be leveraged for strategy

Issues/Questions Resolved

Issue/Question

Resolution/Answer

1

Date Issue/Question Raised:

Is Data on Demand being retired?

Date Resolved/Answered:

There are no formal plans at this time to retire Data on Demond.

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:

14 Jun

Date Resolved/Answered:

Owner:

2

Date Issue/Question Raised:

14 Jun

Date Resolved/Answered:

Owner:

Action Items/Next Steps

Item

Notes