Add configuration option for element substitutes (eg. gco:CharacterString)

Date	2010/03/09
Contact(s)	Francois
Last edited	Timestamp
Status	Draft
Assigned to release	2.5
Resources	GéoSource [BRGM]
Ticket

Overview

Actually, GeoNetwork ignore all gco:CharacterString substitutes due to the following lines in schema-substitutes.xml :

<!-- override all the schema substitutes for gco:CharacterString 
	- we don't want any--> 
	<field name="gco:CharacterString">
	</field> 

It also provide by default all substitutes of an element (see below).

The proposal allows to filter these substitution lists using schema-suggestion configuration file and to be able for some elements to use one or more substitutes of gco:CharacterString. Indeed, some substitute like gmx:FileName or gmx:Anchor could be useful in some situation.

The proposal enhancements are :

• Add configuration of allowed substitutes for an element (for iso19139 or iso19110 records)
• Add support for gmx:FileName to be used to store a document in the catalogue (Configuration example to be used for gmd:otherCitationDetails)
• Suggest only gml:Polygon for bounding polygon element.

Proposal Type

• Type: Editor
• App: GeoNetwork
• Module: Editor

Links

• Email discussions:
• IRC discussions:

Voting History

• Proposed for vote by Francois
• +1 : Francois, Simon

Proposal details

Configuration

The file schema-substitutes.xml is modified to load gco:CharacterString substitute on startup. gmx.xsd schema is imported in iso19139 schema.xsd.

Configuration for gmd:otherCitationDetails

In the schema-suggestion.xml, otherCitationDetails allows use of CharacterString or FileName

<field name="gmd:otherCitationDetails">
  <suggest name="gco:CharacterString"/>
  <suggest name="gmx:FileName"/>
</field> 

This will trigger the following in the editor :

Using the gmx:FileName, editors could upload document for the element using the upload panel :

Configuration for gmd:polygon

<field name="gmd:polygon">
  <suggest name="gml:Polygon"/>
</field>

will only suggest gmd:Polygon to editors. Furthermore, the bounding polygon extent map drawing tools only allows to draw polygons. This will make the editor more consistent.

Backwards Compatibility Issues

If no suggestion defined for an element having a gco:CharacterString sub-element, default behavior is applied.

Risks

Participants

• Francois