@dvonanderson this still doesn't work. The dictionaryId is exported to the mdJSON. But, the dictionaryId from an imported mdJSON file is not beinig assigned to the internal mdEditor-Json object.

@hmaier-fws pushed up some new commits and revised the PR statement please take a look

@dvonanderson there are still some problems.

Issue #679 seems to be resolved. But when importing mdJSON, the dataDictionary and contact arrays are still being embedded in the "type": "records" object (issue #682).

Import of mdJSON, still does not associate the dictionary with the metadata record (no dictionary selected under /record/xxx/edit/dictionary"). I assume this might be due to the dictionary records still not being structured properly. When viewing records using the mdEditor dashboard "Preview JSON":

• contacts are properly structured
• dictionaries should not enclose elements within a "dataDictionary" object. There should only be one object that contains all dictionary elements.

The dictionary is still structured as:

{
  "dataDictionary": {
    "citation": { },
    "subject": [ ],
    "responsibleParty": { },
    "entity": [ ],
    "domain": [ ],
    "description": " ",
    "dictionaryIncludedWithResource": false,
    "dictionaryId": "8dd05b0d-95c9-40f0-880d-72d18ef29c27"
  },
  "dictionaryId": "7648f752-1e09-4fdc-8cdd-c18d233f89bb"
}

It should be structured as follows:

{
  "citation": { },
  "subject": [ ],
  "responsibleParty": { },
  "entity": [ ],
  "domain": [ ],
  "description": " ",
  "dictionaryIncludedWithResource": false,
  "dictionaryId": "8dd05b0d-95c9-40f0-880d-72d18ef29c27"
}

On export, the mdDictionary array IS NOT using the identifiers from .dataDictionary.dictionaryId but it is generating a new .dictionaryId and using that instead of the identifier within the dataDictionary element.