Pages: 1
Print
Author Topic: Accepting tracked changes at the book level, not topic level  (Read 1201 times)
mcastro
Member

Posts: 2


« on: February 02, 2010, 02:35:25 PM »

Some members of my team enabled tracking changes on some topics in a book. After the content was peer reviewed in the PDF and given final sign off, we wanted to accept all the tracked changes. Because we didn't track which topics had this feature enabled and we don't want to have to search all topics in the book to figure out which topics had the feature enabled, we want to know if there is a way to accept the changes at the book level. If this is not possible, is there an easy way to identify all topics in a book that have this feature enabled?

Thank you!
Logged
mcastro
Member

Posts: 2


« Reply #1 on: February 02, 2010, 02:36:55 PM »

By the way, I'm using XMetal 5.5. We manage our files in Trisoft.
Logged
Derek Read
Program Manager (XMetaL)
Administrator
Member

Posts: 1548



WWW
« Reply #2 on: February 02, 2010, 04:30:45 PM »

Basically, no. This feature works at the document level (topic for DITA) only.

The best I can suggest at this point would be to use another tool to do the searching, then open topics that match your search in XMetaL Author to reject/accept any changes.

There's a posting related to searching for links here, which might be the best help we can offer at this point. The same approach could be taken for locating the PIs used with the Track Changes feature: http://forums.xmetal.com/index.php/topic,128

If you are doing a lot of reviewing you may wish to ask the JustSystems sales people about XMetaL Reviewer, a server product specifically designed for reviewing XML documents which is far more powerful than the Change Tracking feature offered in XMetaL Author. Some information here: http://na.justsystems.com/content-xmetal-reviewer
Logged
Derek Read
Program Manager (XMetaL)
Administrator
Member

Posts: 1548



WWW
« Reply #3 on: February 04, 2010, 04:48:12 PM »

Adding this note to round out this posting (some of this was provided in an offline email, but others might be interested).

XMetaL is only really designed to make changes to files on the local file system (stored on your hard drive). Integrations between XMetaL and a CMS assume that the CMS will deliver checked out files to the local machine, typically in some agreed-upon cache location.

A particular CMS vendor could provide a means to search for particular files (and some do) within their CMS, and they might also offer an XMetaL-specific feature to find our PIs (or other content), and perhaps even modify these things. However, this functionality is really dependent on what the CMS vendor can provide. Exposing that functionality within XMetaL Author Enterprise would be up to the people that offer the integration (we call it a "connector") between XMetaL and the CMS, and in most cases these "connectors" are provided by the CMS vendor as well (which is the case with Trisoft).
« Last Edit: February 04, 2010, 06:46:20 PM by Derek Read » Logged
Pages: 1
Print
Jump to:  

email us