Metadata: British Geological Survey (BGS) Geophysical and Sampling Survey 2009/5 (D342): Irish Shelf/Rockall/Hatton (17/Aug/2009 to 18/Sep/2009)

The alternative title is used to add the names by which the resource (e.g. dataset) may be known and may include short name, other name, acronym or alternative language title.

A Unique Resource Identifier allows a dataset to be identified by a code. This code is generally assigned by the data owner and commonly consists of the organisation which manages the dataset and a number or code which is used to uniquely identify it within the databases of the organisation. If this code is unique then it is possible for an organisation to identify a dataset that a 3rd party may be referring to and also to quickly identify where dataset records may be duplicated in a portal.

The abstract should provide a clear and brief statement of the content of the resource (e.g. dataset). Include what has been recorded, what form the data takes, what purpose it was collected for, and any limiting information, i.e. limits or caveats on the use and interpretation of the data. Background methodology and quality information should be entered into the Lineage element (element 10). It is recommended that acronyms and abbreviations are reproduced in full. e.g. Centre for Environment, Fisheries and Aquaculture Science (Cefas).

The online location of the resource.

Keywords belonging to various MEDIN approved thesauri.

These four sub-elements represent the geographical bounding box(s) of the resource's extent. Multiple bounding boxes are allowed to describe datasets or series which have a disparate geographic coverage; each bounding box must have only one occurrence of each of east, west, north and south sub element described. The co-ordinates of these bounding box(s) should be expressed as decimal degrees longitude and latitude. A minimum of two and a maximum of four decimal places should be provided.

Latitudes between 0 and 90N, and longitudes between 0 and 180E should be expressed as positive numbers, and latitudes between 0 and 90S, and longitudes between 0 and 180W should be expressed as negative numbers. In the event that a single point is being described we recommend using the en-coding shown in the last example.

This element describes any restrictions imposed on the resource for security and other reasons using the controlled ISO vocabulary RestrictionCode. If there are no limitations on public access, this must be indicated. All terms are can be found in the MEDIN discovery standard.

This element describes any restrictions and legal restraints on using the data. Any known constraints such as fees should be identified.

Identify the type of resource e.g. a dataset using the controlled vocabulary, MD_ScopeCode from ISO 19115. In order to comply with INSPIRE the resource type must be a dataset, a series (collection of datasets with a common specification) or a service. All terms can be found in the MEDIN discovery standard

It is recommended that all known temporal references of the resource are included. The temporal extent of the resource (e.g. the time period over which data were collected) and the date of publication (i.e. the date at which it was made publicly available) are mandatory.

Keywords selected from controlled vocabularies to describe the spatial extent of the resource. MEDIN strongly recommends the use of the SeaVox Sea Areas which is a managed vocabulary and has a worldwide distribution. Other vocabularies available including ICES areas and rectangles or Charting Progress 2 regions may be used.

Describes the system of spatial referencing (typically a coordinate reference system) used in the resource. This should be derived from the EPSG register of geodetic parameters. To find a code click on the OGP Online Registry and if you know the title (eg WGS84) then type this in the ‘Name’ field and click search. The name, code and further information is displayed. If you are looking for a specific type of reference system such as ‘vertical’ then click in the ‘Type’ box, hover over coordinate reference system and click on vertical and then click the search button and all recorded vertical reference systems are shown. If you want to search for a reference system in a particular part of the world (e.g. Northern Ireland Grid) the you may do so by submitting a term to the ‘Area’ box or fill out the lat and longs then click search. The website also provides a database of the reference systems and web services to access the information.

Provides an indication of the spatial resolution of the data. The element has largely been derived for the mapping community and is currently poorly defined however MEDIN recommends that you provide the average distance (i.e. resolution) between sampling locations in meters. For example, if a dataset was composed of a grid of stations which have an average distance between stations of 2 km then 2000 meters should be recorded. In the case of a multibeam survey it should be the average distance between each sounding or ‘ping’ on the sea bed. For transect data such as an intertidal beach survey or a single beam echo sounder survey the resolution should be taken as the distance between the transect lines.

For single samples and observational data MEDIN recommends using ‘not applicable’.

MEDIN is in discussions with GEMINI and ISO to allow the use of scale for this element (e.g. pressure) and also to allow the use of ‘unknown’. GEMINI accepts that in many cases only approximate values can be given.

This element is mandatory for INSPIRE and must be included. This indicates the main theme(s) of the data resource. It is required for INSPIRE compliance. The relevant topic category should be selected from the ISO 19115/TC 211 Topic Category list. Within MEDIN the parameter group keywords from the BODC Parameter Discovery Vocabulary (P021) list are mapped to the ISO Topic Categories so it is possible to generate the topic categories automatically once the keywords from BODC Parameter Discovery Vocabulary (P021) have been selected.

Lineage includes the background information, history of the sources of data used and can include data quality statements. The lineage element can include information about: source material; data collection methods used; data processing methods used; quality control processes. This should include any data collection standards used. Additional information source to record relevant references to the data e.g. reports, articles, website.

Provides a description of an organisation or person who has a role for the dataset or resource. 'Originator' (a mandatory field) is the person or organisation who created the resource. 'Custodian' (a mandatory field) is the person or organisation that accepts responsibility for the data and ensures appropriate care and maintenance.

If the data has been lodged with a MEDIN approved Data Archive Centre then the DAC should be specified as the Custodian. 'Distributor' (a conditional field) is the person or organisation that distributes the resource. 'pointOfContact' is the party who can be contacted for acquiring knowledge about or acquisition of the resource. There are further designations listed at 'Annex H. ISO Responsible party codelist' in 'Guidance notes for the production of discovery metadata for the Marine Environmental Data and Information Network (MEDIN)'.