Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Metadata Files

(see Metadata Attributes in Section 4.2.4) supplied as per Excel template or alternatively in file formats suitable for reading and loading.

ASCII

  • CSV (Comma separated values)

  • Text (Tab delimited values)

MS Excel

  • Excel 2003 (.xls)

  • Excel 2007 – Excel 365 (.xlsx)

Metadata

Most large organisations that distribute spatial data, catalogue the existence of that data using a metadata catalogue system such as GeoNetwork opensource (geonetwork-opensource.org). AusSeabed Contributing Hubs must provide a catalogue that can be harvested by AODN (and others). The preferred mechanism employed is an Open Geospatial Consortium (OGC) compliant Catalogue Service for the Web (CSW). AusSeabed requires that metadata entries be systematised to support downstream searching and filtering.

...

GeoNetwork provides at least three method of editing metadata: a) a simple interface; b) the full interface; and c) an XML editor. Most metadata can be entered in the simple interface; however, a number of fields require the full editing interface or XML editor (or import) including:

Attribute

Location in XML

Abstract

IdentificationInfo/Abstract

Title

IdentificationInfo/Citation/Title

Keywords

1<mri:descriptiveKeywords>

2  <mri:MD_Keywords>

3    <mri:keyword>

4      <gco:CharacterString>marine</gco:CharacterString>

5    </mri:keyword>

6    <mri:type>

7     <mri:MD_KeywordTypeCode codeList="codeListLocation#MD_KeywordTypeCode" codeListValue="theme"/>

8    </mri:type>

9  </mri:MD_Keywords>

10</mri:descriptiveKeywords>

Start Date

IdentificationInfo/Extent/TemporalExtent/TimePeriod/BeginPosition

End Date

IdentificationInfo/Extent/TemporalExtent/TimePeriod/EndPosition

Vessel (for surveys, not compilations)

Acquisition Information/Platform/Identifier

Instrument (for surveys, not compilations)

Acquisition Information/Platform/Instrument/Identifier

Vessel and instrument should also link to a valid vocabulary entry in a vocabulary server. e.g.

1<mcc:code>

2<gcx:Anchor xlink:href="'http://vocab.nerc.ac.uk/collection/C17/current/09SS' ">Southern Surveyor</gcx:Anchor>

3</mcc:code>

 

Likewise, start and end ports should link to a valid vocabulary entry.

...

A fully marked up ISO-19115 XML example can be found here.