DITA maps with topic references that are imported from the file system maintain referential integrity to the top-level object that was the original target when the object was imported into the PTC Server. Imported content references also maintain referential integrity to the top-level topic target. Even though the link may have a reference ID specified, there is no referential integrity to specific sections inside a target object.

There is an important consideration in how you select DITA objects to bring into Arbortext Editor. When you insert a link using the Resource Manager, the link will go only to the object that was selected from the Browser using Show in Resource Manager. If you select a Ditabase to display in the Resource Manager, then the repository link will go to the Ditabase, even if you insert a topic reference to a topic in the Ditabase. You can link only to the Ditabase, but not specifically to any objects it contains. If you need to link to individual objects from within the Ditabase, expand the Ditabase in the Browser and select the objects individually. When you choose Show in Resource Manager, the CMS Search Results list displays those objects. You can then link directly to the object in the Ditabase.

For example, if you select a Ditabase to display in the Resource Manager, then the repository link will go to the Ditabase, even if you insert a topic reference in the DITA map to a specific topic in the ditabase. You might still want to choose the Ditabase because, if you use many of the topics in the Ditabase, you only need to download one file to access all the topics in it.