Difference between revisions of "Data Collaboration Agreement"

(Created page with " <span style="font-family:Arial,Helvetica,sans-serif;"><span style="font-size:medium"><span style="caret-color:#000000"><span style="color:#000000">When you are starting a col...")
 
 
Line 14: Line 14:
 
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">it is something concrete you can show to a legal department or data expert in your institution, should you be in doubt of what is acceptable.</span></span>  
 
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">it is something concrete you can show to a legal department or data expert in your institution, should you be in doubt of what is acceptable.</span></span>  
  
==== <span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;"><span style="caret-color:#000000"><span style="color:#000000">'''Make sure all policies are respected'''</span></span></span></span> ====
+
=== <span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;"><span style="caret-color:#000000"><span style="color:#000000">'''Make sure all policies are respected'''</span></span></span></span> ===
  
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">List all policies and requirements that are applicable to the project and make sure the DMP is aligned with and satisfy all of them</span></span>
+
<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">List all policies and requirements that are applicable to the project and make sure the DMP is aligned with and satisfy all of them.</span></span>
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">Depending on the scope and size of the project, you might have to draft a legal agreement for the project collaboration, in that case make sure that data is also covered by this agreement</span></span>  
 
  
==== '''<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;"><span style="caret-color:#000000"><span style="color:#000000">What to include</span></span></span></span>''' ====
+
<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">Depending on the scope and size of the project, you might have to draft a legal agreement for the project collaboration, in that case make sure that data is also covered by this agreement. Consult with your legal department and do this as early as possible, it might help if even at&nbsp;this stage you have written down first what you want to be included.</span></span>
  
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">the copyright/ownership of the data should be clearly stated,</span></span>  
+
=== '''<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;"><span style="caret-color:#000000"><span style="color:#000000">What to include</span></span></span></span>''' ===
  
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">any ethical or security considerations</span></span>  
+
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">the copyright/ownership of the data should be clearly stated;</span></span>
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">license to be used for data research output</span></span>  
+
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">any ethical or security considerations;</span></span>  
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">where the data produced by the project will be stored and how the access to this storage is managed</span></span>  
+
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">license to be used for data research output;</span></span>  
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">how the data will be published at the end of the project: what subset, which repository, format etc</span></span>  
+
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">where the data produced by the project will be stored and how the access to this storage is managed;</span></span>  
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">where the data will be archived at the end of the project: what subset of the data should be kept and for how long, which archive and how the access will be managed</span></span>  
+
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">how the data will be published at the end of the project: what subset, which repository, format etc;</span></span>  
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">if there is going to be any embargo, both at the end of the project or to share data internally</span></span>  
+
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">where the data will be archived at the end of the project: what subset of the data should be kept and for how long, which archive and how the access will be managed;</span></span>  
 +
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">if there is going to be any embargo, both at the end of the project or to share data internally.</span></span>  
  
 
<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;"><span style="caret-color:#000000"><span style="color:#000000">If the project has many collaborators, then it is also worth to set up some rules or template to define how data is contributed to the project, in particular if more than one person is likely to work on the same data:</span></span></span></span>
 
<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;"><span style="caret-color:#000000"><span style="color:#000000">If the project has many collaborators, then it is also worth to set up some rules or template to define how data is contributed to the project, in particular if more than one person is likely to work on the same data:</span></span></span></span>
  
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">rules around directory structure and file naming conventions</span></span>  
+
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">rules around directory structure and file naming conventions;</span></span>  
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">which format/metadata should be used when creating a file</span></span>  
+
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">which format/metadata should be used when creating a file;</span></span>  
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">permissions to apply to file/directory</span></span>
+
*<span style="font-size:medium;"><span style="font-family:Arial,Helvetica,sans-serif;">permissions to apply to file/directory.</span></span>  
 +
 
 +
[[Category:Data induction]]

Latest revision as of 23:18, 7 July 2021

When you are starting a collaboration with someone else, be it a single researcher, a research group, a different institution or a stakeholder, you need to have a clear agreement around data.

The context and the scope of the collaboration project will determine what you might need to do. In any case you should have a clear understanding of how data is expected to be managed and shared by anyone in the project.

Minimum requirements

Draft a data management plan and get everyone to agree to it, while this won’t have legal standing:

  • it is something anyone can get back to easily;
  • it will work as a guideline around data for anyone in the project;
  • it will avoid future disagreements, or should some arise help in solving them;
  • it will help individuating potential issues with your data before you even start the project;
  • it is something concrete you can show to a legal department or data expert in your institution, should you be in doubt of what is acceptable.

Make sure all policies are respected

List all policies and requirements that are applicable to the project and make sure the DMP is aligned with and satisfy all of them.

Depending on the scope and size of the project, you might have to draft a legal agreement for the project collaboration, in that case make sure that data is also covered by this agreement. Consult with your legal department and do this as early as possible, it might help if even at this stage you have written down first what you want to be included.

What to include

  • the copyright/ownership of the data should be clearly stated;
  • any ethical or security considerations;
  • license to be used for data research output;
  • where the data produced by the project will be stored and how the access to this storage is managed;
  • how the data will be published at the end of the project: what subset, which repository, format etc;
  • where the data will be archived at the end of the project: what subset of the data should be kept and for how long, which archive and how the access will be managed;
  • if there is going to be any embargo, both at the end of the project or to share data internally.

If the project has many collaborators, then it is also worth to set up some rules or template to define how data is contributed to the project, in particular if more than one person is likely to work on the same data:

  • rules around directory structure and file naming conventions;
  • which format/metadata should be used when creating a file;
  • permissions to apply to file/directory.