Bug 818033

Summary:	RFE: Tag the spec itself with global tags
Product:	[Community] PressGang CCMS	Reporter:	Joshua Wulf <jwulf>
Component:	CSProcessor	Assignee:	Lee Newson <lnewson>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	1.x	CC:	jwulf, lcarlon, misty
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:	2013-05-29 02:23: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 Joshua Wulf 2012-05-02 03:52:27 UTC

Now that Content Specs are topics themselves, 

can we make it so that the Content Spec is tagged with the metadta tags specified as global tags for the Content Spec. 

Since those tags are being applied to all topics in the spec, we can assume that they represent the content of the book, and hence can be meaningfully used to categorise the spec itself.

Comment 1 Misty Stanley-Jones 2013-05-29 02:23:55 UTC

Content specs won't be topics much longer. Closing this.