At the moment we are facing issues with a certain GitLab CI Runner (hifis-runner-manager-1) that execute your GitLab CI pipelines. We are working on it to bring them back to service again. Please excuse the inconveniences.

README.md 3.91 KB
Newer Older
Timm Schoening's avatar
Timm Schoening committed
1
> **Preamble:** We strive to make marine image data [FAIR](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/metadata-profiles-fdos/-/blob/master/FAIR-marine-images.md). We maintain - here in this repository - [data profiles](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/metadata-profiles-fdos) to establish a common language for marine imagery, we develop best-practice [operating procedures](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/standard-operating-procedures) for handling marine images and we develop [software tools](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/software/mar-iqt) to apply the vocabulary and procedures to marine imagery.
Timm Schoening's avatar
Timm Schoening committed
2

Timm Schoening's avatar
Timm Schoening committed
3
# Introduction
Timm Schoening's avatar
Timm Schoening committed
4
Achieving FAIRness and Openness of (marine) image data requires structured and standardized metadata on the image data itself and the visual and semantic image data content. This metadata shall be provided in the form of FAIR digital objects (FDOs). The content of this repository describes how FDOs for images (aka iFDOs) shall be structured. If you want, an iFDO is a human and machine-readable file format for an entire image set, except that it does not contain the actual image data, only references to it!
Timm Schoening's avatar
Timm Schoening committed
5
6

## Delicious (marine) image data
Timm Schoening's avatar
Timm Schoening committed
7
8
9
iFDOs consist of various metadata fields. Some are required, some are recommended, some are optional. You will only achieve FAIRness of your image data with the required core fields populated. You will only gain visibility and credit for your image data with the recommended capture fields populated. And you will only have awesome image data in case you also populate the content fields. As a bonus you can add your own domain-specific optional fields.
<img style="margin: auto 0" src="https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/metadata-profiles-fdos/-/raw/master/graphics/delicious_iFDOs_CCC.png" title="Delicious iFDOs" width="800"><br>
An iFDO file can consists of a header and item information part. For the core iFDO fields, the header part contains all metadata information that is identical for all the image items. The image item information part contains all the information where the individual images require their specific metadata value. An example is the coordinate: for a moving camera, all image items require their own image-latitude value. In case of a stationary camera, the image-set-latitude value can be used instead.
Timm Schoening's avatar
Timm Schoening committed
10

Timm Schoening's avatar
Timm Schoening committed
11
## iFDO sections
Timm Schoening's avatar
Timm Schoening committed
12
13
14
- **Core fields (required)**: [iFDO core](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/metadata-vocabulary-profile/-/blob/master/MareHub_AGVI_iFDO-core.md)
- **Capture fields (recommended)**: [iFDO capture](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/metadata-vocabulary-profile/-/blob/master/MareHub_AGVI_iFDO-capture.md)
- **Content fields (optional)**: [iFDO content](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/metadata-vocabulary-profile/-/blob/master/MareHub_AGVI_iFDO-content.md)
Timm Schoening's avatar
Timm Schoening committed
15

Timm Schoening's avatar
Timm Schoening committed
16
## Version
Timm Schoening's avatar
Timm Schoening committed
17
Continuous versioning of the FDOs is given by the commit hashes. Releases with numerical versioning will be created upon major changes.
Timm Schoening's avatar
Timm Schoening committed
18

Timm Schoening's avatar
Timm Schoening committed
19
## Metadata vocabulary terms
Timm Schoening's avatar
Timm Schoening committed
20
The following wording will be used throughout the documents.
Timm Schoening's avatar
Timm Schoening committed
21
22
23
24
- images: photos (still images) and videos (moving images) acquired by cameras, recording the optical spectrum of light (http://purl.org/dc/dcmitype/Image)
- still image: A static visual representation (http://purl.org/dc/dcmitype/StillImage)
- moving image: A series of visual representations imparting an impression of motion when shown in succession (http://purl.org/dc/dcmitype/MovingImage)
- image set: a collection of at least one, but usually many, images (http://purl.org/dc/dcmitype/Collection)
Timm Schoening's avatar
Timm Schoening committed
25
- `<tag>`: represent various placeholders for information (like variables)
Timm Schoening's avatar
Timm Schoening committed
26
27
28
29
- `<project>`: the project, expedition or cruise acronym
- `<event>`: part of a project, this refers to the station number in marine sciences
- `<sensor>`: a unique, human-readable identifier (or nickname) for the data acquisition device / camera