MAGIC Discovery (v2)

About

Notes

Rational

The base ISO 19115 requirements are very minimal and not sufficient to meet MAGIC's needs for resource discovery, including:

• ensuring records comply with the BAS Data Catalogue Record Requirements
• ensuring Esri item metadata (internal URL) can be derived from records, to prevent inconsistency and repeated effort
• ensuring access and usage constraints are captured, as MAGIC routinely handles sensitive, licensed or otherwise restricted information
• ensuring minimal information is available to enable future editing workflows (progress and status)
• ensuring a minimal level of data quality information is captured (lineage information)

In essence, this profile aims to provide a higher floor for record completeness, to ensure a minimal level of utility.

Base standard

This profile is based on:

• the ISO 19115-2:2009 standard
• the BAS Data Catalogue Record Requirements

Related profiles

In most cases, records will also follow the MAGIC Administration profile to set administrative metadata.

Changes from previous edition

Previous edition: 1 (2025-06-14 revision).

Breaking changes

• restricting allowed progress code (req. 11) values to 'completed' and 'underDevelopment' only
• added new citation requirement (req. 15)
• added new copyright holder requirement (req. 16)

Major changes

• domain consistency (req. 02) changed to reflect edition 2
• including 'initiative', 'feature' and 'fieldSession' as allowed hierarchy levels (req. 03)
• access constraints (req. 09) changed from authoritative to informative (administrative metadata is now authoritative)

Other changes

• editorial tweaks to improve clarity and align with other profiles
• splitting edition from profile in URLs to better support multiple historic versions
• linking to publicly accessible documentation where possible
• adding cross-reference to administrative metadata profile
• corrected mistake in publication date (req. 07) profile obligation (was 'mandatory' should be 'conditional')
• corrected mistake in publication date (req. 07) profile occurrence (was '1' should be '0..1')
• corrected mistake in lineage statement (req. 13) profile obligation (was 'mandatory' should be 'conditional')
• corrected mistake in lineage statement (req. 13) profile occurrence (was '1' should be '0..1')
• corrected mistake in geographic extent (req. 14) profile obligation (was 'mandatory' should be 'conditional')
• corrected mistake in geographic extent (req. 14) profile occurrence (was '1' should be '0..1')
• removed confusing authorisation justification in usage constraints (req. 10)

Definition

Abstract (this document)

JSON Schema

Example records

Minimal resource record (product): JSON | XML

Minimal container record (collection): JSON | XML

Requirements

Overview

Requirement 01 - File Identifier

Records MUST include the file identifier element, using a value that MUST be unique across all records.

Requirement 02 - Domain Consistency

Records MUST include a domain consistency data quality element, stating the record complies with this profile.

The element value MUST be as per Appendix 1 - Data Consistency Element.

Requirement 03 - Hierarchy Level

Records MUST include the hierarchy level element.

The element value MUST be one of these allowed options from the 'ISO 19115 MD_ScopeCode' code list (or a local extension as indicated):

• 'collection'
• 'dataset'
• 'feature'
• 'fieldSession'
• 'initiative'
• 'product'
• 'paperMapProduct' (local extension)
• 'series'

Requirement 04 - Catalogue Identifier

Records MUST include an identifier element, identifying the resource within the BAS Data Catalogue.

This identifier MUST use these values:

• value: the value of Requirement 01 - File Identifier
• URL: the Catalogue item URL for the record, in the form: https://data.bas.ac.uk/items/{file_identifier}
• namespace: 'data.bas.ac.uk'

Requirement 05 - Edition

Records MUST include an edition within the resource citation element, using a value that MUST be unique across all editions of a resource series.

Requirement 06 - Released Date

Published resources MUST include a released date within the resource citation element of the record.

The released date value MAY be in the past (in which case the resource is deemed 'released'), or the future (and deemed 'under embargo').

Draft records MAY include a released date if desired.

Requirement 07 - Publication Date

Published resources MUST include a publication date, with a value in the past, within the resource citation element of the record.

Draft records MAY include a publication date with a value in the future (i.e. if the publication date is known). They MUST NOT use a date in the past, as they will be considered published.

Requirement 08 - Point of Contact

Records MUST include MAGIC as a contact using the 'Point of Contact' role, within the resource citation element.

The contact value MUST be as per Appendix 2 - MAGIC Point of Contact Element.

Requirement 09 - Access Constraints

Records MUST include an access constraint, indicating who can access the resource.

Requirement 10 - Usage Constraints

Records MUST include a usage constraint, indicating the licence under which the resource can be used.

Requirement 11 - Progress Code

Records MUST include a progress code for both the resource and record, using one of these allowed options from the ISO 19115 'MD_ProgressCode' code list:

• 'completed'
• 'underDevelopment'

Requirement 12 - Update Frequency Code

Records MUST include an update frequency code for both the resource and record, using a value from the 'ISO 19115 MD_MaintenanceFrequencyCode' code list.

Requirement 13 - Lineage Statement

Non-collection records MUST include a lineage statement element describing the origins and sources used to create the resource.

Container record types MAY include this element if desired.

Requirement 14 - Geographic Extent

Records MUST include a bounding box element defining the geographic extent of the resource, with an extent identifier of 'bounding'.

Records MAY include additional extents (with geographic and/or temporal and/or vertical components) as desired.

Requirement 15 - Citation

Non-collection records MUST include a citation statement element describing how users must attribute the resource.

Container record types MAY include this element if desired.

Requirement 16 - Copyright Holder

Records MUST include a contact using the 'rightsHolder' role (ISO 19115 'CI_RoleCode' code list).

Appendices

Appendix 1 - Domain Consistency Element

{
  "identification": {
    "domain_consistency": [
      {
        "specification": {
          "title": {
            "value": "British Antarctic Survey (BAS) Mapping and Geographic Information Centre (MAGIC) Discovery Metadata Profile",
            "href": "https://metadata-standards.data.bas.ac.uk/profiles/magic-discovery/v2/"
          },
          "dates": {
            "publication": "2025-11-24"
          },
          "edition": "2",
          "contact": {
            "organisation": {
              "name": "Mapping and Geographic Information Centre, British Antarctic Survey",
              "href": "https://ror.org/01rhff309",
              "title": "ror"
            },
            "phone": "+44 (0)1223 221400",
            "address": {
              "delivery_point": "British Antarctic Survey, High Cross, Madingley Road",
              "city": "Cambridge",
              "administrative_area": "Cambridgeshire",
              "postal_code": "CB3 0ET",
              "country": "United Kingdom"
            },
            "email": "magic@bas.ac.uk",
            "online_resource": {
              "href": "https://www.bas.ac.uk/teams/magic",
              "title": "Mapping and Geographic Information Centre (MAGIC) - BAS public website",
              "description": "General information about the BAS Mapping and Geographic Information Centre (MAGIC) from the British Antarctic Survey (BAS) public website.",
              "function": "information"
            },
            "role": [
              "publisher"
            ]
          }
        },
        "explanation": "Resource within scope of British Antarctic Survey (BAS) Mapping and Geographic Information Centre (MAGIC) Discovery Metadata Profile.",
        "result": true
      }
    ]
  }
}

Appendix 2 - MAGIC Point of Contact Element

{
  "organisation": {
    "name": "Mapping and Geographic Information Centre, British Antarctic Survey",
    "href": "https://ror.org/01rhff309",
    "title": "ror"
  },
  "phone": "+44 (0)1223 221400",
  "address": {
    "delivery_point": "British Antarctic Survey, High Cross, Madingley Road",
    "city": "Cambridge",
    "administrative_area": "Cambridgeshire",
    "postal_code": "CB3 0ET",
    "country": "United Kingdom"
  },
  "email": "magic@bas.ac.uk",
  "online_resource": {
    "href": "https://www.bas.ac.uk/teams/magic",
    "title": "Mapping and Geographic Information Centre (MAGIC) - BAS public website",
    "description": "General information about the BAS Mapping and Geographic Information Centre (MAGIC) from the British Antarctic Survey (BAS) public website.",
    "function": "information"
  },
  "role": [
    "pointOfContact"
  ]
}