Page History

...

• Contacts:
  • Contacts can have different roles e.g. Editor, Owner, Principal Investigator, etc.
  • Make sure to have the following contacts assigned to your device
    • At least one Editor: an editor is allowed to modify the device/platform and its sub devices and acts as contact person. The editor may be inherited from the parent device/platform
    • At least one Owner:
      • “Institute” owning the device. Select your institute contact from the list of contacts or send a request to o2a-support (at) awi.de to do so, if it is not available
    • Add Contact person with role 'Principal Investigator' for the device who can either edit the device in SensorWeb or knows who to contact this for.
    • Add contact “polarstern dship” with role “dship connector” to have devices available in DSHIP
  • Note: Contacts with role 'Editor' or 'Data Provider' will have write access on the MOSAiC Central Storage in the respective Device Directory

• Collections: Add collection(s) to specify the project in which the sensor is being used. This facilitates the search for sensors used in a certain project and grouping sensors in AWIs data portal (data.awi.de)

• Versioning
  • Every time you add an action of type deployment, mount, calibration or commissioned, a version of your current sensor configuration is permanently stored
  • All versions get a citation with a persistent identifier (like DOI) and therefore can be referenced in publications
    • Because of that deletion of versions is always critical, because we never know, if they are already referenced in other publications
    • They can only be deleted by a system administrator
    • Just think about a version like a data publication
  • Enter changes in the order they were done on the device / platform
    • This is a best practice, because once created versions cannot be modified afterwards
  • Every device should be versioned before first device operation with action type ‚comissioned‘ and label ‚MOSAiC 122/Leg-No.‘

• Cloning (Copying)
  • A device / platform can be duplicated with all of it's attributes
  • Be sure to enter everything you want to be cloned before cloning

• Reassignment (Move device)
  • Every reassignment triggers the creation of unmount and mount events in the source and target devices / platforms by default
    • Event creation can be switched off, if you don't want this reassignment to be documented for the future

...