Will use this issue to track the problems with Core JSON things in the SESAR iSB instance.
As a general rule, it looks like the data fields in the SESAR are camel-cased, while the Core JSON is now using lowercase separated by underscores.
e.g.
SESAR
"curation":
{
"curationLocation": "Integrated Ocean Drilling Program (IODP)",
"accessConstraints": "Not Provided"
},
vs. Core JSON
"curation":
{
"curation_location": "",
"access_constraints":
[
""
]
},