Data Responsibilities Statement Issue Documantation

Issue Summary

This issue is for the creation of guidance regarding the responsible use of university data. The Power BI Governance team created a website with an array of guidance for report authors in terms of report development & publication expectations. The website also makes clear the associated responsibilities of report consumers in ethical interpretation and usage.

September 2021 Proposal Forum

Resources

• Data Responsibilities Statement Proposal
• Proposal Forum Presentation Slides 

Forum Notes

• Originated with Power BI implementation in the Power BI Governance Team, but the team identified many of the responsibilities as universal across data platforms.
• Developing guidelines to get people to think about report publication
• We currently have APLs & external regulations (e.g., FERPA) that help shape the guidelines for:
  • Report creators responsible for using correct processes for determining what we can/should publish
  • Report consumers are responsible for their interpretations
• Aligned resources from other organizations, UMS APLs, and brought it together into a draft statement
• Looking to gather feedback for additional revisions ahead of publication
• This is currently proposed as a UMS resource, not an APL
• PBI gives us more choice on what we can share. We need to ensure privacy.
  • Aggregate vs. disaggregate data and small Ns are focal points for report creators & consumers

Comments & Questions

• Why is this not being pursued as an APL? It will be more visible if it is an APL, and more used
  • An APL is not ruled out--starting with a proposed published statement & could pursue APL publication down the road
  • There may be pieces to add/removeas time goes on and perhaps then could become an APL
• An additional aspect to include: the responsibility of people who can write reports at a campus and should not write for other campuses. This responsibilities statement might be a good place to address this expectation.
  • Perhaps we should add examples of this to the statement. Someone from one institution may not know the transformations for another.
  • Also knowing who to contact in those instances could be helpful to provide
• We are careful giving access to Query in Finance for this same reason of query providing broad data access that may be used incorrectly or inappropriately
• Can we identify who has what role (e.g., query writers) to ensure that folks receive communications such as this responsibilities statement? Agreed that APL would be preferable. 
  • Communication is one of our ongoing needs: getting the right info into the right hands without reaching out so often that folks ignore communications. We could use help identifying all of the groups for this.
• Also training for new query writers. Multiple forum participants commented that communication and training are needed regarding data best practices.

Resources & Research