Managing ANS maps

You are a developer working for a news organization that is preparing to bring stories from a CMS into Arc XP. You want Migration Center to process the transformations of your previous CMS source content into ANS documents. You open the Migration Center ANS mapper and create an ANS map document. You choose a story content type template and upload a JSON file containing a representation of a story from the previous CMS, with all its properties. You work through the sample CMS content, locating the content's unique id, story body, author credits, and publish date. You add transformation rules to the map for each of the content pieces you identify. You validate and save the transformation rules and copy the map ID to use in the next part of your project.

You create another ANS map document, choosing an image content type template and uploading a JSON file containing a representation of an image from the previous CMS, with all its properties. You locate the sample image's url, filename, and caption in the uploaded JSON displayed in the ANS map. You add transformations to the map, targeting each of the image properties. You use the mapper tool's validate function to test that your transformations result in valid ANS image JSON. You copy the map ID to use in the next part of your project.

You are a developer working for a news organization that is migrating story content into Arc XP, using content maps you created in the ANS maps page of Migration Center to handle the transformations. You are investigating errors that have stopped some stories from ingesting. The error text suggests that the source content did not transform into valid ANS. You examine the complete source data of an item of erroring source content. You also open the ANS maps page and look at the map that was used for the transformation. When you compare the erroring source content to the sample content in the mapper, you notice that there are differences in the content structure. You identify the cause is that the erroring source content contains different fields than what the source content in the ANS map defines. As a result, this map won't be able to find the story's headline and author data.

You create a new ANS map document, loading the erroring source content as the source file. You create transformation rules for this map, validate that the ANS can generate correctly, save the map, and copy the map ID. You return to the project code that runs the migration routine and add logic to send some stories to the Migration Center API using the original map ID, and other stories to the Migration Center API using this new map ID. You re-migrate the erroring source document, and on the second attempt the new map ID is applied and valid ANS JSON is created and ingested into Arc XP.