Change the product or library to which an object belongs

You can refactor an object from one product or library to another; for example, you can refactor a topic from a product to a library or between libraries.

Several rules dictate to which product or library an object can be refactored; however, the main rule is an object cannot be refactored to a layer higher in the library structure than its parent object or lower than its child objects. Since these relationships can be difficult to discern, they are calculated and displayed in the Library Dependency Editor when you click Refactor. Invalid selections are indicated in dark gray.

For example, as shown in the following figure, suppose you have a product layer (layer 0), a backend layer (layer 3), and legal layer (layer 6). You have a map and its referenced topics in the Output Generator library in the backend (layer 3). If you try to refactor the map, your only valid choices are the DITA CMS product or the Textml Server product layers. You cannot refactor the map to the Logos library in the legal layer, because that would mean the topics (child objects in layer 3) would be in a higher layer than their map (parent object in layer 6).

Figure 1. Example of the relationships in the Library Dependency Editor Example of the Library Node Select Dialog

To refactor an object:

  1. In a view, right-click an object and click Dynamic Release Management.
  2. Click Refactor.
  3. In the library dependency graph, click the product or library to which you want the object to belong.
  4. Click OK.