automate_schema_rule_mapping-BK

[bhawana11]

This is a pull request for issue #341

Expected outcome:
The script lists all the missing schema field names found in the rules_mapping.json in the terminal itself.

Code Changes:
Added a python script in schemas which downloads the schema's from
Umm-c : https://git.earthdata.nasa.gov/projects/EMFD/repos/unified-metadata-model/browse/granule/v1.6.6/umm-g-json-schema.json
Umm-g: https://git.earthdata.nasa.gov/projects/EMFD/repos/unified-metadata-model/browse/collection/v1.18.4/umm-c-json-schema.json
echo-c : https://git.earthdata.nasa.gov/projects/EMFD/repos/echo-schemas/browse/schemas/10.0/Collection.xsd
echo-g: https://git.earthdata.nasa.gov/projects/EMFD/repos/echo-schemas/browse/schemas/10.0/Granule.xsd
dif-10: https://git.earthdata.nasa.gov/projects/EMFD/repos/dif-schemas/browse/10.x/dif_v10.2.xsd
The script then checks every segment in each mapping path and lists all missing schema field names found in rules_mapping.json.

To Reproduce:
Use this command in terminal : python rules_mapping_validation.py

[lavanya3k]

The above code changes have been tested, and the following results indicate missing or changed metadata elements in each schema. Based on the results, we will make changes to therules_mapping.json.

Schema - dif10 and umm-c

Schema - echo-c and echo-g

[lavanya3k]

For umm-c schema, the following metadata elements were revised in the wiki. Let me know the changes required.
@fb0023 - Can you comment on what changes are required for echo and dif10

PaleoTemporalCoverage/PaleoEndDate - Does it exists but is not relevant
PaleoTemporalCoverage/PaleoStartDate - Does it exist but is not relevant
Platform/Characteristics/DataType —> Platforms/Characteristics/DataType
Platform/Instrument/Characteristics/DataType → Platforms/Instruments/Characteristics/DataType
Platform/Instrument/ComposedOf/Characteristics/DataType → Platforms/Instruments/Characteristics/DataType
Platform/Instrument/ComposedOf/ShortName → Platforms/Instruments/ShortName
Platform/Instrument/NumberOfInstruments → Platforms/Instruments/NumberOfInstruments
RelatedUrl/GetService/DataType —> RelatedUrls/GetService/DataType SpatialRepresentationInfo/Horizontal_Resolution_Range —> SpatialExtent/HorizontalSpatialDomain/Geometry/BoundingRectangles/WestBoundingCoordinate
SpatialExtent/HorizontalSpatialDomain/Geometry/BoundingRectangles/NorthBoundingCoordinate
SpatialExtent/HorizontalSpatialDomain/Geometry/BoundingRectangles/EastBoundingCoordinate
SpatialExtent/HorizontalSpatialDomain/Geometry/BoundingRectangles/SouthBoundingCoordinate

SpatialRepresentationInfo/Vertical_Resolution_Range --> SpatialExtent/VerticalSpatialDomain/Value

[bhawana11]

These are the output after updating the automation script: