Device Mappings

It is the responsibility of the licensee to set up and define these mappings.

In this page you can organize the supported devices for auto discovery purposes. This part of Metaflow is ALWAYS the responsibility of the licensee to set up and maintain as many publishers either mandate or give their device names a standard for all applications.

Discovery preferences is simply the highest level of discovering assets and should be viewed as a broad brush stroke approach which will help each project set achieve a 95% complete status straight from discovery (unless the device families are radically different for a project say between 2D and 3D applications).

Metaflow is able to discover projects through the use of understanding a standard device preferences spreadsheet, via a service known as Metaflow to Metaflow Exchange as well as discovery through setting up Discovery Preferences.

The former two methods are more akin to the aggregator and service provider marketplace who may be using Metaflow and have a need to discover many differently named files in the shortest space of time whilst remaining error free.

Within Metaflow the flow of this process is as follows:

There are two other ways of obtaining device mappings which are discussed later in the help.

• Metaflow to Metaflow exchange - where another Metaflow licensee has already set up a project with the correct mappings.
• Ingestion of a Metaflow standard device family spreadsheet.

Auto discovery uses the selected file naming policies chosen during discovery to auto detect the supported device for a discovered asset based on the actual file name of the asset discovered, as above the actual file names are controlled and programmed by the licensee. Managing the discovery device grouping is identical to the channel device mapping pages and is outlined in editing device mappings. The licensee is able to set up a group of devices for example Motorola Triplets or Series60 and then add the real individual devices which relate to that group to the group name. This simply means that if an asset is discovered with the group name of Motorola Triplets for example, then those assets MAY actually relate to a group of devices such as the Motorola V300, V525, V600 and so on when it comes to compatibilities and packaging outputs.

To manage Device Mappings you can perform the following:

Click the Preferences Menubar Item and select Discovery Preferences.

Click on the Discovery Device Mapping page in the left tree view in the metaflow category

In this page you can organize the supported devices for auto-discovery purposes.

Auto-discovery uses the file naming policies selected during discovery to auto-detect the supported device for a discovered asset based it's file name.

Selecting a group in the top pane displays the actual real devices in this group in the lower pane as shown below

You can highlight a group and add devices using the Add devices button.

If you highlight a device in the bottom pane you can also remove that device from the group or show the details of the device.

Device groups in the top pane can be organized hierarchically. To see the options to organize the groups right click in the device groups pane

Note: The device group hierarchy is purely for the user to better organize and locate groups and devices, it plays no other purpose during discovery