This profile together with the E-ARK CITS Geospatial document describes the root METS document for an IP conforming to the E-ARK CITS Geospatial.
An extension schema with the added attributes for use in this profile.
The schema is used with a namespace prefix of sip.
An extension schema with the added attributes for use in this profile.
The schema is identified using the namespace prefix csip.
The filepath must be decoded consistently throughout all file references within the information package.
Describes the type of the alternative record ID.
Describes the type of a note for an agent.
Lists the names of specific E-ARK content information type specifications supported or maintained in this METS profile.
Declares the categorical classification of package content.
Describes the uses of the file group `<fileGrp>` that are supported by the profile.
Own names should be placed in an own extending vocabulary.
All information recorded within the portion of a conforming METS document defined using the Simple DC XML Schema must be employ ISO 639-2 language codes within the 'language' element.
Describes the status of the descriptive metadata section (dmdSec) which is supported by the profile.
The value is set to "https://geospatial.dilcis.eu/profile/E-ARK-GEOSPATIAL-ROOT.xml".
The `mets/@TYPE` attribute is set to the value "Geospatial Data".
The `mets/@csip:CONTENTINFORMATIONTYPE` attribute is set to the value "GeoData".
The `mets/@csip:OTHERCONTENTINFORMATIONTYPE` attribute is not to be used.
The Geospatial root METS document metsHdr element should comply with metsHdr requirements in the CSIP profile.
The Geospatial root METS document metsHdr element should comply with metsHdr requirements in the SIP profile.
The Geospatial root METS document dmdSecr element should comply with dmdSec requirements in the CSIP profile.
The Geospatial root METS document dmdSec element should comply with dmdSec requirements in the SIP profile.
The Geospatial root METS document amdSec element should comply with amdSec requirements in the CSIP profile.
In Geospatial it is required that any rights or digital provenance metadata that is general to the package can be held within the root metadata folder and that any rights or digital provenance metadata that is specific to the data held in the representation should be held in the representation metadata folder.
The eHEALTH1 root METS document amdSec element should comply with amdSec requirements in the CSIP profile.
In eHEALTH1 it is required that any rights or digital provenance metadata that is general to the package can be held within the root metadata folder and that any rights or digital provenance metadata that is specific to the data held in the representation should be held in the representation metadata folder.
There MUST be a minimum of one mets/fileSec/fileGrp[@USE='Representations']/@csip:CONTENTINFORMATIONTYPE with the value “GeoData” as taken from the CSIP Vocabulary for Detailed Content Type that direct to the representation METS.xml in the representation folder containing geospatial data.
The value of the attribute `mets/fileSec/fileGrp/@csip:CONTENTINFORMATIONTYPE` is set to "GeoData".
There must be a discrete representation `div` element for each representation.
Section not defined or used in CSIP, additional own uses may occur.
Information regarding the structural links is found in the METS Primer
Section not defined or used in CSIP, additional own uses may occur.
Information regarding the behavior section is found in the METS Primer
There MUST be a minimum of one representation and, therefore minimum of one Package METS.xml and a minimum of one Representation METS.xml in a CITS Geospatial compliant package.
The Information Package MAY contain a separate representation of the same data, containing geospatial data in its original format
Every geospatial dataset MUST be accompanied with a metadata file, that describes the dataset with the basic required information
Documentation covering all representations in the Information package SHOULD be placed in /documentation on package level
Note that any documentation pertaining to the transferred content is referenced within the representation METS.
A document containing definitions and descriptions of feature types, its feature attributes and feature attributes related to all the geospatial records in the Information Package MUST be provided
A standardised machine-readable feature catalogue SHOULD be provided in the Information Package
Documentation, describing elements of a feature catalogue, not compliant with GEO_27 (a non standardised machine- readable feature catalogue) SHOULD be provided in Documentation/structure folder on the package level
A document describing relationships between multiple geospatial entities or geospatial and non-spatial records SHOULD be provided in the Information Package
If a document describing the logical model exists it MUST be provided in a documentation/structure folder
If a standardised machine-readable version of a document describing the logical model exists it MUST be provided in representations/[RepresentationName]/documentation/structure
A document describing the structure of geospatial records in the GIS System MAY be provided in the Information Package. A standardised machine-readable version is preferred.
An image displaying the overall view or a representative section of any geospatial dataset MUST be provided in the Information Package and placed in a documentation/rendering folder
A document describing visualisation rules and configurations SHOULD be provided in the Information Package
If a document describing visualisation rules and configurations exists it MUST be provided in a documentation/rendering folder
Information product examples based on geospatial record or records example SHOULD be provided in the Information Package
If information product examples exists they MUST be provided in the Information Package in a documentation/rendering folder
Documentation regarding the original system, where geospatial records were used, SHOULD be provided in the Information Package in a documentation/behaviour folder
If documentation regarding the original system exists it MUST be provided in a documentation/behaviour folder
Documentation on the logic of common queries and algorithms used for analysis, transformation, creation, and maintenance of geospatial records SHOULD be provided in the Information Package
If documentation on the logic of common queries and algorithms exists it MUST be provided in a documentation/behaviour folder
Code of queries and algorithms used with the geospatial records in the Information Package MAY be provided in the Information Package
If code of queries and algorithms used with the geospatial records exists it MUST be provided in a documentation/behaviour folder
Contextual documentation covering all representations in the Information package SHOULD be placed in documentation/other on package level
Geospatial metadata in non-long-term preservation representations MAY be stored in its original form or as documentation. However, formats need to comply with the archival guidelines (stored in approved long-term preservation formats).
Requirements not stated in CITS Geospatial
Requirements not stated in CITS GEospatial