diff --git a/01-OS-and-FAIR.html b/01-OS-and-FAIR.html index dd0e204..07e0ba4 100644 --- a/01-OS-and-FAIR.html +++ b/01-OS-and-FAIR.html @@ -885,10 +885,219 @@
Software code (the text) automatically gets the default copyright +protection which prevents others from copying or modifying it. Only by +adding the explicit licence you can permit re-use by others.
+Data, being factual, cannot be copyrighted. So why, do we +need a license?
+While the data itself cannot be copyrighted, the way how it is +presented can be. The extend to which it is protected needs ultimately +to be settled by the court.
+The “good actors” will restrain from using your data to avoid “court” +risks. The “bad actors” will either ignore the risk or can afford the +lawyers fees.
+## Exercise 4: Example of FAIR data (4 min)
+Zenodo is general data repository. Have a look at the dataset record +with COVID-19 data: https://doi.org/10.5281/zenodo.6339631
+Identify how each of F.A.I.R principles has been met.
Hint: navigate to linked github record to easily access the README
+file
The FAIR acronym is sometimes accompanied with the following labels: +* Findable - Citable * Accessible - Trackable and countable * +Interoperable - Intelligible * Reusable - Reproducible
+## Solution
+FAIR does not mean Open. Actually, FAIR guideline +only requires that the metadata record is always accessible. For +example, the existence of the data can be known (their metadata), the +data can have easy to use PID to reference them, but the actual data +files can only be downloaded after the login and authorization.
+However, if data are already in the FAIR form, i.e. accessible over +the internet, in interoperable format and well documented, then it is +almost effortless to “open” the dataset and make it available to the +whole public. The data owner can do it any time when he no longer +perceives oppening as a risk.
+At the same time, Open data which does not follow FAIR guidelines +have little value. If they are not well described, not in open formats +then they are not going to be re-used even if they were made “open” by +posting them on some website.
+Further reading/links:
+ - [Challenges & benefits of OS](https://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.3000246)
+ - [Centre for Open Science](https://www.cos.io/)
+ - [Ted talk supporting OS](https://www.youtube.com/watch?v=c-bemNZ-IqA)
+Which of the following statements about the OS movement are +true/false?
+Content of this episode was adapted from:
+ * Wiki [Open Science](https://en.wikipedia.org/wiki/Open_science)
+ * [European Open Science Cloud](https://www.eosc-hub.eu/open-science-info)
+ * [Science is necessarily collaborative - The Biochemist article](https://portlandpress.com/biochemist/article/42/3/58/225220/Science-is-necessarily-collaborative).
+Content from Using Markdown
Last updated on 2024-02-24 | diff --git a/instructor/01-OS-and-FAIR.html b/instructor/01-OS-and-FAIR.html index a59af2d..49053d0 100644 --- a/instructor/01-OS-and-FAIR.html +++ b/instructor/01-OS-and-FAIR.html @@ -887,10 +887,219 @@
Software code (the text) automatically gets the default copyright +protection which prevents others from copying or modifying it. Only by +adding the explicit licence you can permit re-use by others.
+Data, being factual, cannot be copyrighted. So why, do we +need a license?
+While the data itself cannot be copyrighted, the way how it is +presented can be. The extend to which it is protected needs ultimately +to be settled by the court.
+The “good actors” will restrain from using your data to avoid “court” +risks. The “bad actors” will either ignore the risk or can afford the +lawyers fees.
+## Exercise 4: Example of FAIR data (4 min)
+Zenodo is general data repository. Have a look at the dataset record +with COVID-19 data: https://doi.org/10.5281/zenodo.6339631
+Identify how each of F.A.I.R principles has been met.
Hint: navigate to linked github record to easily access the README
+file
The FAIR acronym is sometimes accompanied with the following labels: +* Findable - Citable * Accessible - Trackable and countable * +Interoperable - Intelligible * Reusable - Reproducible
+## Solution
+FAIR does not mean Open. Actually, FAIR guideline +only requires that the metadata record is always accessible. For +example, the existence of the data can be known (their metadata), the +data can have easy to use PID to reference them, but the actual data +files can only be downloaded after the login and authorization.
+However, if data are already in the FAIR form, i.e. accessible over +the internet, in interoperable format and well documented, then it is +almost effortless to “open” the dataset and make it available to the +whole public. The data owner can do it any time when he no longer +perceives oppening as a risk.
+At the same time, Open data which does not follow FAIR guidelines +have little value. If they are not well described, not in open formats +then they are not going to be re-used even if they were made “open” by +posting them on some website.
+Further reading/links:
+ - [Challenges & benefits of OS](https://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.3000246)
+ - [Centre for Open Science](https://www.cos.io/)
+ - [Ted talk supporting OS](https://www.youtube.com/watch?v=c-bemNZ-IqA)
+Which of the following statements about the OS movement are +true/false?
+Content of this episode was adapted from:
+ * Wiki [Open Science](https://en.wikipedia.org/wiki/Open_science)
+ * [European Open Science Cloud](https://www.eosc-hub.eu/open-science-info)
+ * [Science is necessarily collaborative - The Biochemist article](https://portlandpress.com/biochemist/article/42/3/58/225220/Science-is-necessarily-collaborative).
+Content from Using Markdown
Last updated on 2024-02-24 | diff --git a/instructor/key-points.html b/instructor/key-points.html index c989351..094487c 100644 --- a/instructor/key-points.html +++ b/instructor/key-points.html @@ -259,7 +259,13 @@
.md
files for episodes when you want static
diff --git a/key-points.html b/key-points.html
index 259d0ae..abbe8dc 100644
--- a/key-points.html
+++ b/key-points.html
@@ -257,7 +257,13 @@ .md
files for episodes when you want static
diff --git a/md5sum.txt b/md5sum.txt
index 7e02c6c..f410972 100644
--- a/md5sum.txt
+++ b/md5sum.txt
@@ -4,7 +4,7 @@
"config.yaml" "78527fcaaab88132938042a98642abe4" "site/built/config.yaml" "2024-02-23"
"index.md" "4e900476217a21b1af6c5ef17c813b22" "site/built/index.md" "2024-02-24"
"links.md" "8184cf4149eafbf03ce8da8ff0778c14" "site/built/links.md" "2022-04-22"
-"episodes/01-OS-and-FAIR.md" "6b03c2c0786b43527d7ebe6aa2ec8c5a" "site/built/01-OS-and-FAIR.md" "2024-02-25"
+"episodes/01-OS-and-FAIR.md" "2eaeb21d1d2adb284d5279b9f6556bf5" "site/built/01-OS-and-FAIR.md" "2024-02-25"
"episodes/xTemplate.md" "6c55d31b41d322729fb3276f8d4371fc" "site/built/xTemplate.md" "2024-02-24"
"instructors/instructor-notes.md" "63eca1767f6b7a73a86bb27da69bf71b" "site/built/instructor-notes.md" "2024-02-23"
"learners/reference.md" "1c7cc4e229304d9806a13f69ca1b8ba4" "site/built/reference.md" "2023-03-16"
diff --git a/pkgdown.yml b/pkgdown.yml
index f9a6262..ccc34db 100644
--- a/pkgdown.yml
+++ b/pkgdown.yml
@@ -2,5 +2,5 @@ pandoc: 2.19.2
pkgdown: 2.0.7
pkgdown_sha: ~
articles: {}
-last_built: 2024-02-25T00:11Z
+last_built: 2024-02-25T00:15Z