Select to view content in your preferred language

Esri Metadata Editor ISO 19115-3 Security Constraints: Classification Mapping

215
3
Jump to solution
10-30-2024 07:58 PM
Labels (2)
JSPBNE
by
New Contributor

Hi,

we are using the new Esri Metadata Editor to maintain metadata records for our spatial datasets using the ISO 19115-3 style.

When we create a Security Constraint the using the editor the classification can be selected using the drop down list - but after saving, if we export or view the XML (or HTML) the Classification is not populated. It is listed as missing.

This is the same behaviour across the Resource Constraints section and the Metadata Constraints sections.

Is the correct behaviour or user error?. My understanding is the drop down should map to the ISO 19115-3 MD_ClassificationCode codelist. 

Other codelist mappings are functional.

We are using ArcGIS Enterprise v11.3

Security Constraint Classification.png

---fragments from resulting ISO 19115-3 Style XML.
 
<mri:resourceConstraints>
<mco:MD_SecurityConstraints>
<mco:classification gco:nilReason="missing"/>
<mco:userNote>
<gco:CharacterString>Official</gco:CharacterString>
</mco:userNote>
<mco:classificationSystem>
<gco:CharacterString>NSW Government Information Classification, Labelling and Handling Guidelines</gco:CharacterString>
</mco:classificationSystem>
</mco:MD_SecurityConstraints>
</mri:resourceConstraints>

 

<mdb:metadataConstraints>
<mco:MD_SecurityConstraints>
<mco:useLimitation>
<gco:CharacterString>NSW Government Information Classification, Labelling and Handling Guideline: Official</gco:CharacterString>
</mco:useLimitation>
<mco:classification gco:nilReason="missing"/>
</mco:MD_SecurityConstraints>
</mdb:metadataConstraints>

  

0 Kudos
1 Solution

Accepted Solutions
Laura_B
Esri Contributor

Hey @JSPBNE . I noticed one of the screenshots you shared is for the new editor, and mentioned that you are using ArcGIS Enterprise 11.1. Could you please confirm? I believe the new editor was introduced in beta at ArcGIS Enterprise 11.2.

I was able to reproduce this bug when testing the classic editor at 11.1. The issue seems to have been resolved for the new editor at ArcGIS Enterprise 11.4.

Laura_B_0-1731103068695.png

 

View solution in original post

0 Kudos
3 Replies
Laura_B
Esri Contributor

Hey @JSPBNE . I noticed one of the screenshots you shared is for the new editor, and mentioned that you are using ArcGIS Enterprise 11.1. Could you please confirm? I believe the new editor was introduced in beta at ArcGIS Enterprise 11.2.

I was able to reproduce this bug when testing the classic editor at 11.1. The issue seems to have been resolved for the new editor at ArcGIS Enterprise 11.4.

Laura_B_0-1731103068695.png

 

0 Kudos
JSPBNE
by
New Contributor

Hey @Laura_B . Thanks for responding! Yes - you are right. My original info was not entirely correct :(. We are currently running ArcGIS Enterprise 11.3 and the record was created using the new editor. We will re-test when upgraded to 11.4 or higher. Thanks again!

0 Kudos
Laura_B
Esri Contributor

Thanks for confirming, @JSPBNE. Let us know if you run into issues with this after the upgrade. 

0 Kudos