Bug 823692

Summary: Missing instructions for XML Export Only
Product: [Other] Topic Tool Reporter: Jared MORGAN <jmorgan>
Component: doc-cspAssignee: Joshua Wulf <jwulf>
Status: CLOSED NOTABUG QA Contact: ecs-bugs
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: lcarlon, lnewson, mmurray
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-07 14:58:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jared MORGAN 2012-05-21 22:02:02 UTC
Description of problem:

I needed to export the XML from the CCMS to test import to another toolchain (in my case, Confluence). But there were no instructions specifically for this operation.

Version-Release number of selected component (if applicable):

Unsure of Book version number. I guess it is 1.0


How reproducible:

100%

Additional info:

I checked with Lee Newson, and he confirmed the correct procedure with me. Here it is:

1. csprocessor checkout [content_spec_number)
2. cd [checked-out spec]
3. csprocessor build 
   - csprocessor build -p (-p to enforce permissive mode 
     in case of broken topics - only use for test imports).
4. csprocessor assemble --no-build (so the content spec isn't built,
   and only XML files are assembled)

The dir location for XML files after csprocessor assemble --no-build is <bookname>/assembly/publican/en-US

Comment 1 Lee Newson 2012-07-30 04:54:32 UTC
Just to some minor details to this.

Steps 3 & 4 can be combined into: "csprocessor assemble -p". However this will also run the publican build command. As such I've added an RFE (see Bug #844233) to support the functionality directly.