You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Qlik

Qlik (pronounced "click") Sense is a data analytics platform, hosted by the UW School of Medicine and Public Health. It allows users to interact with data through visualizations, filterable reports, and other formats. 

Institutional data will be made available through the SMPH Qlik platform, including data from campus, UWHealth, and additional SMPH-specific data sources. This will include HR, financial, facilities, and educational data. Research data will, at this time, be limited to research administration. 

Dashboards and reports will be created in Qlik Sense by SMPH IT, as well as by developers from other units within SMPH, giving groups the freedom to build to their own needs and specifications.


Qlik

Release Timeline

DateMilestones
Feb-May 2019

First developers added to Qlik Dev Environment

Building of baseline security groups

Building of baseline Qlik data sets (QVDs)

May 2019

Innaugural developer-to-developer demo

Testing of security roles in Qlik Test Environment

First Qlik apps moved into Qlik Test Environment

June 2019

Launch of twice-monthly Qlik Developer Open Labs

Testing of security roles in Qlik Production Environment

Summer 2019First Qlik apps promoted to Qlik Production Environment


FAQ

Who can log in to Qlik?



How do I get started as a developer?



What are the roles in Qlik?

The following roles exist:
  • Developer - The primary responsibility of the Developer is to create Apps and sheets for use by other Developers, Data Citizens, and End Users. In some cases this will require creation and loading of data objects such as QVDs (Qlik data files) for content development. 
  • Data Citizen - The data citizen has advanced user capabilities and in some instances may work very closely with Developers. They will have access to create new content off of base applications created by Developers.
  • Stream Admin - The Stream Admin is responsible for approval of the content that gets published to a group's Stream, and also for approving requests for new users to be added to their stream.
  • User/Tester - The User/Tester will have access to the Test environment to review Apps before they are deployed into production. This would usually include validating data and reviewing content for accuracy and effectiveness of visualizations.
  • End User - End Users will be allowed to view and interact with content published by the users that fall in the categories above.



DevTestProd
Developer
  • Able to Duplicate Sheets
  • Able to create new objects (tables, graphs, etc.)
  • Consume/explore data
  • Load Data
  • Develop Apps
  • Develop Base sheets
  • Develop community sheets
  • Able to Duplicate Sheets
  • Able to create new objects (tables, graphs, etc.)
  • Consume/explore data
  • Able to Duplicate Sheets
  • Able to create new objects (tables, graphs, etc.)
  • Consume/explore data
Data Citizen
  • Able to Duplicate Sheets
  • Able to create new objects (tables, graphs, etc.)
  • Consume/explore data
  • Able to Duplicate Sheets
  • Able to create new objects (tables, graphs, etc.)
  • Consume/explore data
Stream Admin
  • Gives approval for new devs to be added to stream
  • View apps and sheets as created by others
  • Change parameters on their own views as provided by developer of a given app
  • Gives approval for new user acceptance testers to be added to [regular/sensitive] stream
  • Able to promote personal sheets to be viewable to others.
  • Responsible for approval of content published to stream
  • Gives approval for new users or data citizens to be added to [regular/sensitive] stream
User/Tester
  • View apps and sheets as created by others
  • Change parameters on their own views as provided by developer of a given app
  • View apps and sheets as created by others
  • Change parameters on their own views as provided by developer of a given app
End User

  • View apps and sheets as created by others
  • Change parameters on their own views as provided by developer of a given app

Learn more about responsibilities Developers and Stream Admins have in getting an app to production


Learn More

  • No labels