diff --git a/guides/publish-and-share.qmd b/guides/publish-and-share.qmd index 86d87d34..82d1a3b2 100644 --- a/guides/publish-and-share.qmd +++ b/guides/publish-and-share.qmd @@ -108,14 +108,15 @@ 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} +```{.include shift-heading-level-by=2} ../topics/persistent-identifier.qmd ``` +## Licensing data and software ```{.include shift-heading-level-by=2} -../topics/data-and-software-licensing.qmd +../topics/data-licensing.qmd ``` ```{.include shift-heading-level-by=2} @@ -124,6 +125,6 @@ Instead of archiving research data in a data repository, you may choose to publi ## Dataset Registration -```{.include shift-heading-level-by=1} +```{.include shift-heading-level-by=2} ../topics/dataset-and-software-registration.qmd ``` diff --git a/topics/adding_a_license_github_plus.png b/public/github_file_creation_button.png similarity index 100% rename from topics/adding_a_license_github_plus.png rename to public/github_file_creation_button.png diff --git a/topics/data-and-software-licensing.qmd b/topics/data-and-software-licensing.qmd deleted file mode 100644 index 5de65063..00000000 --- a/topics/data-and-software-licensing.qmd +++ /dev/null @@ -1,25 +0,0 @@ ---- -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: - -* Can people make copies or even distribute copies -* Who should be contacted if you need access to re-use data -* Etc. - -![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/). - -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] - -[^1]: For the source code, see \ No newline at end of file diff --git a/topics/data-licensing.qmd b/topics/data-licensing.qmd new file mode 100644 index 00000000..55eefbdf --- /dev/null +++ b/topics/data-licensing.qmd @@ -0,0 +1,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 - information about software licensing can be found on the [software licensing](../topics/software-licensing.qmd) page). 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? +* 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. 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). + +## 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 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 diff --git a/topics/data-publication.qmd b/topics/data-publication.qmd index 1c888ec4..6cc38144 100644 --- a/topics/data-publication.qmd +++ b/topics/data-publication.qmd @@ -26,4 +26,4 @@ In addition to archiving research data in a data repository, you may choose to p - [Journal of Open Archaeology Data](https://openarchaeologydata.metajnl.com/) - [Journal of Open Psychology Data](https://openpsychologydata.metajnl.com/) -Archiving your data in a repository or publishing a data article are both ways to get a [Persistent Identifier for your data](../topics/persistent-identifier.qmd). It is also important to consider [Data and Software Licensing](../topics/data-and-software-licensing.qmd). +Archiving your data in a repository or publishing a data article are both ways to get a [Persistent Identifier for your data](../topics/persistent-identifier.qmd). It is also important to consider [Data Licensing](../topics/data-licensing.qmd) and [Software Licensing](../topics/software-licensing.qmd). diff --git a/topics/software-licensing.qmd b/topics/software-licensing.qmd index 57221ab9..c208076d 100644 --- a/topics/software-licensing.qmd +++ b/topics/software-licensing.qmd @@ -2,15 +2,17 @@ title: Software Licensing --- -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. +## Licensing software -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. +Publishing research software under an appropriate licence is crucial for its accessibility, usability, and further integration into research. Choosing a licence 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. -There are many licenses out there; below we list some very frequently used licenses in research software. However, if none of these licenses fit your case, there are several tools that can help you to [choose](https://choosealicense.com/) a suitable software license. If you need guidance in choosing a licence for your software, get in touch with the [RDM Support Desk](mailto:rdm@vu.nl?subject=Research%20Software). +A software licence 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 licences are as permissible as possible. + +There are many licences out there; below we list some very frequently used licences in research software. However, if none of these licences fit your case, there are several tools that can help you to [choose](https://choosealicense.com/) a suitable software licence. If you need guidance in choosing a licence for your software, get in touch with the [RDM Support Desk](mailto:rdm@vu.nl?subject=Research%20Software). ## MIT License -The [MIT License](https://mit-license.org) is a popular choice, due to its readability and permissiveness. It allows users to reuse the software for any purpose, including using, copying, modifying, and distributing it, provided they include the original copyright notice and license text. +The [MIT License](https://mit-license.org) is a popular choice, due to its readability and permissiveness. It allows users to reuse the software for any purpose, including using, copying, modifying, and distributing it, provided they include the original copyright notice and licence text. However, its permissiveness means that derivative works can be closed-source and do not need to mention that they use your code, which might not align with all scientific openness goals or general. @@ -24,19 +26,19 @@ This encourages collaborative improvement of software. Any software that include The [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0) allows for modification and distribution of the software and its derivative works, with the requirement that changes to the original code are documented. -It is a more complex license than the MIT License and can be incompatible with GPL-licensed software. The specifics of this go beyond the scope of the handbook. +It is a more complex licence than the MIT License and can be incompatible with GPL-licensed software. The specifics of this go beyond the scope of the handbook. -## Adding a license to GitHub +## Adding a licence to GitHub -On GitHub you add a license on creating a new repository, by selecting the license from the drop-down menu. If your repository already exists, add a new file called "LICENSE" using the "+"-button on top of the repository (see below). +On GitHub you add a licence on creating a new repository, by selecting the licence from the drop-down menu. If your repository already exists, add a new file called "LICENSE" using the "+"-button on top of the repository (see below). -![Location of file creation button](github_file_creation_button.png) +![Location of file creation button](../public/github_file_creation_button.png) -One the next page, start type LICENSE as the file name, and a button to "Choose a licence template" should automatically pop up. Follow the steps provided by GitHub to finish adding the license to the repository. +One the next page, start to type LICENSE as the file name, and a button to "Choose a license template" should automatically pop up. Follow the steps provided by GitHub to finish adding the licence to the repository. -You should now see your license shown on the main page of your repository. +You should now see your licence 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. \ No newline at end of file + * 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.