id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
1046	should FITS HISTORY values be on value or comment?	eugene	Paul Price	It seems the psFitsReadHeader function is putting the header field associated with the COMMENT and HISTORY keys into the psMetadataItem comment element rather that the data.V element.  It is not obvious this is the correct choice: the user then needs to treat those fields even more specially than currently (currently, they are treated as MULTI since they are likely duplicated).  The user has to know to look for the associated value in the comment field not the data field.  Is this sensible?  Or should the entry be considered a value?	enhancement	closed	high		types	unspecified	minor	fixed