Please complete entries for white cells (gray cells will be auto-populated). Choose Submit to save the new entry. Datasource This record Update Date Last Date this Record was Updated. Operating Unit current is --Select-- Agriculture and Life Sciences Alumni Affairs and Development Architecture, Art, and Planning Arts and Sciences Brooks School of Public Policy Computer and Information Sciences Continuing Education and Summer Sessions Engineering Facilities Financial Affairs Graduate School Hotel Administration Human Ecology Human Resources Industrial and Labor Relations Information Technologies SC Johnson College of Business Law School Libraries NYC Tech Planning and Budget President Provost Research Student and Academic Services Veterinary Medicine Operating units as defined by university policy 4.2 Contact Person NetID NetID Contact Person Name Contact Person Title Contact Person Campus Phone Data Steward Pursuant to University Policy 4.12, Data Stewardship and Custodianship, the identified vice president or dean. Abbreviation The shortened name used to refer to the data set. Familiar Name The familiar or commonly used name for the data set. Data Set Business Name The business name for the data set. Type Of Data Alumni Facilities Financial Data Health HR IT Network Data Planning and Budget Sponsored Research Student Video Surveillence Other The type of data in the data set. Check all that apply. (Alumni, Facilities, Financial, Health, HR, IT, Network Data, Planning and Budget, Sponsored Research, Student, Video Surveillence, Other) Source Data From The list of applications and/or databases that source data to the data set. Data Provenance A description of the path and transformations of how the administrative data set is sourced from systems of record. Data Scope Succinct description of the scope and granularity of the data set (e.g., prior six months, since the installation of a system X, etc.). Note that this includes administrative data assets purchased by the university, created from university systems, or machine generated. Data Usage Narrative Summarized information about which systems and/or functional areas use or consume the administrative data set. Audience The business or functional staff members who consume or otherwise use the administrative data set. Access Methods A list of commonly used methods by which users access the data set. BI Solutions A list of existing Business Intelligence (BI) solutions used by the university to access the data set. Examples include Oracle Business Intelligence Enterprise Edition (OBIEE) and Tableau. Size Metrics Approximate number of records and size of data store. Data Currency How often and when the data in the data set is updated. Housed By Where the data set is housed (e.g., on premise or cloud). If on premise, the name of the campus location and if in the cloud, the cloud vendor’s name. Maintained By The university operating unit that maintains the data set. Often this is not the functional area. Maintenance includes responsibility for data refreshes, data structures, and data representation. High Risk Data? Yes No Does the data store contain high risk data as defined by university policy 5.10? (SSN, credit card nos.,driver's license nos.,bank account nos.,protected health information as defined by HIPPA). To Request Access Link to or other information related to requesting access to the data set. Database Technology The database technology used by the data set (e.g., Oracle, SQL Server, MySQL). Data Model Summarized representation of how the administrative data set is structured. Examples include Denormalized (relational), Relational, Dimensional, Cube, etc. Metadata Yes No Data about the data. The registry identifies if this information is available for the administrative data set in question (i.e., Yes or No). Security - Role Based Yes No Yes or No according to whether or not Role Based security is implemented in the data set and, if Yes, a simple description of how this is done. Security - Row Level Yes No Yes or No according to whether or not Row Level security is implemented in the data set and, if Yes, a simple description of how this is done. Table and Column Attributes Available Yes No Yes or No according to whether or not Table and Column attributes (metadata) are available for the data set. ADSR Operating Unit Delegate NetID ADSR Delegate Name ADSR Delegate Title ADSR Delegate Campus Phone Delete Submit Cancel
