MAGIC Discovery (v2)

About

Details

Title: 'British Antarctic Survey (BAS) Mapping and Geographic Information Centre (MAGIC) Administration Metadata Profile'

Edition: 2

First Published: 2025-11-24

Last Revised: 2026-02-11

Licence: Open Government Licence

People

Authors:

• Felix Fennell

Reviewers:

• Louise Ireland

Contents

• About
• Rational
• Base standard
• Related profiles
• Changes from previous edition
  • Breaking changes
  • Major changes
  • Other changes
• Definition
• Example records
• Requirements
  • Overview
  • Requirement 01 - File Identifier
  • Requirement 02 - Domain Consistency
  • Requirement 03 - Hierarchy Level
  • Requirement 04 - Catalogue Identifier
  • Requirement 05 - Edition
  • Requirement 06 - Released Date
  • Requirement 07 - Publication Date
  • Requirement 08 - Point of Contact
  • Requirement 09 - Access Constraints
  • Requirement 10 - Usage Constraints
  • Requirement 11 - Progress Code
  • Requirement 12 - Update Frequency Code
  • Requirement 13 - Lineage Statement
  • Requirement 14 - Geographic Extent
  • Requirement 15 - Citation
  • Requirement 16 - Copyright Holder
• Appendices
  • Appendix 1 - Domain Consistency Element
  • Appendix 2 - MAGIC Point of Contact Element

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 and/or licensed information
• ensuring minimal information is available to enable future editing workflows
• ensuring minimal information is captured for data ownership and quality

In essence, this profile aims to provide a higher floor for record completeness, to ensure a useful 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.

Changes from previous edition

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

Breaking changes

• restricting progress code values to a limited subset (req. 11)
• added new citation requirement (req. 15)
• added new copyright holder requirement (req. 16)

Major changes

• domain consistency changed to reflect edition 2 (req. 02)
• corrected mistake in domain consistency explanation (was 'of British' should be 'of the British') (req. 02)
• allowing additional hierarchy levels (req. 03):
  • 'initiative'
  • 'feature'
  • 'fieldSession'
  • 'mapProduct' (local extension)
  • 'webMapProduct' (local extension)
• access constraints changed from authoritative to informative (administration metadata is now authoritative) (req. 09)
• access and usage constraints extended to cover the resource and metadata (req. 09 & 10)

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 administration metadata profile
• corrected mistake in released date profile obligation (was 'mandatory' should be 'conditional') (req. 06)
• corrected mistake in released date profile occurrence (was '1' should be '0..1') (req. 06)
• corrected mistake in publication date profile obligation (was 'mandatory' should be 'conditional') (req. 07)
• corrected mistake in publication date profile occurrence (was '1' should be '0..1') (req. 07)
• corrected mistake in lineage statement profile obligation (was 'mandatory' should be 'conditional') (req. 13)
• corrected mistake in lineage statement profile occurrence (was '1' should be '0..1') (req. 13)
• corrected mistake in geographic extent profile obligation (was 'mandatory' should be 'conditional') (req. 14)
• corrected mistake in geographic extent profile occurrence (was '1' should be '0..1') (req. 14)
• removed confusing authorisation justification in usage constraints (req. 10)

Definition

• Abstract (this document)
• JSON Schema

Example records

• minimal resource record (product):
  • JSON (BAS ISO 19115 schema)
  • XML
• minimal container record (collection):
  • JSON (BAS ISO 19115 schema)
  • XML

Requirements

Overview

Requirement	Element	Obligation (ISO)	Obligation (Profile)	Occurrence (ISO)	Occurrence (Profile)
01	File Identifier	Optional	Mandatory	0..1	1
02	Domain Consistency	Optional	Mandatory	0..*	1..*
03	Hierarchy Level	Optional	Mandatory	0..1	1
04	Data Catalogue Identifier	Optional	Mandatory	0..*	1..*
05	Edition	Optional	Mandatory	0..1	1
06	Released Date	Optional	Conditional	0..1	0..1
07	Publication Date	Optional	Conditional	0..1	0..1
08	Point of Contact	Optional	Mandatory	0..*	1..*
09	Access Constraint	Optional	Mandatory	0..*	1..*
10	Usage Constraint (Licence)	Optional	Mandatory	0..*	1..*
11	Process Code (Status)	Optional	Mandatory	0..1	1
12	Update Frequency Code	Optional	Mandatory	0..1	1
13	Lineage Statement	Optional	Conditional	0..1	0..1
14	Geographic Extent	Optional	Conditional	0..*	1..*
15	Other Citation Details	Optional	Conditional	0..1	0..1
16	Copyright Holder	Optional	Mandatory	0..*	1..*

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'
  • 'mapProduct' (local extension)
    • 'paperMapProduct' (local extension)
    • 'webMapProduct' (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, using a value that MUST be unique across all editions of a chronological series.

Requirement 06 - Released Date

Records for published resources (as determined by Requirement 07 - Publication Date) MUST include a released date.

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

Unpublished records MAY include a released date if desired.

Requirement 07 - Publication Date

Records for published resources MUST include a publication date, with a value in the past.

Unpublished records MAY include a publication date with a value in the future (i.e. in advance of publication) but 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 with the 'pointOfContact' role (from the ISO 19115 'CI_RoleCode' code list).

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
• the metadata (record) describing the resource

Requirement 10 - Usage Constraints

Records MUST include a usage constraint, stating the licence under which:

• the resource can be used
• the metadata (record) can be used

Requirement 11 - Progress Code

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

• 'completed'
• 'deprecated'
• 'onGoing'
• 'retired'
• 'superseded'
• 'underDevelopment'

Requirement 12 - Update Frequency Code

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

Requirement 13 - Lineage Statement

Resource record types MUST include a lineage statement describing the origins of the resource.

Container record types MAY include a lineage statement if desired.

Requirement 14 - Geographic Extent

Records MUST include an extent, with 'bounding' as an identifier, containing at least a geographic bounding box for the resource.

Records MAY include additional extent components (e.g. temporal), and/or other extents.

Requirement 15 - Citation

Resource record types MUST include a citation element, explaining how users should cite the resource.

Container record types MAY include this element.

Requirement 16 - Copyright Holder

Records MUST include at least one contact with the 'rightsHolder' role (from the 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 the 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"
  ]
}