Masterdata

The heart of MYDAS is the metadata, hereinafter referred to as master data. Knowing that master data is often exchanged by third-party systems via an API, we will explain the structure of the MYDAS master data, the use and navigation through the master data in this chapter.

We differentiate between the so-called control values, which are largely used to control MYDAS functions, and the work master data.

Examples of control values:

  • Order types
  • Break Categories
  • Price model etc

You can find these control values as an admin in the general settings under your user settings. These data are not part of this chapter. If you need instructions as an admin, please refer to the admin manual.

This chapter deals with the master data that you as a user deal with on a daily basis.

The supply-side master data

The offer in MYDAS can be compared with warehouses in a logistical sense. The media kind is the warehouse, a warehouse has several shelves that are usually divided according to content. That would be comparable to the medium. A shelf, in turn, is divided into shelf areas in the case of MYDAS, the advertising space or breaks.

Now you can combine different shelf areas into an offer, a selling option. These offers can be designed flexibly in MYDAS. And a catalog, in turn, has a price list.

In MYDAS this data are structured as follows:

The Media master data (1) is the basis for the offer. All the data required to define the offer are linked here.

The media kind(2) is the specification of the general offer. How the medium is to be treated in the system is specified here. Among other things, it is determined in the media kind, which filters are available for selection in the selling option.(7)

The media type (3) specifies from a technical point of view whether it is a linear or non-linear medium and how it is used in certain applications.

The break offer (linear media) is imported into MYDAS via the breakbuilder. (8)

Several media can be bundled together to form a Media Combi. (4)

Finally, price information is assigned to the medium. These can be rate cards or other models such as GRP deals. (5)

Demand Side Master Data

On the demand side master data, the customer side is mapped.

Client Level Master Data

Client Master Data

All demand or contract companies which are part of the booking process are clients in MYDAS. Depending on their role they are labeled as:

  1. Agency
  2. Advertiser
  3. Invoice Recipient

A client can have more than one role. A direct client can be all of these roles at once. 

Product/Brand:

The brand is the clients product or a service that is object of a campaign. In MYDAS, products can be aligned to a product tree (a hierarchy of industry, product group and product family) 

Material:

Material is in MYDAS as the meta data record for the file that will be broadcast as an advertising spot. 

Order Level Master Data

Order:

The Order folders keep all campaigns and sub-orders on one place. The order contains the information of advertiser, agency & invoice recipient.

Campaign:

The campaign is a concrete advertising/communication project that will be operated in MYDAS. A Campaign could have several Placements.

Operating Master Data/Booking Instructions

Sub-Order:

The Sub Order is only needed for the Media Type, linear. It collects all the spot bookings for a campaign on one place. You can compare it with a shopping cart.

Placement:

A placement maps the booking instructions for the optimizer (linear) or the adserver (non linear). The placement is something like a controller.

 

The entry point into the master data is always the master data table. In the section "Tables in MYDAS", you can read how to work effectively with tables.

Double-click on an entry to get to the details

Tab Structure

The master data is structured in so-called tabs. Ideally, all mandatory fields are shown in the first tab. You will find all other fields in the following tabs. The currently active tab is marked with an orange line.

A very useful feature is the so-called Navigation Path which you can find at the top of the screen. As you have already learned above, all master data is linked to each other. This concept ensures that you can access the associated master data from any point in the system.

The navigation path always shows you the path that you have taken in the system. You cannot get lost in the system. If you want to go back to the starting point, simply click on the corresponding entry in the navigation path and you will be directed back there.

Easy navigation through the master data:

You can go back step by step or skip all intermediate steps. just click on the point you want to be directed back to.

Special Actions

Depending on the type of master data, you will always find a few buttons at the bottom of the screen. These buttons trigger functions. We call them, Special Action Buttons. A special command is triggered by clicking on these buttons.

You can also display and execute the special actions in the master data table. That might save you a click or two. Find out here how to configure the table with the action buttons.

It may happen that you have to navigate between the master data within a master data area. You will find three buttons on the lower right edge of the screen for this.

  • Use the left arrow to jump back to the previous master data record
  • The right arrow takes you to the next master data record.
  • You can use the up arrow to get to the table view

The navigation is based on the currently tortured table view. When you have filtered data, the arrows will lead you back and forth, step by step. How to use the filters in the table view is explained here

UI Elements