USER'S MANUAL

TABLE OF CONTENTS

1.Introduction ------------------------------------------------------------- 02
2.Tabs in MSM front end------------------------------------------------ 02
2.1 Meta Data Manager------------------------------------------------ 02
2.1.1 Client----------------------------------------------------- 02
2.1.2 Database------------------------------------------------- 04
2.1.3 Product Solution---------------------------------------- 05
2.1.4 Characteristic Manager--------------------------------- 07
2.1.5 Hierarchies----------------------------------------------- 13
2.1.6 Folders---------------------------------------------------- 17
2.1.7 Group Definition---------------------------------------- 21
2.1.8 Sorting---------------------------------------------------- 22
2.1.9 Lowest Dimensional Level---------------------------- 23
2.2Source Orchestration----------------------------------------------- 25
2.2.1 Data Model Definition-------------------------------- 25
2.2.2 Distribution Key Definition-------------------------- 26
2.2.3 Input Configuration----------------------------------- 26
2.2.4 Output Configuration--------------------------------- 28
2.3 Dimension Manager---------------------------------------------- 29
2.3.1 Dimension--------------------------------------------- 29
2.3.2 Dimension Editor------------------------------------- 30
2.3.3 Dimension Editor Configuration------------------- 31
2.3.4 Dimension Content---------------------------------- 32
2.4 EQ Analyzer------------------------------------------------------ 33
2.4.1 EQ Analyzer------------------------------------------ 33

1
 Metadata Security Manager - User Guide
1.Introduction

MSM is an application which was developed to simplify the Answers On-Demand's

dimension sourcing process into an application and add security features to it. It is the
heart and brain of AOD.

2.Tabs in MSM Front end

2.1Metadata Manager

2.1.1Client

The Client tab displays all the Client name, Description and Client ID in columns. We
can perform different actions here like Create, Edit and Delete the Client information.

Scr 1 : Metadata Manager → Client

2
In the Client Editor, for a particular Client the available database groups can be assigned
to them and saved.

Similarly the Clients can be created with new ID, description and database groups. There
is also an option for deleting the existing Clients.

Scr 2 : Metadata Manager → Client → Action → Edit

3
2.1.2Database

In the database tab, new databases can be created. The database contents can be defined
here, for eg the database name, description, database type, delivery cycle, etc. If it is a
database group, the Group Indicator check box should be enabled else it will be
considered as an individual database.

New databases can be added and saved in this screen. Content attributes and content
types will contain the additional technical details of the databases. All the details in the
rows are editable here.

Scr 3 : Metadata → Database → Content

4
 2.1.3Product Solution

Product Solution is generally for Scan. This tab contains the Product Solution,
Description and code in the columns. It can perform actions like create, edit and delete.

Scr 4 : Metadata Manager → Product Solution

5
In the Product Solution Editor, for a particular Client the available database groups can
be assigned to them and saved.

Similarly the Definitions can be created with Product Solution, Description and code.
There is also an option for deleting the existing Clients.

Scr 5 : Metadata Manager → Product Solution → Action → Edit

6
2.1.4Characteristic Manager

•Characteristic Creation

The characteristics are created in this tab. Generally they are referred to as Custom-
System characteristics. We have to select the base dimension, Client and the database,
after which the corresponding characteristics will be populated in the columns.

The characteristic name, characteristic abbreviation, description and its type are shown
as columns. These listed characteristics can be edited or deleted. A new characteristic
can also be added and saved.

Scr 6 : Characteristic manager → Dimension → Client → Database

7
•Concatenation

This option is used to combine two or more separate characteristics into a single
characteristic according to the requirement of the client.

For example, for product dimension, UPC ID and UPC Description are two separate
characteristics in the input file, but a client can have a requirement to deliver these two
as a single characteristic.
Scr 7 : Characteristic manager → Concatenation

8
•Value Definition

This tab enables us to define the values for the Custom characteristics. New values can
be added here and saved. Deletion of the existing characteristics is also possible.

Scr 8 : Characteristic manager → Value Definition

•Delivery

Used to deliver the characteristics to database groups. Any changes to characteristic

delivery can be made any time and will be reflected in the next dimension build. Any
changes to characteristic delivery should come as an updated order form from the client

9
 Moving characteristics to the Assigned Characteristic list box for a database group
means the Assigned Characteristics should be part of the dimension build for the
selected database group

Scr 9 : Characteristic manager → Delivery

•Order

This tab is useful in sorting the order of the characteristics in the final dimension build.
Sorting can be done either with in ascending or descending order with the alpha-numeric
type of sorting.

10
Scr 10 : Characteristic manager → Order

•Technical

Only the technical details of the characteristics are defined here. For eg characteristic
type,size,precision,etc.

Scr 11 : Characteristic manager → Technical Only

11
2.1.5Hierarchies

Hierarchies decide in which order the characteristics are placed for a dimension.

•Hierarchy

We can edit the hierarchy name, description, sequence and also the order in which the
characteristics should be arranged.

Scr 12 : Hierarchies → Hierarchy

12
•Hierarchy Order

The order in which the characteristics are displayed can be defined here

Scr 13 : Hierarchies → Hierarchy Order

13
•Hierarchy Display

The display can be modified here

Scr 14 : Hierarchies → Hierarchy Display

14
•Logical Definition

The logical dimensions are selected and defined here.

Scr 15 : Hierarchies → Logical Definition

15
2.1.6Folders

Folders allow you to group dimension items in a particular way. Ideally, folders are for
fact and period dimensions. There are typically many groupings for fact and period.
•Folder
The main purpose of folders is to group items that may not have a functional logical
grouping. Hierarchy will tell you all “categories” that will appear in the data selector
whereas folders will tell you all of the values for a characteristic and characteristic value
(items).

16
Scr 16 : Folders → Folder

•Folder display
If the characteristics that were used in the definition of your folder were delivered
and were modified such that they are now no longer delivered, you will NOT be
automatically notified of this. As a result, you will need to be notified of this change in
another avenue and modify your folders as such.

Scr 17 : Folders → Folder display

17
•Logical definition

The logical dimensions are selected and defined here.

Scr 18: Folders → Logical definition

18
•Preview
When the sub-folder definition is complete, click on ‘Save Sub Folder’
· Upon doing so, you will receive a message if your sub folder was saved
successfully.
· Click on OK.
·You will now see the folder that you created in the grid as well as in the
navigation panel.

Scr 19 : Folders → Preview

19
2.1.7Group Definitions

Content defined for this Database Group will be same for all the Databases
mapped/available for the particular Database Group.

Click on the Database Group created in the right drop down box -> the Databases
available will be displayed in the bottom left drop down box. Select the databases to be
mapped and click on the Right arrow to move the Databases to the Include in Group
Drop Down box -> Click Save.

20
2.1.8Sorting

Defines how the characteristics should be displayed in the data selector

Scr 20 : Sorting

2.1.9Lowest Dimensional Level

We can define the lowest dimensional level for a particular characteristic

Scr 21 : low dimensional level

21
22
2.2 Source Orchestration

2.2.1Data Model Definition

This tab has the data model name, description, and checks if it is defined or not. It
validates the data model. A new data model can be created, edited and deleted.
In mapping, the characteristics are assigned to the data model for a particular dimension

Scr 22 : Source Orchestration → Data Model Definition

23
2.2.2Distribution Key Definition

Here we have each of the data model will have the Base dimension and the distribution
key. Then the distribution key can be edited with a different name and description.
Available characteristics are assigned to that specific distribution key.

Scr 22 : Source Orchestration → Distribution Key Definition

2.2.3Input Configuration

The input configuration screen is used to configure input files and consists of data/meta
data from external and/or internal sources that are needed to process a dimension.

Internal Data Sources

24
 o ESPEC
o Client Totals
o Nielsen’s Product Feed
o Market Production
o Etc.
External Data Sources
o Dimension files from clients or any other sources.

Scr 23 : Source Orchestration → Input Configuration

2.2.4Output Configuration

25
Once all the meta data configurations are done, output configuration is where you create
a build instruction to dimension sourcing by dimension. You can have multiple database
groups assigned to a build instruction. Once a build instruction is provided to dimension
sourcing, a staging table (roll up or master) will be created for the dimension which will
have the combined data content of all database groups assigned to the build instruction.

Scr 24 : Source Orchestration → Output Configuration

26
2.3 Dimension Manager

2.3.1Dimension

It is used for creating a dimension and also maintaining the Client to the database
mapping. The dimensions can be created, edited and deleted based on the database
selections made. The base dimensions and the logical dimensions are edited and then
their respective ids are generated and displayed.

Scr 25 : Dimension Manager → Dimension

2.3.2Dimension Editor
27
Custom characteristics and values defined via MSM do not have relation ship to the
item, so to relate it to dimensional item, we use dimension editor screen.

Scr 26 : Dimension Manager → Dimension Editor

2.3.3Dimension Editor Configuration

For a particular dimension, the column header, column width, display sequence, etc can
be edited here.

Scr 27 : Dimension Manager → Dimension Editor Configuration

28
2.3.4Dimension Content
Content defined for this Database Group will be same for all the Databases
mapped/available for the particular Database Group.
Click on the Database Group created in the right drop down box -> the Databases
available will be displayed in the bottom left drop down box. Select the databases to be
mapped and click on the Right arrow to move the Databases to the Include in Group
Drop Down box -> Click Save.

Scr 27 : Dimension Manager → Dimension Content

29
 2.4 EQ Analyzer

EQ Summary:

This tab allow us to view the EQ that has been assigned to the client. EQ is only
applied for the PRODUCT dimension. By selecting a client, if EQ has been assigned to
the client chosen, the details will populate in the grid below. If EQ has not been assigned
to the client selected, you will be able to create EQ for that client. Based on client
selection, all available EQ will populate in the grid.

Scr 28: EQ Analyzer → EQ Summary

30
 EQ Definition:

We can assign a EQ for a particular client and characteristic. We can also assign a
database for a particular EQ.

Scr 29: EQ Analyzer → EQ Definition

31
 EQ Factor Definition:

In the EQ Factor Definition screen, you will input manually or through an import,
your Conversion Factors as well as select the indicator for units and EQ Value
Restriction.

Scr 30: EQ Analyzer → EQ Factor Definition

32
33