HOW TO
Deciding what validation rules to enforce against documents published to a portal is important because validation affects the quality of the metadata documents available in the portal. Before validation is altered, the purpose for doing so should be clear. Is it a matter of making a specific set of metadata available? Is the current validation too stringent? Could some validation rules be turned off while others are left in place? Or should validation be turned off entirely, so all documents publish without validation?It is best to publish metadata that passes all validation without altering the validation rules. Providing correctly formatted metadata documents is preferable to changing the rules to fit the metadata. However, perfect metadata is not always feasible. Instructions provided describe how to modify validation so that certain documents that currently don't publish can be published successfully.
Unable to publish document.
Your metadata document did not pass Content Validation: filename
Rule: Check the value and presence for field abstract
Status: error
Reason: The required field is not populated, present or contains incorrect information
Metadata Element: /metadata/idinfo/descript/abstract |
/metadata/idinfo/descript/purpose | /metadata/idinfo/descript/supplinf
Rule: Check the value and presence for field subject
Status: error
Reason: The required field is not populated, present or contains incorrect information
Metadata Element: /metadata/idinfo/keywords/theme/themekey
Rule: Check the value and presence for field street address
Status: error
Reason: The required field is not populated, present or contains incorrect information
Metadata Element: /metadata/idinfo/ptcontac/cntinfo/cntaddr/address
Code:
<!--xsl:call-template name="check-origin"/-->
<xsl:call-template name="check-fileIdentifier"/>
<xsl:call-template name="check-title"/>
<xsl:call-template name="check-abstract"/>
<xsl:call-template name="check-subject"/>
<xsl:call-template name="check-restype"/>
<xsl:call-template name="check-date"/>
<xsl:call-template name="check-contact"/>
<!-- special case for extent - must be 4 elements present (to define the bounding box).
Also checks for Lat/Long (i.e. 'Degrees') for coordinate values. -->
<xsl:call-template name="check-bnd"/>
Code:
<!--xsl:call-template name="check-origin"/-->
<xsl:call-template name="check-fileIdentifier"/>
<xsl:call-template name="check-title"/>
<xsl:call-template name="check-abstract"/>
<xsl:call-template name="check-subject"/>
<xsl:call-template name="check-restype"/>
<xsl:call-template name="check-date"/>
<!--xsl:call-template name="check-contact"/-->
<!-- special case for extent - must be 4 elements present (to define the bounding box).
Also checks for Lat/Long (i.e.'Degrees') for coordinate values. -->
<xsl:call-template name="check-bnd"/>
Article ID:000009548
Get help from ArcGIS experts
Download the Esri Support App