Proventeq Migration Accelerator allows you to save time on your migration by defining the mappings to be used as defaults, using an Excel document and a Powershell script.

You'll find attached to this HowTo, two files, one is the Excel template you will need for defining the Content Type and Metadata mappings, and the other is the Powershell script which can be read directly by our product to create the default mappings. This saves the effort of configuring the mappings through UI.

The format also makes it easier to define metadata mappings which are common for all CT mappings – these can be defined only once with a ‘true’ in the ‘common’ column.

So, firstly, lets look at the format of the spreadsheet and what each column is used for. The ‘Format Description’ sheet also explains the purpose of each column if you would rather print for offline use. Some of the columns are not mandatory and the column names can be changed as the Powershell script takes them as a parameter.

• type

  What type of mapping you wish to use
  • Allowed values are:
    Metadata: This should be used when you need to directly map the target field to a source field
    Function: This should be used when a lookup into a CSV file is required or if you need to manipulate the source metadata e.g. concatenate two fields, substring, date formatting etc.
    Constant: If you need to set a constant value, such as always entering the same text into field, i.e. "Policydocument", "Financial reports", etc.

• common

  Specifies whether this mapping is common to ALL Content type mappings. For a mapping which is common, the source and target Content Type columns are ignored and can be left empty.

• src_ct_disp_name

  Source Content Type Display Name (e.g. ‘News Article’). This is optional and is used for generating the mapping name. 
  You can simply copy the values from src_ct_def_name column if you do not wish to specify values for this column.

• src_ct_def_name
  

  Source Content Type Internal Name (e.g. ‘NewsArticle’). This must contain the UCM Internal name.
  This is mandatory and is used for generating the mapping.

• tgt_ct_def_name

  Target Content Type Internal Name (e.g. ‘Article’). This must contain the internal name for CT
  This is mandatory and is used for generating the mapping.

• tgt_ct_disp_name

  Target Content Type Internal Name (e.g. ‘Article’). You can simply copy the values from the tgt_ct_def_name column if you do not wish to specify values for this column.
  This is mandatory and is used for generating the mapping.

• src_attr_disp_name
  

  Source metadata field Display Name (e.g. Title). You can simply copy the values from the tgt_attr_def_name column if you do not wish to specify values for this column.
  This is optional and is used for generating the mapping name. For example, in Oracle UCM, the Display name for internal field dDocTitle is ‘Title’.

• src_attr_def_name
  

  Source metadata field internal Name (e.g. dDocTitle). This must contain the UCM Internal name.
  This is mandatory and is used for generating the mapping name.

• tgt_attr_def_name
  

  Internal name for target field This must contain target internal name for the field.

• tgt_attr_disp_name

  Display name for target field. You can simply copy the values from gt_attr_def_name column if you do not wish to specify values for this column.

• const_val

  Required if the mapping ‘type’ is ‘Constant’. Specifies the constant value that will be set on the target field.

• func_name

  Required if the mapping ‘type’ is ‘Function’. Specifies the function that will be executed for computing the value for target field. Currently, specifying parameters to Function mappings though Excel is not supported, but we should be able to add another column and extend the Powershell to read the parameters from that Column.