Intern:Project data management


 * Keep project members informed about the system, the data flow and the availability of the data.
 * Explain possible access right definitions and password protection.
 * Explain that proper citation and persistent identification of data is assured.
 * Avoid high-end project web pages.
 * Concentrate on data collection, technical quality, complete metainformation, import and availability.
 * Define a data policy in agreement with the partners.
 * Define the goals of the project data management: availability, long-term archiving, publication, compilations ...
 * Define parameters with unit as required by the project, relate parameters to a keyword in pangaea and add a dynamic link on the project web pages.
 * Collect metainformation related to the project: adress of institutions, scientists with email and phone number and provide dynamic list through the project web pages.
 * Keep track on activities, e.g. expeditions, cruises; import sample or station lists when expedition report is available. First import step is to archive metadata of events (labels, latitude/longitude, elevation, date/time etc). Assure consequent usage of event labels throughout the project!
 * Keep track on publications; provide a dynamic list of project related publications.
 * Specify existing data sets usefull to the project and its availability.
 * Keep track on the scientific groups providing data, its structure, parameters, amount and date of delivery. Keep contact with the groups and ensure proper data flow and collection. Personal meetings might be better than email or phone.
 * List possible groups/PI with related data contributions on a web page and povide status of availability.
 * Give feedback to data contributors about the availability of their data; always ask for proof read.
 * Definition of the data flow should include
 * identification of existing and new data,
 * quality control and proof read,
 * formats for import,
 * information about citation and DOI,