Bug 861203

Summary: Include keywordset and keyword elements in assembled content.
Product: [Community] PressGang CCMS Reporter: Stephen Gordon <sgordon>
Component: CSProcessorAssignee: Nobody <nobody>
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.0   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:
Bug Depends On: 836838    
Bug Blocks: 791288    

Description Stephen Gordon 2012-09-27 19:45:42 UTC 
Description of problem:

PressGang currently includes keywords in topics based on the tags associated with the content. For example:

    <sectioninfo>
        <keywordset>
            <keyword>
                Installation
            </keyword>
            <keyword>
                Red Hat Enterprise Virtualization Manager
            </keyword>
            <keyword>
                RHEV 3.1
            </keyword>
            <keyword>
                Text
            </keyword>
        </keywordset>
    </sectioninfo>

When I grep assembled books for the keyword tags though they are nowhere to be found (except oddly enough in Errors.xml). Ideally the keywordsets should be included in the assembled book.
Comment 1 Joshua Wulf 2012-09-28 15:01:11 UTC 
Rendering of the keywordset currently is (not) done in the Publican brand xsl. 

It is injected into the <head> of the html page as a <meta> element when the topic is the html page is chunked on the topic section.

For example:

<meta name="keywords" content=" csprocessor 0.17 ,  csprocessor 0.22 ">

So build your book as chunked html, then find an html page that contains one topic only. The keywordset for that section will render into the <head>.

One thing to do would be to render all the keywords into the bookinfo keywordset - that would put all the elements into the metadata for the html-single version.

Also, a Publican brand could be modified to render the keywordsets for topics as microdata, ala http://schema.org/docs/gs.html.
Comment 2 Stephen Gordon 2012-09-28 15:16:00 UTC 
(In reply to comment #1)
> Rendering of the keywordset currently is (not) done in the Publican brand
> xsl. 

Right, but as it stands currently we aren't getting that far because the keywordsets aren't even in the XML we export for assembly (again except if/when the topic is listed in Errors.xml).