DeepSee End User Guide
Introduction to the User Portal
[Back] [Next]
   
Server:docs1
Instance:LATEST
User:UnknownUser
 
-
Go to:
Search:    

This chapter introduces the User Portal. It discusses the following topics:

Be sure to consult InterSystems Supported Platforms for information on system requirements for DeepSee.
Purpose of the User Portal
The User Portal is intended for direct use by end users (in contrast to such back end tools as Studio and the Management Portal). The User Portal is designed to enable you to do the following tasks:
Logging On to DeepSee
In a supported browser, go to the following URL:
http://localhost:57772/csp/samples/_DeepSee.UserPortal.Home.zen
Where localhost:57772 is the server and port used by the Caché web server and samples is the Caché namespace that you are using. When prompted, enter your Caché username and password.
Selecting a Preferred Language
This user interface can be displayed in different languages. Initially, the default preferred language (that is, the session language) is the language specified for the browser, or English if the browser language is not supported.
To select your preferred language, select About and then select an option in the list Preferred language for this session.
Note that after you select a language here, the system continues to use that language even if you change the language used by the browser.
Introduction to the User Portal
In the SAMPLES namespace, the User Portal looks like the following:
Notice the following elements in this page:
The User Portal is a shared environment. Many of the items you see are also visible to other users.
In the ENSDEMO namespace (in Ensemble installations), the User Portal displays a different set of sample dashboards. These dashboards display Ensemble business metrics but look like the other dashboards discussed in this book.
About Pivot Tables and Dashboards
Pivot tables are central to InterSystems DeepSee; they select and aggregate data. The following figure shows an example pivot table that shows the number of patients and the average allergy count per patient, grouped by age and gender.
Using this example as a reference, let us discuss the key terms in DeepSee:
The preceding example shows a preview of a pivot table within the Analyzer, which provides a large set of tools for modifying the pivot table, exporting to Microsoft Excel, toggling to a chart format, and so on.
You typically see a pivot table within a dashboard, as follows:
Notice that this dashboard includes multiple filters (shown in the Filters box), which you can use to filter the items on this dashboard.
Dashboards can include other kinds of elements, including meters and scorecards. A scorecard shows multiple rows of data in a tabular format that also includes features such as value-dependent lamps and arrows. For example:
A meter shows one or more values in graphical objects like the following:
The next chapter discusses dashboards in more detail; see Using Dashboards.”
Summary of Options in the User Portal
In the User Portal, you can do the following tasks, depending upon your permissions:
Except where noted, these topics are discussed in this book.
Security
DeepSee has a formal mechanism for managing access to DeepSee functionality, DeepSee items, and your data. This mechanism is based on the underlying Caché security framework. This section summarizes how this mechanism affects you.
For details, see the DeepSee Implementation Guide.
Security for Functionality
The User Portal and the Analyzer are secured as separate entities. You may or may not have read and write access to both these components. For example, you might have both read and write access for the User Portal (which would let you view and create dashboards), but only read access for the Analyzer (which would let you change a pivot table but not save the changes).
Security for Pivot Tables and Dashboards
Pivot tables, dashboards, and other items displayed in the User Portal are known as folder items and can be secured via Caché resources. This works as follows:
Security for Model Elements
DeepSee model elements can also be secured via Caché resources. This works as follows: