5.6.2 - Metadata Mapping

Follow

Please select from the Source system from the options below, for source specific information.

 

Meridio Source

There are five types of metadata mappings:

  • Target Metadata to Source Metadata
  • Target Metadata to Constant
  • Target Metadata to Custom Script
    • Iron Python Script and
    • Power Shell Script
  • Target Metadata to built-in Function

 

Target Metadata to Source Metadata:

Selecting the ‘Mapping Type’ as ‘Metadata’, displays all the available source metadata in the drop down, one of which can be used for mapping.

 

Note: Choosing incompatible metadata value may lead to load-failure.

 

5.6.2.1.  Metadata Mapping for Meridio

FIGURE_30_-__METADATA_MAPPING_FOR__MERIDIO.png

 

Target Metadata

Mapping Type

Metadata Value

Name

Script

$MigrationItem.SI.ItemName

Title

Metadata

Title

Document Created By

Function

GetMappedUser{srcMetaValue}

Document Modified By

Function

LastModifiedByUserName

Created

Metadata

CreateDate

Modified

Metadata

LastModificationDate

 

Target Metadata to Constant Value:

If Constant mapping type is selected, user is given an option to specifiy a constant value that will be set in the target metadata.


FIGURE_31_-__CONSTANT_MAPPING.png

 

Target Metadata to Runtime Script:

This option is for advanced users. You can either write IRON Python scripts or PowerShell scripts which will be executed during transformation. Typically, the scripts will modify the value in source metadata fields, which can be passed as inputs to the scripts using variable names provided in the drop down.

 

FIGURE_32_-__POWERSHELL_SCRIPT__MAPPING.png

 

Target Metadata to Function:

This option is for advanced users. If Function mapping type is selected, user can add inbuilt Functions or Create his/her own custom function. For example: Also you need to import a user mapping using a csv file from the User Mappings screen. Refer User Mappings for more detail.

FIGURE_33_-__SELECT_FUNCTION__SCREEN.png

 

Add Function

Besides the built-in functions, the user can create own set of functions based on requirements. To Create New Function user needs to provide Function Language, Group (Optional), Name, Description (Optional), List of Parameters and respective Script for selected language.


FIGURE_34_-__ADD_NEW_FUNCTION__SCREEN.png

 

Edit Function

User can edit the properties of the function in the Edit Functions Dialog. The image below shows how this Dialog looks like.


FIGURE_35_-__EDIT_FUNCTION__SCREEN.png

 

View Function

User can view the properties of the function in the view Functions Dialog. The image below shows how this Dialog looks like.


FIGURE_36_-__VIEW_FUNCTION__SCREEN.png

 

Test Function

User can test the script of the function in the evaluation Functions Dialog. The image below shows how this Dialog looks like.


FIGURE_37_-__TEST_FUNCTION__SCREEN.png

 

Delete an existing Function

User can delete the function. The image below shows how this Dialog looks like.


FIGURE_38_-__DELETE_FUNCTION__SCREEN.png

 

Note: Please be careful when Deleting functions.

 

 

Fileshare Source

There are five types of metadata mappings:

  • Target Metadata to Source Metadata
  • Target Metadata to Constant
  • Target Metadata to Custom Script
    • Iron Python Script and
    • Power Shell Script
  • Target Metadata to built-in Function

 

Target Metadata to Source Metadata:

Selecting the ‘Mapping Type’ as ‘Metadata’, displays all the available source metadata in the drop down, one of which can be used for mapping.

 

Note: Choosing incompatible metadata value may lead to load-failure.

 

Metadata Mapping

FIGURE_27_-_METADATA_MAPPING.png

 

Target Metadata

Mapping Type

Metadata Value

Name

Script

$MigrationItem.SI.ItemName

Title

Metadata

Title

Document Created By

Function

GetMappedUser{srcMetaValue}

Document Modified By

Function

LastModifiedByUserName

Created

Metadata

CreateDate

Modified

Metadata

LastModificationDate

 

Target Metadata to Constant Value:

If Constant mapping type is selected, user is given an option to specifiy a constant value that will be set in the target metadata.


FIGURE_31_-__CONSTANT_MAPPING.png

 

Target Metadata to Runtime Script:

This option is for advanced users. You can either write IRON Python scripts or PowerShell scripts which will be executed during transformation. Typically, the scripts will modify the value in source metadata fields, which can be passed as inputs to the scripts using variable names provided in the drop down.

PowerShell:

FIGURE_32_-__POWERSHELL_SCRIPT__MAPPING.png

 

IronPython:

FIGURE_29_-_IRON_PYTHON_SCRIPT_MAPPING.png

 

Target Metadata to Function:

This option is for advanced users. If Function mapping type is selected, a user can add inbuilt Functions or Create their own custom function. For example: Also you need to import a user mapping using a csv file from the User Mappings screen. Refer to User Mappings for more detail.

FIGURE_31_-_SELECT_FUNCTION_SCREEN.png

 

Add Function

Besides the built-in functions, the user can create own set of functions based on requirements. To Create New Function user needs to provide Function Language, Group (Optional), Name, Description (Optional), List of Parameters and respective Script for selected language.


FIGURE_34_-__ADD_NEW_FUNCTION__SCREEN.png

 

Edit Function

User can edit the properties of the function in the Edit Functions Dialog. The image below shows how this Dialog looks like.


FIGURE_33_-_EDIT_FUNCTION.png

 

View Function

User can view the properties of the function in the view Functions Dialog. The image below shows how this Dialog looks like.


FIGURE_34_-_VIEW_FUNCTION_SCREEN.png

 

Test Function

User can test the script of the function in the evaluation Functions Dialog. The image below shows how this Dialog looks like.


FIGURE_37_-__TEST_FUNCTION__SCREEN.png

 

Delete an existing Function

User can delete the function. The image below shows how this Dialog looks like.

Note: Please be careful when Deleting functions.


FIGURE_38_-__DELETE_FUNCTION__SCREEN.png

 

Oracle UCM Source

There are five types of metadata mappings:

  • Target Metadata to Source Metadata
  • Target Metadata to Constant
  • Target Metadata to Custom Script
    • Iron Python Script and
    • Power Shell Script
  • Target Metadata to built-in Function

 

Target Metadata to Source Metadata:

Selecting the ‘Mapping Type’ as ‘Metadata’, displays all the available source metadata in the drop down, one of which can be used for mapping.

 

Note: Choosing incompatible metadata value may lead to load-failure.

 

Metadata Mapping

FIGURE_18_-__METADATA_MAPPING.png

 

Target Metadata

Mapping Type

Metadata Value

Name

Script

$MigrationItem.SI.ItemName

Title

Metadata

Title

Created

Metadata

CreateDate

Modified

Metadata

LastModificationDate

 

Target Metadata to Constant Value:

If Constant mapping type is selected, user is given an option to specifiy a constant value that will be set in the target metadata.


FIGURE_31_-__CONSTANT_MAPPING.png

 

Target Metadata to Runtime Script:

This option is for advanced users. You can either write IRON Python scripts or PowerShell scripts which will be executed during transformation. Typically, the scripts will modify the value in source metadata fields, which can be passed as inputs to the scripts using variable names provided in the drop down.

PowerShell:

FIGURE_32_-__POWERSHELL_SCRIPT__MAPPING.png

 

IronPython:

FIGURE_29_-_IRON_PYTHON_SCRIPT_MAPPING.png

 

Target Metadata to Function:

This option is for advanced users. If Function mapping type is selected, a user can add inbuilt Functions or Create their own custom function. For example: Also you need to import a user mapping using a csv file from the User Mappings screen. Refer to User Mappings for more detail.

FIGURE_31_-_SELECT_FUNCTION_SCREEN.png

 

Add Function

Besides the built-in functions, the user can create own set of functions based on requirements. To Create New Function user needs to provide Function Language, Group (Optional), Name, Description (Optional), List of Parameters and respective Script for selected language.


FIGURE_34_-__ADD_NEW_FUNCTION__SCREEN.png

 

Edit Function

User can edit the properties of the function in the Edit Functions Dialog. The image below shows how this Dialog looks like.


FIGURE_33_-_EDIT_FUNCTION.png

 

View Function

User can view the properties of the function in the view Functions Dialog. The image below shows how this Dialog looks like.


FIGURE_34_-_VIEW_FUNCTION_SCREEN.png

 

Test Function

User can test the script of the function in the evaluation Functions Dialog. The image below shows how this Dialog looks like.


FIGURE_37_-__TEST_FUNCTION__SCREEN.png

 

Delete an existing Function

User can delete the function. The image below shows how this Dialog looks like.

Note: Please be careful when Deleting functions.


FIGURE_38_-__DELETE_FUNCTION__SCREEN.png

 

 

 

Was this article helpful?
0 out of 0 found this helpful

Comments