Bug 1010757 - Topic Filter should use the topic endpoint and not contentspecnode
Summary: Topic Filter should use the topic endpoint and not contentspecnode
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: DocBook-builder
Version: 1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.8
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-23 02:00 UTC by Lee Newson
Modified: 2014-07-13 21:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-07-13 21:10:55 UTC
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.