Metadata guidance

Metadata can be described as data about data. It provides information on the who, what, where and when of data. It allows prospective users of the data to assess what the data contains and whether it is appropriate for their needs.

The EIDC requires two types of metadata: discovery metadata and contextual metadata.

1. Discovery metadata

Discovery metadata contains brief information about a dataset that enables prospective users to find it using internet search tools and to determine if the data is suitable for their needs.

Discovery metadata contains simple information such as:

  • A brief, concise title  (please see our guidance)
  • A short description of the dataset
  • A list of those who created the dataset (authors)
  • Brief information about how the data were created/processed

It also contains information about how to access (download) the dataset, the terms and conditions regarding its use and how others using it should acknowledge & cite the data.

When you deposit data with the EIDC we'll ask you to provide this information.

The EIDC has a catalogue to make discovery metadata available.

By publishing your data with the EIDC your dataset will be available via our data catalogue and will also be automatically included in, the NERC data portal, the EU's INSPIRE geoportal and via search engines such as Google.

The EIDC adheres to a minimum metadata standard which incorporates the UK GEMINI metadata standard and the Natural Environment Research Council (NERC) metadata quality guidelines 

To see an example of a discovery metadata record and the information it contains, please visit our catalogue.

2. Contextual metadata

Discovery metadata does not provide enough information to be able to use the data and so we require that data also be accompanied by contextual metadata. This provides more detailed information about the data to enable others to properly understand and reuse it.

There is no standard way of recording contextual metadata. We recognise that each dataset is unique and so we are flexible in what metadata is required. However, there are elements that are common to all data, please see Guidance - Supporting Documentation.