Implementing the ability to add campaign information to the ISO, I've been using the spreadsheet. Similar to the bit with Platforms, I think the spreadsheet may not be completely up-to-date. Here is a sample of the ISO we are using:
<gmi:operation xlink:type="simple">
<gmi:MI_Operation>
<gmi:description>
<gco:CharacterString>2009_GR_NASA > Operation IceBridge Greenland/Arctic Sea Ice 2009, StartDate=2009-01-01T00:00:00Z, StopDate=2009-12-31T23:59:59</gco:CharacterString>
</gmi:description>
<gmi:identifier xlink:type="simple">
<gmd:MD_Identifier>
<gmd:code>
<gco:CharacterString>2009_GR_NASA</gco:CharacterString>
</gmd:code>
</gmd:MD_Identifier>
</gmi:identifier>
<gmi:status/>
<gmi:parentOperation xlink:type="simple"/>
</gmi:MI_Operation>
</gmi:operation>
This is all in the Acquisition Information tag, between the instruments and platforms tags.
The part in the "code" tag seems to get picked up properly as the Short Name. The entire string of "description" seems to be pulled in as Long Name. However, I am not sure what the proper way to do Start and Stop date is; the spreadsheet says to do it as part of the character string, but in practice it seems that description is just used only as the Long Name. Also, I think we may not need to do it in "keyword" format for this part (but we can include keywords in the ISO in addition to this).
It DOES seem to ingest multiple campaigns properly; when I include multiple sections like the above, the ECHO10 does seem to have multiple campaigns, so I think the key will just be to knowing how to get the start/stop dates added properly. The spreadsheet may also need to be updated to reflect how it's ingesting, as the spreadsheet makes it seem like Short Name and Long Name would be separate identifiers, which I'm not sure is allowed.