How to migrate files share to OpenText™ Content Server

Scenario

This how-to outlines steps to migrate data from multiple file shares to an instance of OpenText™ Content Server. This approach is optimal when content from the source will be replicated in the destination from the root directory.

Prerequisites

This scenario assumes the following prerequisites have been completed:

An initial source metadata crawl for the dataset that will be migrated
A hash crawl that includes, if desired, full text extraction
Tag duplicates tooling has been run on the index
ROT rules have been reviewed, customized if required, and actioned

Process

The general migration workflow includes the following steps:

Complete an export of the index
Flag ‘to be migrated’ files within the export
Bulk enrich the index with the additional ‘to be migrated’ field
Migrate flagged content

Export the index

To export the necessary details from the index to move forward with subsequent migration steps:

Open Command Prompt as an administrator.
Change directory (cd) to where the Cognitive Toolkit is installed.
In a text editor such as Notepad++, copy the following command:

POWERSHELL

CognitiveToolkit ExportFromIndex --fields name,parent,length,id -q "C:\match_all.json" -u INDEX_SERVER_URL -i INDEX_NAME

4. Make the following updates to the copied command:

Replace INDEX_SERVER_URL with the URL for the index that includes the data to be migrated
Replace INDEX_NAME with the name of the index that includes the data to be migrated

5. Copy the updated command from your text editor to Command Prompt and run.

Flag ‘to be migrated’ files within the export

Using the index export, files can be flagged for migration. Shinydocs recommends using the following approach for flagging ‘to be migrated’ content:

Within the exported .csv, add a new column titled Migrate.
For each file to be migrated, the column value is updated to True.
Once completed, share the updated .csv file with your Shinydocs’ support contact.

Bulk enrich the index

Once identified and shared, Shinydocs completes a bulk enrichment of the index, adding a new migrate field to the index and a value of true for each flagged file.

Bulk enrichment can also be completed by your organization. To do this, please refer to the bulk enrichment templates and README information available from the Shinydocs Customer Portal.

After bulk enrichment completes, refreshing the Visualizer is required. To refresh the Visualizer:

From the Visualizer, click Management.
Click Index Patterns.
Click the respective index pattern.
Click the refresh icon.

Migrate flagged content

Once the index is enriched, content is ready to migrate. To migrate content:

Access Shinydocs Collab and download the migrateTrue.json script.
Navigate to the location where the Cognitive Toolkit is installed.
Copy the script file to this location.
Open Command Prompt as an administrator.
Change directory to the location where the Cognitive Toolkit is installed.
In a text editor such as Notepad++, copy the following command:

POWERSHELL

CognitiveToolkit Migrate   --destination-source-settings "C:\contentserver.json" --start-location 291560 -q "C:\migrateTrue.json" -u INDEX_SERVER_URL -i INDEX_NAME --path-prefix-to-remove "C:\Share\Path\Folder\ACME Test Data - June 2020"

Note: contentserver.json is part of Shinydocs’ resources, and is available from the Shinydocs Customer Portal if not already part of your Cognitive Suite setup.

7. Make the following updates to the command:

Replace the value for start-location with the Node/Object ID for the folder in OpenText™ Content Server that is the migration destination
Replace INDEX_SERVER_URL with the URL for the index that includes the data to be migrated
Replace INDEX_NAME with the name of the index that includes the data to be migrated
Replace PATH-PREFIX-TO-REMOVE with the folder depth desired for the destination
- For example, \\acme\share_1\folder123\file could be updated to \folder123\file, if desired

8. Copy the updated command from your text editor to Command Prompt and run.