Migration Center Content Mapper tool

Note

ANS Mapper is part of the Migration Center product suite. If you're interested in learning more about ANS Mapper and Migration Center, contact Arc XP Customer Support.

The process of importing your content into Arc XP involves three key steps:

understanding your current CMS and its data mappings,
converting your content into ANS (Arc XP Native Specification) format, and
loading that ANS into Arc XP using Migration Center.

Migration Center’s content mapping tool focuses on the second step: converting your content into ANS.

The mapping tool helps you translate your source content into ANS by guiding you through the process of creating ANS documents. This tool lets you create ANS documents one at a time, teaching you the process along the way. If you encounter validation errors, you must update the content map, which you can do directly in the tool.

When you create a content map, you must choose a content type: story, image, gallery, video, author, or tag. Therefore, you must create a content map for each type of content you want to transform into ANS. Use the following sections to build your ANS document and troubleshoot any errors you receive.

The following procedures pertain to the ANS content mapping tool.

Creating an ANS mapping

Creating an ANS mapping is the first step in migrating your content into Arc XP. Use these steps to create your content map.

Navigate to Migration Center.
Click Create Map. The New ANS Map pane opens.
Complete the following fields:
- Map name - enter a name for your content map, for example, Authors
- Content type - choose the type of content you’re mapping, for example, story, image, video, and so on.
- File - click Upload file and upload either an XML or JSON source file.
Click Create map. Your content map appears on the Migration Center page.

You can now proceed to validating your mapping.

Editing an ANS mapping

After you create a mapping, you can update only the name when using the slide out panel. If you need to modify your source document or mapping template, you must navigate to the map editor to replace source documents or edit your mapping template.

Navigate to Migration Center.
On the mapping you want to edit, click the ellipsis icon > Edit. The Rename ANS Map pane opens.
Update the Map name field.
Click Update map.

Validating a mapping

Testing the mapping to ensure the ANS structure is correct is an essential step to converting your content.

Navigate to Migration Center.
Click the name of the content map you want to validate. The mapping opens.
Click Validate. The system processes your content mapping and provides the results on a new page.
Review the results. If errors exist, note the errors and resolve the errors in your content mapping. See Validation errors and resolutions.

Downloading mapping details

After you successfully validate your content map, you can use that map as a guide to bulk convert your content to ANS. You can you download the map as a JSON file to make is easy to use in your migration script.

Navigate to Migration Center.
On the mapping you want to edit, click the ellipsis icon > Download. Your content map downloads as a JSON file.

Deleting a mapping

You can delete a mapping when you no longer need that content map.

Navigate to Migration Center.
On the mapping you want to edit, click the ellipsis icon > Delete.

Validation errors and resolutions

The following table provides a list of errors you might receive when validating your content maps along with instructions for how to resolve them.

Error Examples	Description	Error Category	Error Notation in the UI	Error Resolution
Expected property name or `}` in JSON at position 858 Expected `:` after property name in JSON at position 865 Expected `,` or `}` after property value in JSON at position 28	These errors indicate that your content map contains JSON schema errors.	Syntax Error	N/A (appears as an inline error message in the map pane)	Check the JSON notation in the map for possible errors due to missing or incorrect JSON syntax.
`/mappingTemplate/mappings/0/sourceValue/value` must be string	The `query` was expecting a string, but the `query` is missing or incorrect.	Transformation Error	Mapping Validation	Check the `query` for possible errors due to missing or incorrect values. Refer to the Transform Engine for more details on transform engine rules and usage.
`${assignedField}` is not a supported property for the path you provided for ANS version: `${assignedAnsVersion}` and `type: ${assignedAnsType}`	The ANS body contains elements that the schema version and content type do not support. This usually occurs when `targetPath` (JSON field in the ANS output file) in the map is missing, incorrect, or incomplete.	Validation Error	ANSValidationError	Check the `targetPath` for possible errors due to missing or incorrect ANS field names. Refer to the ANS schema for details on correct naming and usage.
ANS version 0.10.23 is not a valid version	The ANS version that the map is using is not a version that Arc XP supports	Validation Error	ANSValidationError	Fix the ANS version used in the map
`.${assignedField}` should be string	The ANS body contains values that the schema version and content type do not support. This usually occurs when a transformed value (JSON value in the ANS output file) is missing or not valid.	Validation Error	ANSValidationError	Check the ANS output for possible errors due to missing or incorrect ANS values. Refer to the ANS schema for details on supported data types and proper usage. Check the processors in the mapping block for possible errors due to incorrect invocation or dependencies. Troubleshoot by testing one processor at a time.

In this section: