Intent:Expedition data management

How was there a data manager on board?

• The expedition leader of PS149 asked for funding for a data manager on his project.

Preparations before the expedition:

• all instruments/devices have to be in Registry so they can be used during the expedition
• only with a Registry ID, the device receives a folder in the MDM where data can be stored on the ship and transfer to land after the expedition
  • within ca 3 months before the expedition I gave a presentation to the participants about Registry, its documentation, how to register a device in Registry, how to create an account, etc.
  • there were after that many reminders to the participants to register their devices in Registry
  • As data manager of the expedition, I was also mission manager in Registry. That is a role for the expedition leader but he can ask that others may be added as mission manager for the mission in Registry.
    • by being mission manager was my task to add devices to the mission
    • in an excel sheet, the participants added their instruments with Registry ID, and these were later added by me into the mission.
• ADD HERE THE PRESENTATION FROM THE MEETING

Workshop in Trømsø two days before oficial start of expedition:

• the expedition leader organized a two days workshop/meeting where a lot of the training was done before we entered the ship, one of these workshops was data management related.
• The Data workshop was devided into two parts – the first part was a presentation where how the Events should be named for Registry and PANGAEA; how the folders for data storage in the MDM should be named and how data should be stored. The second part was a one to one meeting or me and a smaller group, where the participants could ask their questions about Registry, about events logging, solve their problems with device registration and ask whatever else they wanted.
  • In the first part we talked again about registering the devices, but the main message was how the events should be named:
    • Station label + device short name (as in Registry) + action –
      • e.g. PS149_13-1-snowpit-01
        • PS149_13-1 = staion label
        • -snowpit = device short name as in Registry
        • -01 = action/measurement/collection
    • In the workshop I also presented the excel table where after every ice station the participants should add their events with all the necessary metadata
      • the table was a compilation to result in two different data tables – one was the event table for Registry, the other was the station list for the cruise report.
      • ADD THE TABLE HEADER HERE.
    • Device folder on MDM: the device folder were names with the device short name as in Registry automatically, no chance of changing that.
      • the expedition leader requested that the participants would create folders inside the device folder with station label, and the data from each station would than be stored in the station folders:
        • e.g. MDM -> BEAST -> PS149_13-1 -> data collected
  • In the second part of the Data workshop the individual groups were visiting four different stations regarding survival, security, etc. and data
    • in this part they could ask questions about devices in or to be in Registry, how the events would be logged etc.
• ADD HERE THE PRESENTATION FROM THE WORKSHOP

Getting on board: ask the sysman to upload again the Registry list into DShip – and every time someone register a new device on board or forgot to add a device to the mission – ask the sysman to upload again the list from Registry.

After ice station day work participants should:

• fill up the events table
• mark on an image where they did measurements, collected samples, or deployed instruments, buoys, etc.

Data manager task after ice station work (during transit):

• collect the events table
• collect the image with the markings
• create a thematic map with the measurements locations in QGis
• collect the UTM coordinates from each measurement points in QGis
• calculate the relative distance in meters of the measurement points to the ship adding them to an excel table (which will be published together with the maps in PANGAEA soon)
• prepare the thematic maps to be added to the Cruise Report at the end of the expedition.
• create scrips that will read the events table, and via API upload the events into Registry.
• check if the events created by the participants are correct (following the request of the expedition leader)

After the expedition: