Report to Data Governance Executive Sponsors from Data Governance Council
August 2007
July Meeting
The data stewards met as the Data Governance Council on July 11. In attendance were Johnie Sullivan (presenting), Elora Paik, Anthony Vaughn , Monty Young, Gwenn Pons, Susan Hobbes, Karen Emptage, Lynne Personius, Christina Drum, Stacy Shiroma, Josh Brauer and Mary Williams. Two new members, Josh and Stacy representing the Law school were introduced.
Meeting minutes available at:
http://unlvdata.nevada.edu/DGCouncil/Administrative.minutes.7.11.07.html
Security and Data Privacy
Johnie Sullivan discussed OIT Security policy. He emphasized that the focus is on compliance. There is one capstone policy that says that UNLV will use computer security to protect assets. Other policies are written to enforce this, and to focus on specifics.
Policy 1 - Policy standards are the requirements that have to be met to satisfy the policy. Arrive at them by considering privacy and confidentiality, and then classifying the data accordingly. The policy goes beyond the “official” data base to include copies of data that reside on laptops and desktops.
Data stewards will look at the data within their control, and classify it. Together with the security office, they will look at how to protect it.
Retention and destruction policy is important. In some places paper records are a problem.
The Data Management Issue Resolution Process
The following data management issues are being analyzed by data stewards who are working together with colleagues toward consensus.
Pending
1. Terminal Degree Designation, submitted by IAP, owned by Elora Paik
Description of this data issue: HRMS does not have a field that identifies terminal degrees (the highest attainable degree within a particular academic discipline).
2. Tech Room Designation submitted by Anthony Vaughn , owned by Don Diener
Tech rooms - designating them is removing the indication of whether or not they are a lab, classroom, seminar room,
3. SIS Room Inactivation submitted by Anthony Vaughn, owned by Karen Emptage
The SIS data base has rooms that need to be inactivated, and who is responsible for this?
4. Building Room Data Inconsistencies submitted by Lynne Personius, owned by Rick Storlie
Where there is common data, it must be the same in every system. However, where each application uses data that is specific to their own needs, that data will be kept accurate by the system where it is needed.
5. Exemption and Deal Codes submitted by Lynne Personius, owned by David Ellison.
Exemptions may be granted for a number of different reasons, and so different codes are (presumably) entered by different units across campus. This process is unclear. Also, the timeliness with which these codes are entered on SIS appears inconsistent, and sometimes occurs well after a semester has begun. However, there is a need to access this information earlier and more consistently from term to term (to the extent possible) in order to more accurately project enrollment-based revenue.