Bug 1010757

Summary: Topic Filter should use the topic endpoint and not contentspecnode
Product: [Community] PressGang CCMS Reporter: Lee Newson <lnewson>
Component: DocBook-builderAssignee: Lee Newson <lnewson>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.1CC: mcaspers
Target Milestone: ---   
Target Release: 1.8   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-13 21:10:55 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 Lee Newson 2013-09-23 02:00:50 UTC 
The Topic Filter in the DocBuilder currently works by doing a query on the contentspecnode endpoint, however if new topic types are added then this is going to fail. It would make more sense to do a query on the topic endpoint and expand the "contentSpecs" collection. This would also allow for all the data to be pulled down in one request instead of a request per topic id.
Comment 1 Misty Stanley-Jones 2013-09-26 02:01:20 UTC 
Can you rephrase this into a user story?
Comment 2 Lee Newson 2014-06-23 00:16:43 UTC 
Fixed in the devel branch of DocBuilder2. The query has also been compacted down to a single query as well instead of a query per topic id.

See https://github.com/pressgang-ccms/DocBuilder2/commit/59157a25111734a88417e1b7b0eef50f8cdb5d0a
Comment 3 Matthew Casperson 2014-07-03 21:55:26 UTC 
Verified that queries now used the topic endpoint and expand the content specs.

Also confirmed that new node types like info topics can be used to filter the list.