Ensure Interoperability for records exported from gCat - need to import/harvest into other systems

[LauraBeazley]

I tried to import an XML from gCat with no luck.(import into ArcGISPro.

We need to ensure interoperability for gCat:
a) other catalogs will want to harvest metadata from gCat (open data portal and geo.ca) and
b) our metadata authors need to be able to export their record from gCat and import the XML back into ArcGISPro (for datasets largely) so they can update their source record with the new information that is added to their record in gCat (IDs, links, associations and any edits that transpired , etc) instead of manually updating it. (push changes back to source)

Here's the workflow for dataset:

1. export embedded metadata as 19115-3 XML (2014) from ArcPro (without sensitive info checkbox)

2. import 19115-3 XML(2014) into gCat (using a translation from 2014 to 2018 XML)

3. Add new content and change/remove content. Validate, Edit, review, ready and authorize publication, publish to target audience (public or restricted)

4. Once record is "ready for publishing" - it would help authors to be able to update their source metadata (synchronize) which they had created in ArcGISPro environment, (source metadata is embedded in the dataset), as this is where they will edit their metadata (for datasets "1st lift", we might create another workflow for after first lift )

Example: I exported a dataset record from eCat and brought that into ArcGISPro no problem. When I try to do the same with the same record exported from gCat - it does not import. (Failed to import) Why? Is it the 2014 vs 2018 content ? or is there something going on with the export tool? I though that the ISO XMLs are supposed to be "interoperable"? Do we need a "Save as 2014 version XML? How can a harvester harvest from gCat to another catalog - if the interchange file is not able to be imported into a GIS? Do we need to create a backwards compatible XML? Is the header/schema in the export correctly designed?

something to try? - would Australia be able to import a record from gCat for example, perhaps we could provide an XML to them to see if they can?

Observation: The header for the XML from gCat is different from the same record exported from eCat. These are attached as reference./A test case.

Here are the two files in a ZIP for reference.
6bf24104-2259-4aba-bf9b-0419a4dfb088-AustraliaGDB_from_gCat.zip
19a48f01-4a22-4ccd-b827-3621d34dc391GDB_Australia_from_eCat.zip