The MCS is the central storage place for your raw data with an automatic back-up of the data. After each leg The data are taken home on tape were they will be made available to the MOSAiC consortium via web access.

The MCS is divided into two areas, the 'platforms' area and the 'workspace' area. Both areas are automatically connected to the virtuals virtual machines (VM) acquired via marketplace.awi.de (see Get virtual machines for instructions). Your own computers can be connected by mounting the areas as shares or using an ftpsftp-client . For detailed information have a look at !Connect to MCS on boardto access mosaic-dat.org (see Accessing MOSAiC data on land (@AWI)for details). 

Platforms area

• The MCS directory structure is closely connected to the SENSOR web and the DShip ActionLog. Directory structure follows the URN assigned to the devices in SENSOR.
  
• ONLY devices entered in SENSOR which are set to 'public'  and have the contact 'polarstern dship' with role 'dship connector' assigned will be can be imported into the MCS directory structure
• ONLY users entered as 'Editors' or 'Data Providers' of the specific device in SENSOR have the right to upload and modify data in to their respective device directories. This can however not be done directly. Please contact the data representative of your group or the data supporter if you have questions regarding the writing access to the MCSsee  Upload MOSAiC data to the MCS on land for instructions how to upload data to the platforms area.
• The platforms area is READABLE by ALL participants MOSAiC users.
  

If there are subdevices attached to your device they will appear under the folder of your parent device. Every device and subdevice will have a folder called 'exdata' were you are supposed to copy your raw data to. It is up to you and your data structure to decide whether raw data will all be stored under the parent device or individually under the folders of the subdevices.

...

For every device operation you are logging logged in DShip (see DShip stepwise manual under DShip ActionLog manual) on board during the expedition a folder with the device operation ID will be was attached to the 'exdata' folder of your device / subdevice. Raw data obtained during the specific device operation must be uploaded (automatically or manually by Data PI) to the respective subdirectory.

If you need to add a missed device operation after the end of the expedition please refer to Update or add DSHIP-Device Operations for past legs for instructions.

Workspace area

All participants have READ access to the workspace area. There is a back-up of the workspace area too and it will be taken home and made available after each leg. This is the place to store documents, joined presentation etc. which you want to keep. The public folders under \\fs-polarstern.de\poldata$\public which you may also get access to via connect to Polarstern public servers ARE NOT back-up and will be deleted after each cruise.

...