Metadata is the mapping needed for users to access and manipulate data. For consistency, everything that can possibly be included in the metadata should be included, so all users get the same view of the data. You want to avoid a situation where you may have two reports on the same data, generating different values, because the calculation was done in different ways.

The metadata can contain a wealth of information. Items which should be included in the metadata for WebFOCUS systems include:

• File Remark. Adding the optional file remark attribute provides descriptive information about the data source.
• Data Location. If the data is stored in an external dataset, it should be indicated in the metadata, so all users access the same file. The data may also be stored in databases, in which case the location is indicated in the Access File (ACX).
• Profile. If there are any dynamic attributes, they should be set in the MFD_PROFILE. This file is executed at every invocation of the metadata. Some common values that can be set include dataset, security, titles, expressions, and so on.
• File Commentary. Placing important information in comments at the beginning of the metadata allows administrators to understand the use of the files. Common information stored includes:
  • Use of the data (for example, where it is from, and how it is used).
  • Contact information (for example, who is responsible for the metadata and the data).
  • Inputs (for example, any parameters used for dynamic attributes).
• Field Names. Field names may indicate what the data represents. However, since the same field name may be used in multiple metadata, it is a good idea to add an indicator, as to the metadata source for the field. This may be a short prefix before each field (for example, fields in the SALES file all begin with SA_).
• Format. For display purposes, using format options to indicate comma-editing, currency symbols, decimal points, and decimal digits ensure everyone sees the data the same way.
• Title. Adding titles to the metadata allows all output to use the same column heading for any field. The facility also exists to allow titles to be stored in multiple languages, so only a single metadata is required for multiple countries.
• Field Description. Adding a description helps to explain the meaning of field names, especially though the GUI tools, where these descriptions can be displayed.
• Calculations (DEFINE/COMPUTE/FILTER). To ensure that all users use the same calculations, store them in the metadata, so they are available to all and consistent across use.

Metadata Location

• Metadata is stored on the WebFOCUS Reporting Server in Application Directories. Some customers choose to keep the Master Files and Access Files in the same Application Directory while others choose to keep them in separate Application Directories. WebFOCUS by default, will search for both Master Files and Access Files in the same directory. If they reside in separate Application Directories, then the following rule change must be issued in the global server profile or in the appropriate profile or procedure.

  APP SET METALOCATION_SAME OFF

  Note: The default value for METALOCATION_SAME is ON.

• Segregate Master Files, Access Files, and FOCEXECs by WebFOCUS applications and store them in separate Application Directories.
• Paths specified in the Master File DATASET attribute must exist on all environments to reduce the need for manual changes.

Describing the Data With Schemas

There are several types of schemas that can be used to describe the data, starting with the base schema.

Base Schema

• Core metadata attributes, such as DEFINEs and COMPUTEs, should be defined in the base schema.
• Cluster Views and Business Views that are based on the base schema will respect these attributes, eliminating the need to redefine them in the views.

Customizing Views for Business Requirements

• Mask selected fields, hide interrelationships from the end user. The Business View provides the flexibility to name fields in business terms that make sense to the business analyst.
• Hide fields that are not relevant or restricted.
• Fields can be described in the metadata that are for internal use and not exposed to any type of user using ACCESS_PROPERTY=INTERNAL.
• Respects attributes in the base schema, such as MFD_PROFILEs and DBA security rules.

Relating Base Schemas With Cluster Views

• Single metadata that encompasses multiple other metadata and their relationships.
• Avoid redundancy in that lookups are used as opposed to storing the lookup values with every dimension.
• The Cluster View is a pre-built view of the fact/dimension relationships.
• Respects attributes in the base schema, such as MFD_PROFILEs and DBA security rules.

Defining Column Hierarchies With Dimension Views

Use this when there is a hierarchical relationship (rollup/drill down) between the fields of the data (COUNTRY/STATE/CITY).