5.5.6 - File and Folder Settings
Please select below for the details for your source system.
Meridio Source
The File and Folder settings are used to configure structure hierarchy of items that will be loaded to the target.
You can proceed with the default settings from this window or import a structured mapping CSV file.
Create a new Structured Hierarchy using Import Mappings
Structured Mapping or Import Mappings is an extensive feature used to create a new hierarchy on target which may or may not follow the source hierarchy. Here you can load child items/folders at an entirely different new location specified by you. Also, if child items structure mapping is not present / given by you then they will inherit the mapping of the parent.
This feature is not mandatory for migrating content from source to target. In this case, you can map Source Container to a Document Library or folder directly.
To import a Structure mapping CSV, you need to create a comma delimited CSV file with following columns as header:
- SourcePathId - Source Path Value will be DocID
- SourcePathType - Blank
- SourcePath – Source URI Path/Blank
- SourceTaxanomy - Blank
- TargetPathId - Blank
- TargetPathType - Blank
- TargetPath - Blank
- TargetSite – Site Name (System Name or Name in URL)
- TargetSiteSettings – Blank
- TargetLibrary – Library Name (System Name or Name in URL)
- TargetLibrarySettings – Blank
- TargetFolder – Path of the folder hierarchy under which item will be
- TargetFolderSettings - Blank
- TargetPathMetadata - Blank
- TargetTaxonomy - Blank
- TaxonomyMappingType - Blank
- PathMappingType - Blank
- MappingSettings – Specify either “Create” or “Merge” for source item loading option
PMA supports different type of structure mapping to facilitate your requirements, such as maintaining source hierarchy or to recreate target hierarchy.
- Based on URI (Default Settings)
- Based on DocID
- Based on Metadata Expressions
You can select the structure mapping type from drop-down menu:
Below is a sample Structure Mapping:
Please find sample structure mapping files at this location:
[Installation directory] \Proventeq\Proventeq Migration Accelerator\SampleFiles
Create file with Unique Name
In the source system, we could have documents with a duplicate name within the same container (E.g. Folder). So, while migrating such documents, PMA supports a feature to create unique document name by appending auto incremental numbers to their names.
In order to use this feature, you need to select an option ‘Create a new file with unique name’ in the File and Folder Settings tab.
E.g. If we have a total of 3 files with the same name as “XYZ.pdf” then PMA will create unique names for them like below:
- XYZ.pdf
- XYZ (1).pdf
- XYZ (2).pdf
Oracle UCM Source
Recreate Source Hierarchy
The File and Folder settings are used to configure structure hierarchy of items that will be loaded to the target.
You can proceed with the default settings from this window or import a structured mapping CSV file.
Create a new Structured Hierarchy using Import Mappings
Structured Mapping or Import Mappings is an extensive feature used to create a new hierarchy on the target which may or may not follow the source hierarchy. Here you can load child items/folders at an entirely different new location specified by you. Also, if child items structure mapping is not present / given by you, then they will inherit the mapping of the parent.
This feature is not mandatory for migrating content from source to target. In this case, you can map the Source Container to a Document Library or folder directly.
To import a Structure mapping CSV, you need to create a comma delimited CSV file with following columns as header:
- SourcePathId – Source content or collection Id in Oracle UCM. For site it will be Site Id or Name E.g. Proventeq. For file content it will be Content ID E.g. PROV_032903 and for folder/collection it will be a Collection ID E.g. 609002818. For Content Type it will be fixed value -11111, since it is a virtual root considered for migrating all documents of that content type.
- SourcePathType - Blank
- SourcePath – Blank
- SourceTaxanomy - Blank
- TargetPathId - Blank
- TargetPathType - Blank
- TargetPath - Blank
- TargetSite – Site Name (displayed in URL)
- TargetSiteSettings – Blank
- TargetLibrary – Display Name (displayed on UI)
- TargetLibrarySettings – Blank
- TargetFolder – Path of the folder hierarchy under which item will be
- TargetFolderSettings - Blank
- TargetPathMetadata - Blank
- TargetTaxonomy - Blank
- TaxonomyMappingType - Blank
- PathMappingType - Blank
- MappingSettings – Specify either “Create” or “Merge” for source item loading option.
- CreateHierarchyIfNotExists –
- Set to “TRUE” to create the specified TargetSite/TargetLibrary/TargetFolder on target if they do not exist
- Set to “FALSE” so that item will fail if specified path does not exist
Below is a sample Structure Mapping:
Note that it is mandatory to select document library in “Content Type Mapping Settings” for relevant content mapping. Ideally, we should select the document library name as “Based on Structure Mappings”, if we have specified the library name in structure mapping file for relevant documents. Otherwise, you can select the specific document library in the target site collection for relevant content mapping and then you can skip to mention the same in the structure mapping file for relevant documents.
Comments