Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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)
  • Item States:
    • Construction:

      • Seen only by “editor” of this device under “My Devices”
        • not Ready for publication

      Public:

      • Seen by everybody (no Login)
        • Ready for publication
        • Public devices should not be deleted. (Measured data would loose metadata)

      Store:

      • Device they are not in use
      • Device at the store
  • 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/‚PS122-Leg-No.‘', e.g. "PS122-1" for Leg 1.


  • 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

...