The Data Cookbook is a central repository of data definitions that the University of Wisconsin is using for Business Intelligence. It will help users better understand the data in the UWBI OBIEE Tool dashboards, reports, and visualizations. Having one location to store UWBI’s data definitions, terminology, and specifications improves the understanding of existing reports and provides clear, agreed-upon terms for the creation of new ones through workflows.
WHO CAN USE IT?
- Data Cookbook’s current members include the UWBI Teams who have rights to login and view information within Data Cookbook.
- Eventually, all users will have access.
- There may be an authentication process depending on your institution's requirements.
- If you need assistance accessing Data Cookbook, please contact your institution UWBI Support Contact.
HOW TO LOG IN
Go to uwsa.datacookbook.com and enter your EPPN/UWBI Login and temporary password received in your data cookbook account creation email notification. You will need to follow the directions in the email and then go to preferences to change/update your password.
RESOURCES
You can find additional resources in the Resources tab of this website and also by contacting your designated UWBI Trainer. List of UWBI Trainers.
TRAINING
Institution-specific training can be found by contacting your institution's designated BI Trainer through your support contact.
ROLES
Who is a VIEWER?
A viewer can only view and comment on approved and in-progress objects. All UWBI Data Cookbook users will initially be assigned a viewer role in the authorized functional area. When assigned to definitions/specifications through a workflow as a reviewer/approver, you may be able to edit. When working in viewer permissions sensitive data may be restricted.
Who is an Editor?
Editors have the same rights as a viewer, as well as the ability to create new definitions and specifications, initiate a change in approved objects, and edit attributes not managed by version.
Who is a MANAGER?
Managers have the same rights as a viewer and editor, as well as the ability to perform all operations necessary to manage an approved definition/specification. This includes deleting, sharing with a Community, and changing the functional area assignment.
Who is an Administrator?
Administrators are those individuals charged with maintaining your Data Cookbook account. Their tasks and responsibilities include defining your site-specific codes and workflows. The UWBI Central Team acts as your administrators. If you would like to reach out to the system administrators, please contact your UWBI Support Contact.
Who can create a New Data System?
UWBI users with granted permissions for their Functional Area may create a new data system for an area. General users will not have the ability to do so and can only see existing data systems created by those with granted permissions. If you would like to request a new data system be added, please contact your UWBI Support Contact for further investigation.
Who is a Data Manager?
UW Systems and Institution employees who are considered Subject Matter Experts (SMEs). In Data Cookbook, the role of the Data Manager is to collaborate with the Data Steward in the creation, review, and approval process of definitions and specifications.
Who is a Data Steward?
UW Systems and Institution employees who ensure that accurate definitions and specifications in Data Cookbook are created and maintained.
Data Cookbook Definitions
Classification: Classification codes indicate the level of sensitivity of the data being described by Data Cookbook definitions. Example classification codes include Confidential Data, Sensitive Data, Internal Data, Unrestricted Data, and Public Data.
Data System: Data Systems are the Data Cookbook’s representation of these organizational systems. When users work with definitions and specifications in the Data Cookbook, knowing the systems that house or use these objects, including some technical information about them, helps them to better under the object’s purpose and use.
Definition: A single definition for each of your report’s elements so that there is no confusion about what is meant when someone refers to an approved definition.
Functional Area: Functional areas describe the organizational layers at your institution that manage or steward data. These areas often mirror offices, administrative groups, or other organizations at your institutions that will play a role in your defining and managing your data and reports.
Specification: Specification Types allow you to identify reporting deliverables based on the nature of the specific deliverable. Examples of specification types include reports, text files, database tables or views, and dashboards.
Workflow: Workflows control the process of approving, resolving, or responding to an object after it has been created.
