Page History

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">operation>
<gmi:MI_Operation>
<gmi:description>
<gco:CharacterString>2009_GR_NASA &gt; Operation IceBridge Greenland/Arctic Sea Ice 2009, StartDate=2009-01-01T00:00:00Z, StopDate=2009-12-31T23:59:59<CharacterString>StartDate=2010-10-19 EndDate=2010-11-21</gco:CharacterString>
</gmi:description>
<gmi:identifier xlink:type="simple">identifier>
<gmd:MD_Identifier>
<gmd:code>
<gco:CharacterString>2009CharacterString>2010_GRAN_NASA</gco:CharacterString>
</gmd:code>
<gmd:codeSpace>
<gco:CharacterString>gov.nasa.esdis.umm.projectshortname</gco:CharacterString>
</gmd:codeSpace>
<gmd:description>
<gco:CharacterString>Operation IceBridge West Antarctica/Antarctic Sea Ice 2010</gco:CharacterString>
</gmd:description>
</gmd:MD_Identifier>
</gmi:identifier>
<gmi:status gco:nilReason="missing"/>
<gmi:parentOperation xlink:type="simpletype>
<gmi:MI_OperationTypeCode codeList="#MI_OperationTypeCode" codeListValue="real">real</gmi:MI_OperationTypeCode>
</gmi:type>
<gmi:parentOperation gco:nilReason="missing"/>
</gmi:MI_Operation>
</gmi:operation>

This is all in the Acquisition Information tag, between the instruments and platforms tags.

A few notes:

• The part in the identifier "code" tag seems to get picked up properly as the Short Name as expected.
• The spreadsheet (M530) indicates that the Long Name should be coming from the "description" tag inside the identifier tag.  However, it seems to be pulling from the OUTER "description" tag (the one just above the identifier tag).
• The spreadsheet (M532:M533) indicates that the Start and Stop dates should be coming from parsing out the outer "description" tag; however, as mentioned above, the outer tag is being used to pull in the Long Name instead.  (I tried putting the StartDate= and EndDate= bits in the "inner" description just to see what would happen, and it's still being ignored.
• There are a few tags that are required by the schema that aren't discussed in the spreadsheet:
  • gmi:status - this is a required tag.  I wasn't sure what to put here, so I just put it as "missing"
  • gmi:type - I may have been able to try putting "missing" here, but I did find a code list entry for this; in the case of what we are doing here, the value is going to all be "real" for our datasets anyway.  It doesn't seem to care that I didn't put a full URL in, but I'll probably need to find out what the URL part should be.
  • gmi:parentOperation - Seems to be required, but I'm not sure what should go here, so I just put it as missing.

 .  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.