5.6.6 - File and Folder Settings

Follow

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 target.

User can proceed with the default settings from this window or import structured mapping CSV file.

FIGURE_51_-__RECREATE_SOURCE__HIERARCHY.png

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.

Note: Import structure mapping is mandatory for a target container which is mapped at the site-collection or site level.

This feature is although not mandatory for migrating content from source to target. In this case user can map source container to a Document library or folder directly.


FIGURE_52_-__IMPORT_MAPPINGS.png

To import a Structure mapping csv, you need to create a comma delimited CSV file with following columns as header:

  1. SourcePathId - Source Path Value will be DocID
  2. SourcePathType - Blank
  3. SourcePath – Source URI Path/Blank
  4. SourceTaxanomy - Blank
  5. TargetPathId - Blank
  6. TargetPathType - Blank
  7. TargetPath - Blank
  8. TargetSite – Site Name (System Name or Name in URL)
  9. TargetSiteSettings – Blank
  10. TargetLibrary – Library Name (System Name or Name in URL)
  11. TargetLibrarySettings – Blank
  12. TargetFolder – Path of the folder hierarchy under which item will be
  13. TargetFolderSettings - Blank
  14. TargetPathMetadata - Blank
  15. TargetTaxonomy - Blank
  16. TaxonomyMappingType - Blank
  17. PathMappingType - Blank
  18. MappingSettings – Specify either “Create” or “Merge” for source item loading option

 

PMA supports different type of structure mapping to facilitate user requirements such as maintaining source hierarchy or to recreate target hierarchy.

  1. Based on URI (Default Settings)
  2. Based on DocID
  3. Based on Metadata Expressions

FIGURE_53_-__DIFFERENT_STRUCTURE_MAPPING__OPTION.png

 

User can select the structure mapping type from dropdown list based on his requirements

Below is a sample Structure Mapping:

Please find sample structure mapping files on below location:

[Installation directory] \Proventeq\Proventeq Migration Accelerator\SampleFiles

FIGURE_54_-__SAMPLE_STRUCTURE_MAPPING_FILE_USING___URI.jpg


FIGURE_55_-__SAMPLE_STRUCTURE_MAPPING_FILE_USING___DOCID.png

Create file with Unique  Name

In source system, we could have documents with duplicate name within 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, user need to select an option ‘Create a new file with unique name’ in File and Folder Settings tab.


FIGURE_56_-__FILE_AND_FOLDER_SETTINGS__CREATE_A__NEW_FILE_WITH_UNIQUE____NAME.png

E.g If we have total 3 files with same name as “XYZ.pdf” then PMA will create unique names for them like below:

  • XYZ.pdf
  • XYZ (1).pdf
  • XYZ (2).pdf

 

 

Fileshare Source

The File and Folder settings are used to configure structure hierarchy of items that will be loaded to target.

User can proceed with the default settings from this window or import structured mapping CSV file.

FIGURE_51_-__RECREATE_SOURCE__HIERARCHY.png

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.

Note: Import structure mapping is mandatory for a target container which is mapped at the site-collection or site level.

This feature is although not mandatory for migrating content from source to target. In this case user can map source container to a Document library or folder directly.


FIGURE_52_-__IMPORT_MAPPINGS.png

To import a Structure mapping csv, you need to create a comma delimited CSV file with following columns as header:

  1. SourcePathId - Source Path Value will be DocID
  2. SourcePathType - Blank
  3. SourcePath – Source URI Path/Blank
  4. SourceTaxanomy - Blank
  5. TargetPathId - Blank
  6. TargetPathType - Blank
  7. TargetPath - Blank
  8. TargetSite – Site Name (System Name or Name in URL)
  9. TargetSiteSettings – Blank
  10. TargetLibrary – Library Name (System Name or Name in URL)
  11. TargetLibrarySettings – Blank
  12. TargetFolder – Path of the folder hierarchy under which item will be
  13. TargetFolderSettings - Blank
  14. TargetPathMetadata - Blank
  15. TargetTaxonomy - Blank
  16. TaxonomyMappingType - Blank
  17. PathMappingType - Blank
  18. MappingSettings – Specify either “Create” or “Merge” for source item loading option

PMA supports different type of structure mapping to facilitate user requirements such as maintaining source hierarchy or to recreate target hierarchy.

  1. Based on URI (Default Settings)
  2. Based on DocID
  3. Based on Metadata Expressions

FIGURE_53_-__DIFFERENT_STRUCTURE_MAPPING__OPTION.png

 

User can select the structure mapping type from dropdown list based on his requirements

Below is a sample Structure Mapping:

Please find sample structure mapping files on below location:

[Installation directory] \Proventeq\Proventeq Migration Accelerator\SampleFiles

FIGURE_54_-__SAMPLE_STRUCTURE_MAPPING_FILE_USING___URI.jpg


FIGURE_55_-__SAMPLE_STRUCTURE_MAPPING_FILE_USING___DOCID.png

Create file with Unique Name

In source system, we could have documents with duplicate name within 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, user need to select an option ‘Create a new file with unique name’ in File and Folder Settings tab.


FIGURE_56_-__FILE_AND_FOLDER_SETTINGS__CREATE_A__NEW_FILE_WITH_UNIQUE____NAME.png

E.g If we have total 3 files with 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 target.
User can proceed with the default settings from this window or import structured mapping csv file.

FIGURE_38_-__RECREATE_SOURCE__HIERARCHY.png

 

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.

Note: Import structure mapping is mandatory for a target container which is mapped at the site-collection or site level.

This feature is although not mandatory for migrating content from source to target. In this case user can map source container to a Document library or folder directly.

FIGURE_39_-__IMPORT_MAPPINGS.png

To import a Structure mapping csv, you need to create a comma delimited CSV file with following columns as header:

  1. 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.
  2. SourcePathType - Blank
  3. SourcePath – Blank
  4. SourceTaxanomy - Blank
  5. TargetPathId - Blank
  6. TargetPathType - Blank
  7. TargetPath - Blank
  8. TargetSite – Site Name (displayed in URL)
  9. TargetSiteSettings – Blank
  10. TargetLibrary – Display Name (displayed on UI)
  11. TargetLibrarySettings – Blank
  12. TargetFolder – Path of the folder hierarchy under which item will be
  13. TargetFolderSettings - Blank
  14. TargetPathMetadata - Blank
  15. TargetTaxonomy - Blank
  16. TaxonomyMappingType - Blank
  17. PathMappingType - Blank
  18. MappingSettings – Specify either “Create” or “Merge” for source item loading option.
  19. CreateHierarchyIfNotExists –
    1. Set to “TRUE” to create the specified TargetSite/TargetLibrary/TargetFolder on target if they do not exist
    2. Set to “FALSE” so that item will fail if specified path does not exist

 

Below is a sample Structure Mapping:

FIGURE_40_-_SAMPLE_STRUCTURE_MAPPING_FILE___UCM_CONTENT_TYPE_TO_SHAREPOINT_SITE_COLLECTION_MIGRATION.png

Note that it is mandatory to select document library in “Content Type Mapping Settings” for relevant content mapping. Ideally we should select 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 specific document library in target site collection for relevant content mapping and then you can skip to mention the same in structure mapping file for relevant documents.

FIGURE_41_-__STRUCTURE_MAPPING_-_CONTENT_TYPE_MAPPING_SETTINGS.png

 

 

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

Comments