MAGIC Discovery (v1)
Last updated
Last updated
The base ISO 19115 requirements are very minimal and not sufficient to meet MAGIC's needs, including:
ensuring records comply with the (internal URL)
ensuring (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 licensed 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.
This profile is based on:
0..1
1
0..*
1..*
0..1
1
0..*
1..*
0..1
1
0..1
0..1
0..1
0..1
0..*
1..*
0..*
1..*
0..*
1..*
0..1
1
0..1
1
0..1
0..1
0..*
1..*
Records MUST include the file identifier element, using a value that MUST be unique across all records.
Records MUST include a domain consistency data quality element, stating the record complies with this profile.
Records MUST include the hierarchy level element.
The element value MUST be one of these allowed options:
'collection'
'dataset'
'product'
'series'
Records MUST include an identifier element, identifying the resource within the BAS Data Catalogue.
The identifier MUST use these values:
URL: the Catalogue item URL for the record, in the form: https://data.bas.ac.uk/items/{file_identifier}
namespace: 'data.bas.ac.uk'
Records MUST include an edition within the resource citation element, using a value that MUST be unique across all editions of the resource.
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.
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 not be considered as draft.
Records MUST include MAGIC as a contact using the 'Point of Contact' role, within the resource citation element.
Records MUST include an access constraint, indicating who can access the resource.
Records MUST include a usage constraint, indicating the licence under which the resource can be used.
Records MUST include a progress code for both the resource and record, using a value from the 'ISO 19115 MD_ProgressCode' code list.
Records MUST include an update frequency code for both the resource and record, using a value from the 'ISO 19115 MD_MaintenanceFrequencyCode' code list.
Non-collection records MUST include a lineage statement element describing the origins and sources used to create the resource.
Collection records MAY include this element if desired.
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.
the standard
the BAS Data Catalogue (internal URL)
(this document)
Minimal product: |
Minimal collection: |
The element value MUST be as per .
value: the value of
The contact value MUST be as per .