Skip to content

Commit db7f507

Browse files
committed
UPDATE:Communications Images
1 parent 79ca8c3 commit db7f507

8 files changed

Lines changed: 69 additions & 50 deletions

File tree

05_seminar3/readme.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ See
3131
- [`../99_resources/03_open_access/readme.md`](../99_resources/03_open_access/readme.md).
3232

3333
## Further reading:
34+
- [Open Science and Innovation](https://www.fosteropenscience.eu/node/2334) on the FOSTER portal.
3435
- [Modular design](https://en.wikipedia.org/wiki/Modular_design) enables interaction. If the interfaces in a modular system are clear, modules can be swapped in and out with ease.
3536
- Modular design has also started to appear in wind lidar:
3637
- The e-WindLidar data formats (See [§4.3 in ](https://zenodo.org/record/2478051) and [Lidaco](https://github.com/e-WindLidar/Lidaco)) enable much simpler data exchange.
90.2 KB
Loading
61.8 KB
Loading

07_seminar4/notes/online_comms.png

126 KB
Loading

07_seminar4/notes/readme.md

Lines changed: 49 additions & 41 deletions
Large diffs are not rendered by default.
117 KB
Loading

11_selfstudy5/readme.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Write up a short article about your research and publish it as part of your port
1717
_6 hours of extra credit are available for this work_
1818

1919
## Resources
20-
See [`../99_resources/07_data_management_plans/readme`](../99_resources/07_data_management_plans/readme).
20+
See [`../99_resources/07_data_management_plans/readme.md`](../99_resources/07_data_management_plans/readme.md).
2121

2222
## Further reading
2323

99_resources/08_case_studies/readme.md

Lines changed: 18 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,9 @@ We'll assume:
4444
- The status of the data - restricted or open - is irrelevant, as the data underlying the paper are not made available.
4545

4646
### Weaknesses
47-
The work has limited impact because others cannot leverage the work. They cannot repeat it or reuse the knowledge for other projects. All of this means that the work loses its impact very quickly.
47+
- The work has limited impact because others cannot leverage the work.
48+
- They cannot repeat it or reuse the knowledge for other projects.
49+
These factors mean that the work loses its impact very quickly.
4850

4951
### Possible improvements
5052
- The paper could have been published as open access.
@@ -84,13 +86,13 @@ We'll assume
8486
- The paper combines the methods, data processing, and results.
8587
- They wrote their code in a proprietary language.
8688
- They didn't make clear what data and code were used to create their published data.
87-
- The communications
89+
- The communications go a long way towards promoting the paper, but the lack of a "call to action" or actionable insights means that any buzz that they generate is wasted.
8890

8991
### Possible improvements
90-
- The data, tools, and results could have been separated out into diffferent publications, each with their own DOI.
92+
- The data, tools, and results could have been separated out into different publications, each with their own DOI.
9193
- They could have written their processing code using an open language like `Python` or `R`.
92-
- They could have mitigated repeatability challenges by uing [GitHub's _releases_](https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/about-releases), which capture a repository status at a specific point in time.
93-
- They could have used better-suited data file formats, for example NetCDF. They should have also made sure they used the file type favored by their community.
94+
- They could have mitigated repeatability challenges by using [GitHub's _releases_](https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/about-releases), which capture a repository status at a specific point in time.
95+
- They could have used better-suited data file formats, for example NetCDF. They should have also made sure they used the file type favoured by their community.
9496

9597
## Publishing a paper that uses data that is partly or totally restricted
9698
As researchers continue through their career they will often start to work with data that is commercially sensitive or includes some kind of intellectual property. This data must be protected. However, researchers need to be recognised for their skills and given credit for their work. How can we reconcile the need for security with the need for visibility?
@@ -102,20 +104,28 @@ We'll assume
102104
| | | | |
103105
|---------------|--------------|---|---|
104106
| Goal | | To advance their field of research despite working with restricted data |
105-
| Concept | | |
106-
| Approach | | Publish the data, methods, and results seperately. |
107+
| Concept | | Publish the data, methods, and results separately. |
108+
| Approach | | Publish the data, methods, and results separately. |
107109

108110
We now need to apply FAIR and R5 to each of the publications coming out of the project.
109111

110112
### A data publication
113+
114+
The authors write a short paper about their data and check it in to Zenodo.org
115+
111116
| | | | |
112117
|---------------|--------------|---|---|
113118
| Data | **F**indable | The data are checked in to a repository where they are assigned a DOI. The authors provide multiple keywords that include broad or generic terms and detailed terms. | ![](yes.png) |
114119
| | **A**ccesible | The authors restrict access to the data, but the metadata describing it are kept open access. | ![](yes.png) |
115120
| | **I**nteroperable | The authors provide metadata to the repository. The repository is using the [Dublin core](https://en.wikipedia.org/wiki/Dublin_Core), so the metadata are standardised. They choose keywords from a domain-specific list (see e.g. [the wind energy taxonomy of topics](http://data.windenergy.dtu.dk/ontologies/view/wtax/en/)). | ![](yes.png) |
116121
| | **R**eusable | The data repository includes a license and information about the origin of all data. | ![](yes.png) |
122+
| Code | Re-runnable (R<sup>1</sup>) | The authors include short examples of how to extract data from the repository. |
123+
| | Repeatable (R<sup>2</sup>) | The authors provide a release that corresponds to the published data and paper. | ![](yes.png) |
124+
| | Reproducible (R<sup>3</sup>) | The authors included test data with passing criteria. Other users can therefore check the data. | ![](yes.png) |
125+
| | Reusable (R<sup>4</sup>) | The data is stored using self-describing a standard data format (e.g. NetCDF) | ![](yes.png) |
126+
| | Replicable (R<sup>5</sup>) | The work can be replicated by other researchers (using their own data). | ![](yes.png) |
117127

118-
R<sup>1</sup> through R<sup>5</sup> are not applicable at this point.
128+
| Communications | | The authors decide to present their work at conferences. To increase attendance they promote their work through social media. They provide links to their paper as well. | ![](caution.png) |
119129

120130

121131
### A methods publication

0 commit comments

Comments
 (0)