Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
I'm having a slightly different but related issue. I'm hoping someone can offer a creative solution other than having to copy and paste the code or re-create the master TOC manually.
Our situation (RH7) is that several authors own individual projects that pertain to their specific subject area. However, all have the same TOC and folder structure (e.g., all have a book called "Procedures", another called "Work Instructions" and so forth). They didn't want to have separate books in the final master project because the end-users may not necessarily know which "book" to look in to find the procedure or work instruction they need (the subject areas sometimes overlap or are relatively transparent to the users). In other words, we want one master book called "Procedures" that merges the topics from all the subprojects' "Procedures" books in the TOC.
I was hoping the TOC placeholder would work like the Index placeholder, which merges all the entries. Thinking about it now, I guess that's totally wishful thinking, but does anyone know how to easily achieve this effect, even if it means re-thinking our architecture and workflow?
Thanks!
-Kristen
Copy link to clipboard
Copied
Hi Kristen.
Do the projects each of your authors work on need a book at all? My thinking is that if the TOC only contains topics that the master project could just contain a "Procedures" book inside which are the merged projects.
Read the RoboColum(n).
Copy link to clipboard
Copied
Thanks Colum, for giving this some thought. Yes, they do need books since there are hundreds of work instructions in a dozen or more functional areas. But we've sort of figured out a process whereby all authors check in their projects on Thursday EOB, and then the "robohelp administrator" gets the latest version of all subprojects, generates locally, and then publishes the master project on Friday. We have been able to collect the metrics (roboserver reports) using this methodology, by some small miracle. So it satisfies our requirements for the time being.
Also, in order to do "ad hoc" publishing, we have set up a test system on a file share, published the master to it to create the MergedProjects folder and subfolders, and then mapped the subprojects "output folder and start page" to that subfolder. We just generate the subproject to that location whenever necessary and have a shortcut to the "Master.htm" ("launch file") to view the whole sha-bang. That lets the different authors to psydo-publish their own projects independantly of the others.
That's how we ended up resolving the issue.
-Kristen
Copy link to clipboard
Copied