Table of contents Affiliate sponsorship Types of Affiliates Basic Affiliate vs Regular Affiliate Basic Affiliate Regular Affiliate Non-paid appointment vs. Affiliate record Use the Affiliate information screen Required notification to be given to Affiliates On-Line Dean/VP approva

Table of contents Data stewardship structure Data owner Data trustees and DPAC Data stewards Data managers Data users Data subsets, managers, stewards, trustees, and DPAC The University of Maryland, College Park recognizes the importance of university data as a resource of the

The Data Policy Advisory Committee (DPAC) approved the creation of a Power Users group in 2013. The Power Users have access to Student data for all schools, in addition to data for their own school. There are two possible Power Users appointed per school or division. Each Dean may identify one Power

Table of Contents Level 1: Low Services Level 2: Moderate Services Level 3: High Services Level 4: Restricted Services Further reading Level 1: Low Services Any DIT supported service can be used to store Level 1: Low data. For example, Google Drive can store and share Level 2 and Leve

Table of contents Use of forms PHR unit types Moving a unit Informing affected groups of the unit change PHR unit report Use of forms The Unit Code Maintenance Forms can be used for creating new units, moving units, changing unit names, or making units obsolete. Use the appropriate fo

Affiliates are individuals who receive University services and who are not students, employees, or non-paid appointees. The Request for Employee Designee Affiliate is to be completed by a Regular employee (or Contingent II employee if included in their contract) of the University of Maryland to des

A| B| C| D| E| F| G| H| I| K| L| M| N| O| P| S| T| U A Advanced Sick Leave/Extended Sick Leave Tracking The UHR Information Services unit centrally manages and monitors the UMCP employee usage of Advanced and Ex

Denodo is a data virtualization application that integrates enterprise data across disparate systems without replication. The Denodo community website describes that data virtualization creates a single virtual layer that connects disparate data and provides unified access for consuming applications

This article provides steps for approvers to manage the Kuali Rice workflow to approve or disapprove requests for data warehouse access by potential Power Users of  student data.   You will receive an email with a request for action from the Rice workflow. You can click on the link

Listed below are University of Maryland policies which are pertinent to the delivery of data to the campus community. The policies may be found on the President's page of University Policy. VI-22.00(A), University of Maryland Policy on Institutional Data Management VI-23.00(A), University of Ma

This document provides steps for potential Power Users of student data to request access to the data warehouse using the Kuali Rice workflow.   To access the form, click Data Warehouse Access request. Log onto the Central Authentication Service (CAS), After you have successfully logged

The Oracle data warehouse at University of Maryland (UMD) is restricted to users who have been approved by Data Managers to access certain subsets of data. Once a user is approved by a Data Manager to access the data warehouse, certain reports, tables, and views are made available for the user to vi

Departmental users of the Oracle Data Warehouse may request that columns or tables be changed or added to the existing warehouse of current, future, historical or frozen data. The process for doing so is as follows: The Requestor lists what is required and contacts the Office of Data Administrati

Table of contents Approval actions Task actions Following requests History Data stewards can review and approve Ad-Hoc Query Access Requests, and related training tasks, from the special Data Steward dashboard.  This dashboard is only for Data Access requests (including Ad-Hoc, PHR