Page History
| Anchor | ||||
|---|---|---|---|---|
|
| Table of Contents | ||
|---|---|---|
|
Overview
| Styleclass | ||
|---|---|---|
| ||
...
Skill/Knowledge | Description |
|---|---|
Ability to analyse user needs | The view administrator must have the skills to conduct user needs analyses to create categories and fields that are relevant to the user vocabulary, and to develop views that meet the needs of the user community. |
Database knowledge | A View administrator needs to have a good working knowledge of the company's company’s database management system (DBMS), how the databases are deployed, the logical database structure, and the type of data stored in company databases. |
Structured Query Language (SQL) | A working knowledge of SQL is necessary. |
View Components
| Styleclass | ||
|---|---|---|
| ||
The purpose of field categories is to provide logical groupings of fields within a view. The name of a category should intuitive to the business user and provide an indication of the fields that it is likely to contain. | |
A field is a named component that maps to data or a derivation of data in the database. The name of a field should be drawn from the business vocabulary of the targeted user group. |
...
| Dimension fields retrieve the data that will provide the basis for analysis in a report. Dimensions typically retrieve character-type data (employee names, company names, etc.), or dates (years, quarters, etc.) |
| Metric fields retrieve numeric data that is the result of calculations on data in the database. |
| View Geography Fields are fields linked to a GeoPack. |
| Pre-Defined Filters are fields where a set of conditions have been set up when the view was created. This assists users to limit the data returned in a query to only the expected results. For example if the filter is called 'United States' ‘United States’ then only data from the united states would be included in the results. |
| Parameters are fields which are used to capture user defined values and pass them into calculated fields or filters. These parameters can assist in conducting what if analysis. |
| View Filter Groups are sets fields to be used as filters, reused multiple times. Filter Groups can contain filter dependency hierarchies, as well as cached values. These only have to be set up once, rather than for each report. |
View Use
| Styleclass | ||
|---|---|---|
| ||
...
Yellowfin report writers use views for reporting and analysis. The view should provide them with categories and fields relevant to their business domain.
View Design
| Styleclass | ||
|---|---|---|
| ||
...
Development phase | Description |
|---|---|
Prepare | Identify the target data source and become familiar with its structure. |
Analyse | Identify what information the users need. Identify what standard reports they require. |
Implement | Build the view either on the database or through the Yellowfin view builder. |
Test | Form a small group of users, preferably power users who have some knowledge of what information they expect to get from the view. |
Deploy | Migrate the view from your Test to Production environments. |
Evolve | Update and maintain the view as the data sources and user requirements change and grow. |
Note: View design should always be driven primarily by user requirements and NOT the data source structure.
| horizontalrule |
|---|
| Styleclass | ||
|---|---|---|
| ||