Project specific best practices and recommendations are listed under "Projects"
You will be requested to assign a short name for all items you want to create. Items are uniquely identified via a local URN identifier (URN means Uniform Resource Locator) using the item type and individual short name syntax .. Example: vessel:ms_hel:fb_740602 points to the ferrybox on MS Helgoland.
While creating a short name for your device, keep in mind that the short names cannot be modified once created because they are in-use within INGEST and STORAGE (for setting the path to data files for a particular item). Be also aware that you cannnot create items with the same short name under one parent item.
SENSOR allows us to keep track of the items owned by a given institute. For this sake, fill out under the "Contacts" tab the name of the institute to which the item should be affiliated to (use the role "owner"). If your institute is not listed yes, please contact sensor (at) awi.de.
In addition to entering the "owner" of an item, you are also requested to enter the name of contact informaiton of PI, engineer-in-charge, data scientist, etc
We recommend you to use the autocompletion functionality (simply type the first 3 characters of the station label as listed in PANGAEA's expedition catalogue) to confortably get the metadata fields under "Action" automated filled out for you and this way avoiding possible typos. The autocompletion functionality for station metaddata is supported for all large and middle-sized german vessels (Polarstern, Sonne, Metero, Alkor, Heincke, Poseidon) Shipborne and Aircraftborne items represent a special use-case in SENSOR because the metadata is being maintained by a third-party company. In case the device you will be using in a given research vessel or aircarft is not listed yet, please contact sensor (at) awi.de |
In real life devices arebeing 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.