Create template for CNM message in JSON format

[lisakaser]

1 story point

Acceptance criteria:

Visual inspection of CNM message and JSON format by Amy

[juliacollins]

@afitzgerrell I created two template files: one for the "body" of the CNM message which applies to all CNM content for a given collection, and one that can be repeated for the multiple files associated with a collection (including the UMM-G file).

The body content:

{
    "version": "1.5.1",
    "submissionTime": "$submission_time",
    "identifier": "$uuid",
    "collection": "$auth_id",
    "provider": "$provider",
    "product": {
        "name":  "$producer_granule_id",
        "dataVersion": "$version",
        "files": []
    }
}

The files content (repeated for each file):

{
    "name": "$file_name",
    "type": "$file_type",
    "uri": "$staging_uri",
    "checksumType": "$checksum_type",
    "checksum": "$checksum",
    "size": $file_size
}

[juliacollins]

@afitzgerrell a few notes to guide your review:

• The terms beginning with a $ in the template files will be replaced with the actual values for a given dataset.
• To see the files in their native habitat, update your working directory (notes on that step below) and look in <path-to-your-copy-of-granule-metgen>/src/nsidc/metgen/templates

To update your copy of the code base:

• cd path-to-your-copy-of-granule-metgen
• See if you've made any changes to files that might collide with changes in the remote repository: git status "Untracked" files don't matter.
• Make sure you're on the main branch and update your local copy: git checkout main; git pull
• Checkout the branch where I'm making changes: git checkout issue-39

That should do it, but let me know if you're not seeing the expected updates.

[afitzgerrell]

Everything worked and checks out well!