| 1 | OT-SC + DWW SILS Analytics check-in | Discuss UCOP Statistics and Analytics in SILS | 50 mins | Team | Goals for today: Instead of the write-up and ask document that has been prepared, what if we went back to a 3-5 bullet point document to provide to DOC Most of the anxiety at UCB, was how to go about collecting the stats; hoping the NZ analytics could serve some of that but realization that it has to happen on an IZ scale caused anxiety There is an assumption that we can use templates from already Alma campuses, but for some of the new to Alma campuses, this reporting might be more complex Would still require quiet a bit of modification for UCB to use what some of the already Alma campuses have done previously
Interested in how the current context can be massaged to further set the stage for the recipients of the write-up The purpose of doing a smaller 3-5 bullet point document would be to set the expectations for what the data will look like this year, especially pointing out the issues with the data But do not include an ask; just acknowledge the present state with which we will be reporting Do not have to report the specific areas that will be problematic, just note that the data is compromised
Seeking excusal is not possible, some data (ARL) is a requirement of membership What would be the outcome we might face if we produce “wonky” data and caveat it - would there be negative outcomes from that? Depends on the data, but would be a campus specific decision as to whether they use that data, or use previous year’s data It’s okay, this has happened before; this is a larger scale since it is a systemwide issue Besides working with the vendor and continuing to do data clean-up, this is the best we could do at the moment It’s not up to a systemwide group to decide what individual campuses will do to report to third parties, etc.
Even if the data is crummy, it’s still good Normalize that we are restricted by the systems we use, and it’s no individual’s fault Support one another, support that everyone is still learning, etc.
Why is SILS-OT trying to be on top of this; what is the scope of what SILS-OT is trying to do? How do we want to use this meeting to support success with the greater group tomorrow? This meeting will help layout the changes in approach; at this point we will not be asking for anything, just describing the situation Need to explain to the larger group the changes in approach Explain that we don’t need to ask for permission to have “wonky” stats, and instead tell DOC and CoUL we will be doing our best, but nonetheless, we will have issues with our data because of x, y, and z
And then open it up to questions from the larger OT group
Would be helpful for Danielle to explain our obligations with the data reporting at our OT meeting tomorrow In terms of what’s the best path forward, who would be best to address that? Danielle can speak to the consequences of having “wonky” data Also want to touch on tomorrow, the update from ExL that they know what we want even if they can’t provide it right now Decision on the current write-up: freeze it as is, and pull from it as needed 3-5 Analytics Bullet points document Q&A Document Who will be drafting the next write-up to DOC and CoUL aka the 3-5 bullet points? Caitlin, Tom, and Jackie can work on drafting this new write-up, using the previous write-up as a jumping off point At the end of the discussion tomorrow, explain that we are re-working it from an ask to a current status document and open it up to folks from OT if they want to participate in writing this new document It was really helpful to have John assist with the previous write-up, so we should ask if he is willing to help with the new write-up
| | |