Understand the CSV mapping file

A CSV mapping file is created when you run the map command. The CSV mapping file captures your eDNA point configuration data. This file is used as input during the migration operation to define which eDNA points’ data to migrate to the PI System. It is also used to configure any manual point type and quality information the user wants to make between the source eDNA point data and the migrated PI tag data.

Important: When migrating large numbers of multistate tags in eDNA, additional processing to the mapping file may be required to consolidate empty or unused states. Data Archive allows 16,385 possible digital state sets. Multistate points in eDNA provide 18 states including undefined states. You can manually edit the mapping file or use a script to remove undefined or empty states. Additionally, you can also consolidate sets with the same name-enumeration pairs into a single digital state set.

By default, the CSV mapping file contains the following columns:

• Selected(x): PI Builder uses this field to determine if the tag will be created. Set this field to x if you want a PI tag created for the corresponding eDNA point.

  Note: The Selected(x) column is also used as input during the migration operation. The CSV mapping file is passed as input during the migration and will only migrate data for eDNA points that have an "x" in the Selected(x) column.

• eDNA Point: The name of the eDNA point

• eDNA Field: The source field of the eDNA point data. This field will be either Value or Status.

• Name: The name of the target PI tag to be created. If no prefix is specified, the target PI tag name will be identical to the eDNA point name.

• ObjectType: The object type being sent by PI Builder. This should always be set to PIPoint. In most cases, this will be set to PIPoint, but for migrating multi-state eDNA data, it can be set to DigitalState or DigitalStateSet. These values should not be modified between map and migrate options.

• PointType: The point type of the PI tag to be created. The eDNA and PI tag types will match, unless the eDNA data type is not supported by PI.

  Note: The PointType values generated by the mapping file are recommendations from the application, based on the source eDNA point type. Prior to using the mapping file to generate the PI tags on the target PI System, the user can replace the recommended PointType and replace it with another legal PI tag point type if they choose, and the migration utility will make its best effort to form the eDNA point values into that tag during migration.

• PointSource: The PointSource used for creating the PI tag.

• PtClassName: The PI point class used for generating the PI tag. The Classic PI tag class is always assigned.

There can also be additional columns, if the migration utility reads multi-state information from eDNA points, which the application will attempt to store in digital PI tags:

• DigitalSet: Indicates a name for a PI digital state set

• Parent: Indicates the parent PI tag that the digital state set uses.

• EnumerationValue: Stores the various values of the digital state set.

  Note: You can configure compression settings in bulk via the CSV file during tag creation and editing. You will need to add the Compressing column header to the CVS file and then set the value in this column to '1' in PI Builder. The Compressing column header indicates if data is to be compressed for a PI tag. A value of '1' indicates that compression is turned on and a value of '0' indicates that it is not. See Set column headers in a worksheet and Compression guidelines.