Bug 1013924

Summary:	RFE: Allow empty metadata elements to be set
Product:	[Community] PressGang CCMS	Reporter:	Ruediger Landmann <rlandman>
Component:	CSProcessor	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.1
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:

Description Ruediger Landmann 2013-10-01 04:38:50 UTC

Description of problem:
Topic maps currently require edition to be set to be valid; this is not required for DocBook validity

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


How reproducible:
100%

Steps to Reproduce:
1. Create a topic map that does not specify an edition


Actual results:
Validation fails

Expected results:
Validation does not fail

Additional info:
I'm guessing that edition is mandatory because Publican used it for packaging some time ago. This is no longer the case. If edition is mandatory only to appease Publican, we can drop this requirement now :)

Comment 1 Lee Newson 2013-10-01 04:51:16 UTC

Hmm this is a bug/regression as edition previously has not been mandatory and definitely shouldn't be now.

Anyways I just tried it out just now on our test server and couldn't replicate it, so would you be able to provide the error message you are getting Rudi please?

Note: I'm wondering if you are trying to set edition in the following way:

Edition = 

This will throw an error because it looks as though you are trying to define an edition and as such is expecting one (this is true for all metadata elements). If you don't want an edition specified, then you should be able to just not specify it and the edition won't be included in the build output.

Comment 3 Ruediger Landmann 2013-10-02 01:55:54 UTC

(In reply to Lee Newson from comment #1)

> Note: I'm wondering if you are trying to set edition in the following way:
> 
> Edition = 
> 
> This will throw an error because it looks as though you are trying to define
> an edition and as such is expecting one (this is true for all metadata
> elements). If you don't want an edition specified, then you should be able
> to just not specify it and the edition won't be included in the build output.

Yep; that's it; this happened in the context of trying to automate imports. 

So this might well be NOTABUG; but what would be the harm in ignoring elements that don't have a value associated with them?