Data licensing

guides/publish-and-share.qmd

@@ -108,11 +108,12 @@ Instead of archiving research data in a data repository, you may choose to publi
 * [Journal of Open Archaeology Data](https://openarchaeologydata.metajnl.com/)
 * [Journal of Open Psychology Data](https://openpsychologydata.metajnl.com/)
 
-#### Persistent Identifier
+### Persistent Identifier
 
 ```{.include shift-heading-level-by=3}
 ../topics/persistent-identifier.qmd
 ```
+### Licensing data and software
 
 ```{.include shift-heading-level-by=2}
 ../topics/data-and-software-licensing.qmd

topics/data-and-software-licensing.qmd

@@ -4,22 +4,29 @@ title: Data Licensing
 
 ## Licensing the data
 
-A data licence agreement is a legal instrument that lets others know what they can and cannot do with your research data (and any documentation. scripts and metadata that are published with the data). It is important to consider what kind of limitations are relevant. An important component can be a guideline on how people should cite the dataset. Other components could be:
+A data licence agreement is a legal instrument that lets others know what they can and cannot do with your research data (and any documentation, scripts and metadata that are published with the data). It is important to consider what kind of limitations are relevant. Usually, at least the following questions are considered:
 
-* Can people make copies or even distribute copies
-* Who should be contacted if you need access to re-use data
-* Etc.
+* Can people make copies or even distribute copies?
+* Do others (and you) reusing the dataset need to acknowledge you as the author of the original dataset? (This is called Attribution.)
+* Do others (and you) who reuse the dataset and/or make derivatives of the dataset need to share their work under a similar licence? (This is called Share-Alike.)
+* Can others (and you) use your dataset commercially? (A restriction on commercial use is called Non-Commercial.)
+* Can others (and you) create a new work based on the dataset? (This is called a Derivative.)
+
+The considerations above are the 'building blocks' that [Creative Commons licences](https://creativecommons.org/share-your-work/cclicenses/) use. There are also other considerations, and also other licences.
 
 ![An image of open data, made up of public domain icons](../public/Open_Data_CC0_Wikidata.gif)
 
-In principle, Dataverse allows you to choose your terms of use. Some data repositories require you to use a certain licence if you want to deposit your data with them. At [Dryad](https://datadryad.org/), for example, all datasets are published under the terms of [Creative Commons Zero](https://creativecommons.org/share-your-work/public-domain/cc0/) to minimise legal barriers and to maximise the impact for research and education. Some funders may also require that you publish the data as open data. **Open data** are data that can be freely used, re-used and redistributed by anyone - subject only, at most, to the requirement to attribute and share alike ([Open Knowledge International definition)](https://opendatahandbook.org/guide/en/what-is-open-data/). If you need help with drawing up license agreements, you can contact the [IXA office](https://www.ixa.nl/).
+In principle, Dataverse allows you to choose your terms of use. If you publish your data in Yoda, there is [guidance](https://yoda.vu.nl/site/getting-started/selecting-license.html) available on how to choose a licence and how to customise licences. Some data repositories require you to use a certain licence if you want to deposit your data with them. At [Dryad](https://datadryad.org/), for example, all datasets are published under the terms of [Creative Commons Zero](https://creativecommons.org/share-your-work/public-domain/cc0/) to minimise legal barriers and to maximise the impact for research and education. Some funders may also require that you publish the data as open data. **Open data** are data that can be freely used, re-used and redistributed by anyone - subject only, at most, to the requirement to attribute and share alike ([Open Knowledge International definition)](https://opendatahandbook.org/guide/en/what-is-open-data/). If you need help with drawing up licence agreements, you can contact the [VU's legal office](https://vu.nl/en/research/portal/research-impact-support-portal/check-legal-support).
+
+## Licensing software
+Licences that are suitable for data are usually not suitable for software. Giving your software a licence is very important, because it informs other users how they may use your software and for what you take responsibility. You also usually choose a licence for your software at the very beginning of your software development process. You can read more about software licensing on the [Software Licensing page](../topics/software-licensing.qmd).
 
 Additional websites and tools:
 
 * [Explanation about copyrights and licences](https://www.youtube.com/watch?v=_J26POpb-rQ&feature=youtu.be) by a professor from Leiden University (English subtitles available)
 * The [Guide to Creative Commons for Scholarly Publishing and Educational Resources](https://zenodo.org/record/4090923#.X6ugz1DvJPY) by NWO, VSNU and the University and Royal Libraries
 * [DCC how-to guide on licensing research data](https://www.dcc.ac.uk/guidance/how-guides/license-research-data), a guide that links to the Creative Commons website, where many terms are explained
 * [Open Data Commons Public Domain Dedication and License (PDDL)](https://opendatacommons.org/licenses/pddl/)
-* [EUDAT B2SHARE license selection wizard](https://ufal.github.io/public-license-selector/), which Pawel Kamocki (et al.) released under an open source license.[^1]
+* [EUDAT B2SHARE licence selection wizard](https://ufal.github.io/public-license-selector/), which Pawel Kamocki (et al.) released under an open source licence.[^1]
 
-[^1]: For the source code, see <https://github.com/ufal/public-license-selector/>
+[^1]: For the source code, see <https://github.com/ufal/public-license-selector/>

topics/software-licensing.qmd

@@ -2,6 +2,8 @@
 title: Software Licensing
 ---
 
+## Licensing software
+
 Publishing research software under an appropriate license is crucial for its accessibility, usability, and further integration into research. Choosing a license usually happens right when you start developing the software or when you put it in a public repository, rather than when the software is finished and fully baked. 
 
 A software license states how other people may re-use your code and under which circumstances. For research software, it is recommended (and often required by funders) that licenses are as permissible as possible. 
@@ -39,4 +41,4 @@ You should now see your license shown on the main page of your repository.
 ## Further considerations
 
  * If you are reusing software or libraries written by someone else, you must stick to the clauses of the licence given to the original software/library;
- * When choosing a licence, do not just think about what _others_ may do with the software, but also what _you_ might want to do with the software in the future.
+ * When choosing a licence, do not just think about what _others_ may do with the software, but also what _you_ might want to do with the software in the future.