...
name | id | meta | uuid |
---|---|---|---|
public | 1 | Item is completly completely describe and in use | a080ff68-30b2-450a-9a44-06ecd244c0b7 |
construction | 2 | Item description is currently beeing being created | 380e59eb-5f70-4d6f-9f79-c212c5141e20 |
devicestore | 3 | Item is currently not on a mission | d251b7d5-3476-4606-81d4-1f76632eb802 |
decom | 4 | Item is retired and not used anymore | 8fa8fd50-a2bf-49ea-991d-03b85cee1b7f |
...
In sensor.awi.de the history per item is tracked. Two entities must be considered: history of item configurations and history of item operations.
In the UI always the most recent configuration of the item is displayed. Former item configurations are accessible via the dropdown menu (below the blue bar on the top). Each item version comes with a PID, such as https://hdl.handle.net/10013/sensor.8e03063e-6179-48b4-b626-a25573727623, thus you can specificly address and reference a certain setup of your device, e.g. in report reports or articles. This was used for example by Wulff, Lehmenhecker, and Hagemann (2016),, when they referenced https://doi.pangaea.de/10013/sensor.664525cf-45b9-4969-bb88-91a1c5e97a5b to describe configuration of an AUV.
Following the link leads to a former setup of the item. (link: https://hdl.handle.net/10013/sensor.9fd3386a-6c1a-4775-bcbb-cc5d50e27494)
For item operations the Actions (see https://spaces.awi.de/x/0oa0FQ) are the place to store and handle such things.
...