Project Description
Version |
Date |
Changes |
1.0 |
2011-05-24 |
Initial version. |
Situation: I have a product that consists of operations (chapters). Each operation has unique steps plus steps (plugins) used in many operations. For example:
Log Collection (operation/chapter)
- - About Log Collection and Extraction (unique)
- - Extract or Compress (unique)
- - Find All Subnets Step (ref to plugin)
- - Select Operations (unique)
- - Find All Nodes Step (ref to plugin)
- - Select Nodes Step (ref to plugin)
- - Key Distribution Step (ref to plugin)
The topics called "Steps" have a generic statement that says this step is used many times so to get more info on this step (plugin) click the Related Link. That link opens the topic that has the information about the plugin (which has the context-sensitive TopicAlias tag on it). These "Steps" and plugins are in their own chapter map.
Plugins (chapter)
- - Find All Subnets (plugin content)
- - Find All Subnets Step (topic used in many ops to point back to associated topic)
- - Find All Nodes
- - Find All Nodes Step
- - Select Nodes
- - Select Nodes Step
Problem: When using a single DITA topic multiple times in a help project, WebWorks creates the first instance of that topic with the Related Link in it and working. Subsequent instances of the same topic are created with an "_n" appended and the link is not there.
Our production content is still in Frame9 (designed the same way) and WebWorks ePublisher Express 2010.3 does NOT create "duplicate" topics with that source the way it does with the DITA content. The reason this is designed this way is that the TopicAlias tag can only be used once and must be placed on the plugin topic with the content.
Is there a way to keep the working Related Link in the subsequent topics?
Thanks, Nancy