Date: Fri, 29 Mar 2024 06:56:37 +0100 (CET) Message-ID: <992939719.3207.1711691797258@confluencesrv1.awi.de> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3206_1062556413.1711691797257" ------=_Part_3206_1062556413.1711691797257 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In order to add certain =E2=80=98Actions=E2=80=99 to items, several ways= are available:
The actions
automatically create a new version of the item (including a handle, such= as this one: hdl.handle= .net/10013/sensor.1b1ff06f-dc5c-4246-8844-f4bb305c9512) to have
Since creating a new version can be omitted when reassigning an item, th= ere is still the chance to do so (just for the case you recognized it was m= istakenly without version) by manually create the mounting event and hence = triggering the creation of a version.
=E2=80=98Actions=E2=80=99 additionally give you as a user a chance to be= come more visible in DWS. Properly added missions make thi= s data stream pop up there in the facet =E2=80=98Mission=E2=80=99. Furtherm= ore entries of the types =E2=80=98Mission=E2=80=99 and =E2=80=98Deployment= =E2=80=99 are searchable in DWS.
|
---|
Field in DWS to filter for Acti= on Labels from registry.awi.de |
If the above mentioned facts were not convincing you to manage your meta= data, the standardized entries from registry.awi.de/api can be f= orwarded to other places with ease, e.g. applications that make use of= the API, such as Jupyter/R notebooks, knitr, webpages, portals or somethin= g alike.
|
---|
Adding new Actions in registry.awi.de |
When adding new events some fields are mandatory and some are not. Nonet=
heless it is strongly recommended to fill in every field, since several ser=
vices, such as autoQC
(spaces.awi.de/x/22WjEw) make use of it. Furthermor=
e, especially the spatial information can be used in map applications.
Name | Description | Mandatory/Optional |
---|---|---|
Label | reasonable, coherent, and unique name of the eve= nt | 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 circumst= ances, background, etc. | Optional |
Latitude | aka N or S | Optional |
Longitude | aka E or W | Optional |
Elevation | applies to depth too, below water surfaces rathe= r negative integers, else positive integers | Optional |
systemName | id | description | uuid |
---|---|---|---|
Calibration | 15 | The item was recalibrated, the re= spective Calibration certificates and/or associated documents should be sup= plied via the Resources tab in the upper navigation banner. | c922c7f9-a2d8-464c-8f30-3ae60a303= 94a |
Commissioned | 215 | This Event Type applies to large-= scale platforms, such as land-based stations, research vessels, and aircraf= ts. It describes the beginning of the operational use of this device. | 3a791fbc-f2c8-4277-91e7-2c68e8c7d= c55 |
Configuration | 317 | Describes a change in an items co= nfiguration (something new has been mounted, the item has been recalibrated= =E2=80=A6) | 9fc7575c-6125-4dc6-89a7-eee2eb257= 55b |
Decommissioned | 216 | This Event Type applies to large-= scale platforms, such as land-based stations, research vessels, and aircraf= ts. It describes the end of the operational use of this device. | 94ae38e6-8fda-4c07-b40c-018339828= 12f |
Deployment | 187 | A device is deployed, means it is= in operational use. Deployment applies to small-scale vehicles and ship-op= erated devices, such as CTD rosettes, buoys, etc.. | 047a4f46-020b-4187-808a-6f245caeb= bc3 |
Information | 50 | Describes issues associated with = this item relevant for its operation. Includes failure and maintenance info= rmation. | d865bf37-04c3-44f5-a474-0458dc68f= 915 |
Maintenance | 16 | The Event Type Maintenance descri= bes functional checks, servicing, repairing or replacing of parts. The devi= ce might still be operational, but the device&amp;amp;amp;amp;apos;= s measurements might be affected by means of maintenance. | d1a2a98a-8ad1-44a5-902f-9ce151326= 2cf |
Mission | 182 | A Mission refers to the device's = operation within a defined range of time and purpose. | 78318577-0e23-4dfe-ad2b-bfe6cb23b= 9a7 |
Mount | 25 | The device installed/attached to = a parental device. The Event Type Mount mostly applies to ship- and airborn= e sensors. | 13c8e2d6-a0ff-4612-bc7c-3d6540f52= 655 |
Partial_failure | 200 | The Event Type Partial Failure sh= ould be set if the device&amp;amp;amp;amp;apos;s functionality some= how is restricted or limited. | f663f3a3-78bc-4c47-a9eb-f14657190= 7e8 |
Processing | 470 | Used in laboratory context, when = samples run down a processing chain. | e45c70dc-5b6d-4ab9-a3eb-9d2c1597d= ad2 |
Recovery | 188 | When a device is retrieved from w= ater or ice the Event Type Recovery should be set. Then it is no longer ope= rational. This usually applies to buoys or moorings. | 6fac6351-0c4a-48c1-87e4-a5e721f9c= 1ae |
Total_failure | 201 | The Event Type Total Failure deno= minates the total loss of functionality of the respective device. Any re-us= e is foreclosed. | a6f292be-e5f6-4f4f-b34a-8e335675e= d92 |
Unmount | 26 | The device is extracted from a pa= rental device. The Event Type Unmount mostly applies to ship- and airborne = sensors. | 6f705b42-bc1f-4f47-89c8-7d89efabf= dd5 |