Export mdJSON function does not write dictionaryId

[hmaier-fws]

Issue

mdEditor Version (find version under settings): https://github.com/adiwg/mdEditor/tree/405d949e

mdEditor Web Address (enter the URL): https://go.mdeditor.org/

Issue Description:

The "Export mdJSON" function does not include a dictionaryId with the dataDictionary object

Steps to reproduce (Bug reports only):

1. Load example mdEditor file "min-valid-mdEditor-dict1-20240430.json". The metadata record in this file is associated with dictionary "mdDictionary":["7e520389-7b0a-4552-ac3f-f5f1bc81c056"]
2. Export metdata record using the "Export mdJSON" option. Resulting file: min-valid-mdJson-dict1-20240430.json

Observed Results (Bug reports only):

• The mdJson file contains dataDictionary (line 10) and mdDictionary (line 125) arrays.
• The dataDictionary object (lines 11-123) does not contain a dictionaryId element.
• Subsequent import of the mdJson into the mdEditor results in a Data Dictionary without an identifier
  • The dictionary summary page displays the "Dictionary Id" as "Not Defined"
  • Metadata record is no longer associated with the data dictionary.

Expected Results (Bug reports only):

1. Exported mdJSON file should contain a dictionaryId element within the dataDictionary object:

{
  "dataDictionary": [
    {
      "dictionaryId": "dictionary UUID",
      "citation": {
        ...
      },
      ...
    }
  ]
}

2. Import of the mdJson into the mdEditor should:

• Result in the imported data dictionary having a dictionaryId
• The metadata records should retain their associations with the appropriate data dictionary(ies)

[hmaier-fws]

@dvonanderson this seems to be a broader problem with how the internal mdEditor data is structured. Currently, the data model stores the dictionaryId key outside of the dataDictionary object:

The dictionary ID should be included as an element of the object:

{
  "dataDictionary": {
    "dictionaryId": "77985ed7-7972-4a5b-ac25-04457e1c854e",
    "citation": { },
    ...
}

[hmaier-fws]

Implementing a fix for issue #705 would likely also resolve this issue.