You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 5
Next »
CREATING METADATA WITH CONTEXT |
---|
Before getting started make sure you discuss your particular use case with one of the chief editors listed under SENSOR page. You should also visit the our YouTube channel, in particular watch the ones we recommend. So that you will be able to easily find your device using the facetted search make sure the chief editor has created for you in advance the following attributes - the tag for "Collection"
- the tag for your "Institute"; in case your affiliation is different form the institute which owns the device, make sure this is also created. In addition to entering your own role (example PI, tehcnical, etc) you are requested to enter also the name of the institute which owns the device.
|
SHIP-MOUNTED SENSORS |
---|
Ship-mounted sensors represent a special use-case in SENSOR.awi.de because the metadata is being maintained by a company. In case the device you will be using in a given research vessel is not listed yet, please contact o2a-support(at)awi.de |
BOOKKEEPING DEPLOYMENTS AND CALIBRATIONS |
---|
In real life devices are being deployed in well-defined actions (e.g. action log from DSHIP) along with fixed payload of sensors. The data from the individual sensors are then stored in repositories like PANGAEA. In order to link the dataset to the information from SENSOR to a given event/action, it is important that you select the action of type deployment (=mount, commisioned). This will trigger the generation of a version of the device (including respective sensors) for the point in time a deployment action was carried out. In the new version you will find a cite-enabled PID (in this case a hnadle) for the instrument along with a recommended citation style. THe PID should be provided during dataset submission. In the PANGAEA example https://doi.pangaea.de/10.1594/PANGAEA.857507 the handle hdl:10013/sensor.664525cf-45b9-4969-bb88-91a1c5e97a5b points to SENSOR metadata specific for action/event Because calibrations often involve changes in the data output, it is important to also document these as a stand-along action. In particular in this case, we remind you to additionally upload calibration certificates or documents. |
CREATING A VERSION and PID |
---|
The creation of metadata version along with a persistant identifier (PID) of type handle is optional but recommended for action types "Deployment" and "Calibration". If you need to delete a given version/PID, please contact o2a-support(at)awi.de |
DEVICE NAMING CONVENTION |
---|
You will be asked to create a short and long name for your device. Keep in mind that the short names cannot be modified once created because they are in-use at the storage level. |
CLONING A BUOY OR MOORING |
---|
Realising the certain platforms like buoys and morrings hav |