The interrogation rule itself looks ok. However, if you also have the base ISO 19115 profile active AND if the interrogation rule for ISO 19115 is before your custom profile, the metadata may still be interpreted as ISO 19115. That is because the rule for ISO 19115 is:
{
key: "iso-19115",
requiredPath: "esri/dijit/metadata/types/iso/base/DataDocumentType",
interrogationRules: [{
path: "/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification",
must: true
}]
},
And means your ISO-based metadata will still be recognized by this rule. You have two options:
- Move your custom profile to the top of the list of typeDefinitions. This way the rule for your custom profile will be evaluate before the base ISO 19115 rule. Geoportal evaluates the rules in order of the list.
- Remove the base ISO 19115 profile ('iso-19115') from the list of allowedTypeKeys. This will remove it entirely from the editor.