...
...
Since creating a new version can be omitted when reassigning an item, there is still the chance to do so (just for the case you recognized it was mistakenly without version) by manually create the mounting event and hence triggering the creation of a version.
‘Actions’ additionally give you as a user a chance to become more visible in DWS. Properly added missions make this data stream pop up there in the facet ‘Mission’. Furthermore entries of the types ‘Mission’ and ‘Deployment’ are searchable in DWS.
Field in DWS to filter for Action Labels from sensor registry.awi.de |
If the above mentioned facts were not convincing you to manage your metadata, the standardized entries from sensor registry.awi.de/api can be forwarded to other places with ease, e.g. applications that make use of the API, such as Jupyter/R notebooks, knitr, webpages, portals or something alike.
...
Adding new Actions in sensor registry.awi.de |
When adding new events some fields are mandatory and some are not. Nonetheless it is strongly recommended to fill in every field, since several services, such as autoQC
(spaces.awi.de/x/22WjEw) make use of it. Furthermore, especially the spatial information can be used in map applications.
Name | Description | Mandatory/Optional |
---|---|---|
Label | reasonable, coherent, and unique name of the event | Mandatory |
Event Type | see table below | Mandatory |
From | point in time when the event started | Mandatory |
To | point in time when the event ended | Mandatory |
Description | detailled description of the event, its circumstances, background, etc. | Optional |
Latitude | aka N or S | Optional |
Longitude | aka E or W | Optional |
Elevation | applies to depth too, below water surfaces rather negative integers, else positive integers | Optional |
...