generated from rstudio/bookdown-demo
-
Notifications
You must be signed in to change notification settings - Fork 4
/
01-intro.Rmd
125 lines (68 loc) · 12.2 KB
/
01-intro.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
# Overview {#overview}
## Ambition in the Open Music Europe Grant Agreement
[Open Music Europe](https://openmuse.eu/) aims to contribute to the aim of creating a decentralised European intelligence hub where centralised data collection and analysis have failed in the music industry during the past 20 years.
We envision the Open Data Observatory as a decentralised, complementary service to the ESSnet system (Eurostat and the national statistics offices) and the planned, centralised European Music Observatory (EMO). […] We plan to implement the Open Data Observatory as an open-source, public-facing solution working in synergy with the EMO.
We will create `reproducible` “dynamic policy documents” that can be transferred from one country to another or scaled up from one country to a group of countries or even the entire European Union, and recast with little effort after the inception of new data every year, due to their very high level of data/output standardisation and interoperability.
Instead of creating a large budget, ad-hoc valuation reports, these reports, with their automatic data harvesting and processing, can be recast annually with little further investment, or they can be transferred from Hungary to Bulgaria, from Slovakia to Lithuania.
## Methodology in the Open Music Europe Grant Agreement
The `Level 3` version of the *Open Policy Analysis* (`OPA`) Guidelines gives practical guidance on how to improve the transparency and replicability of policy-making work with a scientific underpinning. The OPA guidelines go farther than current Horizon Europe recommendations, subjecting policy research and deliberation to standards as rigorous as those used in e.g. open-source software development and open science peer review.
The guidelines consist of three layers:
- [x] `open materials` (i.e., the evidence considered in policy) | check out the materials of this handbook.
- [x] `open analysis` (the analytical procedures to which the evidence is subject); see for example [D 1.3 Report on the European Music Economy](https://openmuse.dataobservatory.eu/resources/report-european-music-economy/) | [Slides](https://openmuse.dataobservatory.eu/slides/report-european-music-economy/) | [file folder](https://github.com/dataobservatory-eu/report-european-music-economy) | [long term storage](https://zenodo.org/record/6464782#.ZCCWP9JBzlg) | [README](https://github.com/dataobservatory-eu/report-european-music-economy/blob/main/README.md).
- [x] `open output` (the indicators, recommendations, etc. derived from the analysis): we syncronize them with libraries via [OpenAIRE](https://www.openaire.eu/) and our visual assets and cultural data via [Europeana](https://www.europeana.eu/en) aggregators.
Each level must be fully replicable. Establishing a clear link between input and output by displaying how the output changes under `Open Music Europe` uses `Open Policy Analysis` to create policy-relevant indicators. [@OPA_guardia_et_al_2020] and they are fully in line with the Open Science objectives of the European Union
[@reproducibility_scientific_results_eu_2020].
```{r opafig-wp, fig.align='center', fig.cap='Our ambition to increase transparency with introducing the Open Policy Analysis into the European music policies and collaborative data use in the European industry.', echo=FALSE}
knitr::include_graphics(here::here("png", "opa_framework.png") )
```
Open Music Europe furthermore ensures that all materials, analysis, and outputs meet the `FAIR principles` enshrined in Horizon Europe and the EU’s open science agenda and will be submitted as best practices to the *Knowledge4Policy* [K4P](https://knowledge4policy.ec.europa.eu/home_en) Portal horizontal knowledge areas on Evidence-Informed Policy Making, Composite Indicators, Modelling, and AI Watch.
In Europe, the European Commission launched the platform, along with several initiatives to make EU-funded research more accessible, notably, with changing some financial guidelines for its research program, and amending the [Open Data Directive](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32019L1024) in 2019.
The subsequent chapters of this Manual show how we will comply with both FAIR and OPA by making our documents and files [Findable](#findable) in a way that meets open policy analysis compliance, make them [Interoperable](#interoperability) for machines and researchers, [Accessible](#accessible) for human and algorithms, and [Reusable](#reuse) for human and automated use.
These efforts toward radical transparency will help ensure open deliberation and consensus-forming among stakeholders. Putting evidence-based policymaking into practice in music research, we will establish a precedent for its incorporation as a keystone of the social sciences and digital humanities more broadly.
## OPA
The [OPA Guidelines](https://www.bitss.org/opa/community-standards/) feature nine steps for implementation, grouped by their relation to the three key principles of OPA: `Open Output`, `Open Analysis`, and `Open Materials`. Each step is modular, meaning it can be implemented independently from the rest, and features three gradual levels of rigor. Analysts can adopt each step at varying levels of rigor, depending on what is appropriate for their work. Status quo in policy analysis practices should be interpreted as Level 0.
You can become a signatory of the `OPA Guidelines` by adding your name (or the name of your organization, if you sign as an organizational representative) to [this form](https://docs.google.com/forms/d/e/1FAIpQLSdn63GXNpK6CsggWg_0Z0MrhE9zPuKmv8rocoEfsDrScRdaLQ/viewform) and including a statement in policy reports indicating they were developed in accordance with the OPA Guidelines (e.g., “This analysis complies with level 3 of the Open Policy Analysis (OPA) Guidelines developed by BITSS”). Second, you can submit your feedback to these Guidelines to [BITSS Project](https://www.bitss.org/opa/community-standards/).
## Documents, Word Processing, Manuscripts, Blogposts
We must make our documents Findable, Interoperable, Accessible and Reusable. We introduce the [tidy text](#interoperability-tidy-text) concept in the [Interoperability](#interoperability) chapter.
Interoperability in this case making your text editing simpler. Regardless your use of Word, Grammarly, Libre, or a markdown editor, we would like you to keep it as simple that it can be translated to markdown notation, which then can create automatically correct, beautiful Word, PDF, or LaTeX documents.
Markdown is a very simple text notation, similar to the earlier manuscript markup languages used by book editors. You can learn it in 1-2 hours, but even if you do not use it, you should always check that your formatting remains simple enough to be translated (simplified) to markdown. An introduction to using markdown is in \@ref(tidy-text) [Tidy Text](#tidy-text). You can get the concept in 10 minutes with [Dillinger](#try-markdown).
::: {.rmdnote data-latex="{note}"}
See the first version of our slide templates [here](https://openmuse.dataobservatory.eu/slides/open-music-europe-document-template/), and visit our template folder ([Open Music Europe dissemination and communications assets](https://github.com/dataobservatory-eu/open_music_europe_templates/)). Help our colleagues at Synyo to make this template more aesthetic, more usable, and more interoperable by sending issues and big reports [here](https://github.com/dataobservatory-eu/open_music_europe_templates/issues).
:::
## Datasets, Tables, Tabular Data
We must make our documents Findable, Interoperable, Accessible and Reusable. We introduce the [tidy data](#interoperability-tidy-text) concept in the [Interoperability](#interoperability) chapter, and go into further depth (only to be used for the Data Management Plan, and some quantiative task of WP1, WP2, WP3, and the programimng parts of WP3) in the \@ref(tidy-data) [Tidy data](#tidy-data) separate chapter.
For laypersons, tidy data ensures that your data is very easy to import into a relational database (SQL, etc) or it can be read into Excel, OpenOffice, SPSS or STATA without a hiss. Keeping your data is keeping your data simple, and will save you countless hours in the [Data Sisyphus](https://dataandlyrics.com/post/2021-07-08-data-sisyphus/).
## Presentations
Presentations are special types of documents where the visual elements dominate. Making them truly interoperable is a big challenge, because we expect them to work on a projector, on a Windows laptop, an Apple desktop, a Linux server, on a tablet, smartphone.
::: {.rmdnote data-latex="{note}"}
See the first version of our slide templates [here](https://openmuse.dataobservatory.eu/slides/open-music-europe-slide-template/), and visit our template folder ([Open Music Europe dissemination and communications assets](https://github.com/dataobservatory-eu/open_music_europe_templates/)). Help our colleagues at Synyo to make this template more aesthetic, more usable, and more interoperable by sending issues and big reports [here](https://github.com/dataobservatory-eu/open_music_europe_templates/issues).
:::
## Working Folders (repositories)
Our file folders, or repositories, are stored on Microsoft's Github. They work similarly to a Google Drive or a Dropbox, but with some further featured that makes them compliant with the EU's FAIR and the OPA.
The use of a standardised file structure and the use of an open, selfcontained folder with a readme file is central to \@ref(open-collaboration) [Open collaboration](#open-collaboration), i.e., or project management philosophy, as well as to compliance with the \@ref(findable) [F - Findable](#findable) principle in the European open science requirements and in OPA.
- [x] Access to them is not proprietary, it requires the https protocol (or SSH)
- [x] They are version controlled, and protected for deleting, overwriting
- [x] Many people can work on them without disturbing each other.
- [x] WP leaders and task leaders can assign tasks connected to files (such as issues, check out the improvement issues to make our Word and PPTX files truly interoperable).
- [x] Competing ideas can be disussed under the issues, or help can be asked for, even outside of our work groups or consortia.
- [ ] You need a program to sync it to your computer (Similarly to DropBox o Microsoft's OneDrive)
The downside is a bit more learning:
- [x] You do not work in the same folder, like in Google Drive, in the cloud, you always create your copy ('fork') first, so that you are protected from accidentally overwriting; this is both a blessing and a curse for beginners.
- [ ] The sync is never automatic: you always have to approve every download and upload
- [ ] Resolving conflicts (you changed something in a text that somebody else also changed in a different way) requires experience.
You find more information on how to use Git and GitHub in the [Collaboration tools](#collaboration-tools) chapter.
## Final folders for syncronization and publication
Our long term storage is [Zenodo](https://zenodo.org/communities/music_observatory/?page=1&size=20), the repository system of [OpenAIRE](https://www.openaire.eu/) and
CERN, the European Organization for Nuclear Research.
Zenodo is an extremely useful tool:
- [x] It places our work directly into global library catalogues, if it is high-enough capacity
- [x] It connects it to people who cite us, it connects it with similar books, articles, datasets
- [x] It provides for a truly open an interoperable access point.
Yet, it is no exception to the garbage-in-garbage-out principle. In WP4 we develop tools that helps to make out a lot more from your blogposts, presentations, manuscripts, final articles, and datasets on Zenodo and the global knowledge graphs. See more in \@ref(tidy-data) [Tidy data](#tidy-data).
```{r reportoneconomicszenodo, echo=FALSE}
knitr::include_graphics(here::here(file.path("png", "report-european-music-economy_0_1.png") ))
```
Check out our [Digital Music Observatory collection](https://zenodo.org/communities/music_observatory/) and this particular [storage folder](https://zenodo.org/record/6464990#.ZCCdGNJBzlg).
## Biographies
We use [ORCiD](https://orcid.org/) because we rely on Zenodo as an open source repository, but we can include almost any academic badge on your profile that you like, just make sure that you have an ORCiD ID, too.
## Photographs