generated from ubvu/handbook-template
-
Notifications
You must be signed in to change notification settings - Fork 21
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #13 from ubvu/Elisa-on-GitHub-patch-1
Elisa on GitHub patch 1
- Loading branch information
Showing
2 changed files
with
52 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
# Data Publication | ||
|
||
## Open Access and Open Science | ||
Open Access publishing means that you make your publication freely accessible online to everyone without restrictions. The Vrije Universiteit believes that government-funded research should be available free of charge to as many people as possible. To that end, the VU Library offers a guide on how to go about Open Access Publishing. | ||
|
||
Open Access publishing is one component of Open Science. The European Commission has defined open science as follows: “Open Science represents a new approach to the scientific process based on cooperative work and new ways of diffusing knowledge by using digital technologies and new collaborative tools. The idea captures a systemic change to the way science and research have been carried out for the last fifty years: shifting from the standard practices of publishing research results in scientific publications towards sharing and using all available knowledge at an earlier stage in the research process”. (Definition taken from Nationaal Programma Open Science.) This includes making openly available research data, methods and documentation where possible. As such, RDM and the practices outlined in this LibGuide are a precondition of Open Science. You can read more about Open Science in the Netherlands on the website of the Nationaal Programma Open Science and join the Open Science Community Amsterdam, the community of VU employees interested in Open Science (joint with the University of Amsterdam). | ||
|
||
## Publishing your data in a data journal | ||
Instead of archiving research data in a data repository, you may choose to publish an article about your data collection. This is not necessarily common for all disciplines. Some examples of data journals where you can publish your data and dataset, are: | ||
|
||
Scientific Data - Nature | ||
Geoscience Data Journal | ||
Gigascience | ||
Dataset Papers in Science | ||
Journal of Physical and Chemical Reference Data | ||
Earth System Science Data | ||
Journal of Open Archaeology Data | ||
Journal of Open Health Data | ||
Journal of Open Psychology Data | ||
|
||
## What is a persistent identifier? | ||
A persistent identifier (PID) is a durable reference to a digital dataset document, website or other object. It is a kind of ISBN for digital files. By using a persistent identifier, you make sure that your dataset will be findable well into the future. A DOI or Handle are the commonly used PIDs. The data archiving options at the VU commonly offer DOIs. | ||
|
||
Most data archives or repositories offer a persistent identifier and generate this automatically when research data are archived. For example, this is the case for DataverseNL at the VU. In Yoda at the VU, assigning a PID is possible, but does not happen automatically. Please get in touch with the RDM Support Desk if you have questions about assigning a PID when you archive data in Yoda. | ||
|
||
## 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. | ||
|
||
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, for example, all datasets are published under the terms of Creative Commons Zero 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). If you need help with drawing up license agreements, you can contact the IXA office. | ||
|
||
Additional websites and tools: | ||
|
||
Explanation about copyrights and licences by a professor from Leiden University (English subtitles available) | ||
The Guide to Creative Commons for Scholarly Publishing and Educational Resources by NWO, VSNU and the University and Royal Libraries | ||
DCC how-to guide on licensing 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) | ||
EUDAT B2SHARE license selection wizard, which Pawel Kamocki (et al) released under an open source license. | ||
|
||
|
||
## Licensing software | ||
As with data, it is important to license any software that you write for your research. Some basic information about software licensing can be found here, but it is also important to keep the following in mind: | ||
|
||
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; | ||
If you used proprietary software to write your code (e.g. SPSS syntax), your options in choosing a licence will probably be limited; | ||
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. | ||
|
||
If you need guidance in choosing a licence for your software, get in touch with the [RDM Support Desk](mailto:rdm@vu.nl). |