├── .github
└── ISSUE_TEMPLATE
│ ├── bug_report.md
│ └── feature_request.md
├── 3rd-BEXIS-2-User-and-Developer-Conference.md
├── 5th-LEARN-workshop-2017.md
├── 8th-Wikidata-birthday.md
├── ASAPbio-Preprint-Curation-and-Review-Design-Sprint-2020.md
├── ArchivesSpace-Online-Forum-2019-emergencies.md
├── ArchivesSpace-Online-Forum-2019-wikis.md
├── ArchivesSpace-Online-Forum-2019.md
├── Beilstein-Open-Science-Symposium-2020.md
├── CCTB-2021-FAIR-Ethics.md
├── Creative-Commons-Summit-2015.md
├── Creative-Commons-Summit-2020.md
├── DSI-Lunch-Learn-April-2019.md
├── DSI-Presidential-Fellows-Orientation-August-2019.md
├── ECSA-2018-Citizen-science-and-Open-science.md
├── ECSA-2018-IAS.md
├── ECSA-2018-Usability.md
├── ECSA2016.md
├── ECSA2018.md
├── EGI-Community-Forum-2015.md
├── Endangered-Data-Week-UVA-2018.md
├── Environmental-Health-Seminar-Env-H-580-on-2019-01-31.md
├── FORCE-2018-1-minute-madness-remote.md
├── FORCE-2018-1-minute-madness.md
├── FORCE-2018-jrost.md
├── FORCE-2018-research-performed-last-week.md
├── FORCE-2018-research-published-last-week.md
├── FORCE-2018-wikidata-wikibase.md
├── FORCE-2018.md
├── FSCI-2017.md
├── FSCI-2018.md
├── Fachtagung-Katastrophenvorsorge-2020.md
├── Force-2017-Wikimania-in-Africa.md
├── Force-2017-discovery-tools.md
├── ICEI2018-SDGs.md
├── ICEI2018-citizen-science.md
├── ICEI2018-research-ecosystem.md
├── ICEI2018.md
├── IDCC17.md
├── IMED-2016.md
├── International-Data-Week-2018.md
├── JLab-AI-Lunch-Series.md
├── JROST-2020.md
├── July-2020-Climate-Reality-Leadership-Corps-Global-Training.md
├── JupyterCon-2017.md
├── JupyterCon-2020.md
├── LICENSE
├── MozOpenLeaders-2017.md
├── New-Arctic-Bridging.md
├── Open-Science-Jetzt-Vienna-2015.md
├── OpenCon-2016.md
├── OpenCon-satellite-Leipzig-2015.md
├── PIDapalooza-2016.md
├── PIDapalooza-2018.md
├── PIDapalooza-2019.md
├── PIDapalooza-2021.md
├── PIDapalooza.md
├── README.md
├── SNF-Workshop-on-Open-Data-in-Science-2015.md
├── SORTEE-2021.md
├── Sage-Assembly-2017.md
├── SciDataCon-2018-Wikidata.md
├── SciDataCon-2018-data-sharing.md
├── SciDataCon-2018-maDMPs-for-disaster-data-management.md
├── SciDataCon-2018.md
├── SciDataCon2016.md
├── Summer-2020-Climate-Reality-Leadership-Corps-Global-Training.md
├── UVA-Datapalooza-2017.md
├── WCSE.md
├── WeMissiPRES-2020.md
├── WikiCite-Cologne-2020.md
├── Wikimania-2016.md
├── data-science-in-climate-and-climate-impact-research.md
├── neuromatch3.md
└── recordings.md
/.github/ISSUE_TEMPLATE/bug_report.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Bug report
3 | about: Create a report to help us improve
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Describe the bug**
11 | A clear and concise description of what the bug is.
12 |
13 | **To Reproduce**
14 | Steps to reproduce the behavior:
15 | 1. Go to '...'
16 | 2. Click on '....'
17 | 3. Scroll down to '....'
18 | 4. See error
19 |
20 | **Expected behavior**
21 | A clear and concise description of what you expected to happen.
22 |
23 | **Screenshots**
24 | If applicable, add screenshots to help explain your problem.
25 |
26 | **Desktop (please complete the following information):**
27 | - OS: [e.g. iOS]
28 | - Browser [e.g. chrome, safari]
29 | - Version [e.g. 22]
30 |
31 | **Smartphone (please complete the following information):**
32 | - Device: [e.g. iPhone6]
33 | - OS: [e.g. iOS8.1]
34 | - Browser [e.g. stock browser, safari]
35 | - Version [e.g. 22]
36 |
37 | **Additional context**
38 | Add any other context about the problem here.
39 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature_request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Feature request
3 | about: Suggest an idea for this project
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Is your feature request related to a problem? Please describe.**
11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12 |
13 | **Describe the solution you'd like**
14 | A clear and concise description of what you want to happen.
15 |
16 | **Describe alternatives you've considered**
17 | A clear and concise description of any alternative solutions or features you've considered.
18 |
19 | **Additional context**
20 | Add any other context or screenshots about the feature request here.
21 |
--------------------------------------------------------------------------------
/3rd-BEXIS-2-User-and-Developer-Conference.md:
--------------------------------------------------------------------------------
1 | *[About](#about)・[Abstract](#abstract)・[Dedication](#dedication)・[Contact](#contact)*
2 |
3 | # Opening up the research data life cycle
4 |
5 | ## Abstract
6 |
7 | More and more aspects of the research data life cycle involve some form of sharing - be it the protocols used to generate the data, the software to analyze it, metadata about the data, the data itself or other aspects of its life cycle, from ethical review to citizen science. This talk zooms in on some examples in different stages of different data life cycles and explores how the changing dynamics of data sharing interact with the dynamics of doing research more generally.
8 |
9 | ## The research data life cycle
10 |
11 | - can be framed in [many ways](https://www.google.de/search?q=%22data+life+cycle%22)
12 | - ([UVA example](http://data.library.virginia.edu/data-management/lifecycle/))
13 | - key components: plan **・** get permissions **・** get funding **・** get infrastructure **・** collect metadata **・** collect data **・** process data **・** analyze data **・** *publish* **・** curate data **・** preserve data **・** reuse metadata **・** find data **・** access data **・** reuse data **・** reproduce data **・** delete data
14 | - exact arrangement can and does vary
15 | - frequent 'rinse and repeat'
16 |
17 | ## What does it mean to open it up?
18 |
19 | - no single *publishing* step within the cycle, since every intermediate step is an opportunity to share
20 | - [video](https://www.youtube.com/watch?v=LwW1-X3glak)
21 |
22 | ## Some of my activities in this space
23 |
24 | - helping to improve [data sharing in public health emergencies](http://www.who.int/bulletin/volumes/95/4/17-192096/en/)
25 | - working on [making data mangement plans machine actionable, versioned and public](https://doi.org/10.3897/rio.3.e13086)
26 | - helped shape the [Open Science Prize](http://openscienceprize.org/)
27 | - helping to explore [technical aspects of preprint services in the life sciences](https://doi.org/10.3897/rio.3.e11825)
28 | - helping to [collect citations for the sum of human knowledge](https://meta.wikimedia.org/wiki/WikiCite_2017)
29 | - contributing to [data science policy in the European Union](https://github.com/FAIR-EG/consultation)
30 | - helping to [organize events around modernizing scholarly communication](https://www.force11.org/group/force2017-organizing-committee/program-committee)
31 | - editing an open-science [journal](http://riojournal.com/browse_articles) that aims to make entire research processes visible, not just the results
32 | - running a [bot](https://commons.wikimedia.org/wiki/User:Open_Access_Media_Importer_Bot) that feeds openly licensed multimedia from PubMed Central into Wikimedia Commons for reuse on Wikipedia and elsewhere
33 | - editing the [Topic Pages](http://collections.plos.org/topic-pages) collection at PLOS Computational Biology
34 |
35 | ## How to discover research that is being *performed now* or *planned for the near future*?
36 |
37 | - **Actual need**
38 | - [Zika example](https://www.statnews.com/2016/02/16/zika-data-sharing/)
39 | - [further notes on emergency response](https://github.com/Daniel-Mietchen/datascience/blob/master/emergency-response.md)
40 | - **Some inspiration**
41 | - real-time [visualization](http://wikistream.wmflabs.org/#namespace=article&robot=true&user=true&wiki=all) and [sonification](http://listen.hatnote.com/#en,fa,ar,sa,es,de,ru,jp,zh,ko) of Wikimedia edits
42 | - What about [doing this for research](https://github.com/sparcopen/open-research-doathon/issues/34)?
43 | - As it happens (e.g. as per the video above)
44 | - [All along the research cycle](https://doi.org/10.3897/rio.1.e7547)?
45 | - with appropriate filtering, something of this kind could serve as the basis for researchers, funders, the public and others to engage with a given research topic
46 | - particularly relevant in the case of public health emergencies, which also provide a context where "open by default" is actually within reach
47 | - works best if data and metadata are [FAIR](https://doi.org/10.1038/sdata.2016.18) by default (see [open consultation](https://github.com/FAIR-Data-EG/consultation/issues))
48 | - publicly versioned [machine actionable data (or project) management plans](https://doi.org/10.3897/rio.3.e13086) as a way to connect research projects (past, ongoing and future) with relevant individuals, communities, institutions and their respective resources and workflows
49 | - **Queriability**: How can data from different parts of the research ecosystems best be integrated in a way that allows to address issues that cut across research fields?
50 | - Wikidata as a hub for structured open knowledge across domains, with biomedicine being one of the pilot areas
51 | - [sample queries](https://www.wikidata.org/wiki/User:ProteinBoxBot/SPARQL_Examples)
52 | - [map of topics co-occurring with "Zika virus" in the literature](https://query.wikidata.org/#%23defaultView%3AGraph%0A%23defaultView%3ATable%0Aselect%20distinct%20%3Ftopic1%20%3Ftopic1Label%20%3Ftopic2%20%3Ftopic2Label%20where%20{%0A%20%20{%20%3Fwork%20wdt%3AP921%2Fwdt%3AP31*%2Fwdt%3AP279*%20wd%3AQ202864%20.%20}%0A%20%20union%20{%20%3Fwork%20wdt%3AP921%2Fwdt%3AP361%2B%20wd%3AQ202864%20.%20}%0A%20%20union%20{%20%3Fwork%20wdt%3AP921%2Fwdt%3AP1269%2B%20wd%3AQ202864%20.%20}%0A%20%20%3Fwork%20wdt%3AP921%20%3Ftopic1%2C%20%3Ftopic2%20.%20%0A%20%20filter%20(wd%3AQ202864%20!%3D%20%3Ftopic1%20%26%26%20wd%3AQ202864%20!%3D%20%3Ftopic2%20%26%26%20%3Ftopic1%20!%3D%20%3Ftopic2)%0A%20%20SERVICE%20wikibase%3Alabel%20{%0A%20%20%20%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%2Cfr%2Cde%2Cru%2Ces%2Czh%2Cjp%22.%0A%20%20}%0A}%0A%0A)
53 | - [scholarly profile pages](https://tools.wmflabs.org/scholia/topic/Q202864)
54 | - **Reproducibility**
55 | - [Jupyter notebook from LIGO](https://twitter.com/KyleCranmer/status/698240530900193282)
56 | - [analysis of reproducibility of Jupyter notebooks](https://github.com/sparcopen/open-research-doathon/issues/25)
57 | - today's workshop [Fostering reproducible science – What data management tools can do and should do for you](http://fusion.cs.uni-jena.de/bexis2userdevconf2017/workshop/)
58 | - **Ethics**: making ethics data FAIR
59 | - [talk on the topic](https://github.com/Daniel-Mietchen/events/blob/master/PIDapalooza.md)
60 | - [further notes](https://github.com/Daniel-Mietchen/datascience/blob/master/ethics.md)
61 | - **Sustainability**: How to better align the priorities within the research ecosystems (open or not) with the needs of humanity as a whole?
62 | - e.g. the [UN's Sustainable Development Goals](https://sustainabledevelopment.un.org/sdgs)
63 | - [further notes](https://github.com/Daniel-Mietchen/datascience/blob/master/sustainability.md)
64 | - **Lean administration**: How can openness be used to reduce bureaucracy?
65 | - e.g. [self-organized fund allocation](https://doi.org/10.1007/s11192-016-2110-3)
66 | - **Effective policies**: How can different policies and infrastructures be made better aware of each other?
67 | - make policies machine readable?
68 | - start with machine readable licensing statements, e.g. [CC0 waiver](http://creativecommons.org/publicdomain/zero/1.0/deed.en)
69 | - [dedicated talk](https://github.com/Daniel-Mietchen/events/blob/master/5th-LEARN-workshop-2017.md)
70 |
71 | ## What does this mean for BEXIS?
72 |
73 | * Use persistent identifiers whenever possible
74 | - [botanical collections example](https://doi.org/10.1038/546033d)
75 | * Use open licenses and [avoid -NC restrictions](https://dx.doi.org/10.3897/zookeys.150.2189) to the extent possible, and CC0 for data
76 | - [WikiPathways example](http://wikipathways.org/index.php/WikiPathways:CC0_Announcement)
77 | * Share early and often
78 | - let others see more of what you are doing, closer to when you are doing it [upcoming iDiv symposium on data mobilization](https://github.com/Daniel-Mietchen/events/issues/44)
79 | * Share where others are looking to find things
80 | - [Ernst Abbe example](https://twitter.com/EvoMRI/status/741461595608522752)
81 | * Others includes people and machines
82 | * Your ideas
83 |
84 | # Dedication
85 |
86 | I dedicate this talk to the memory of my grandfather Werner Mietchen, whose funeral is [taking place the day after](https://github.com/Daniel-Mietchen/events/issues/138).
87 |
88 | # Contact
89 |
90 | - [@EvoMRI](https://twitter.com/EvoMRI)
91 | - email: daniel.mietchen[@](https://please-do-not-spam.me)virginia.edu
92 | - ORCID: [0000-0001-9488-1870](http://orcid.org/0000-0001-9488-1870)
93 |
94 | # About
95 |
96 | This page ( https://github.com/Daniel-Mietchen/events/blob/master/3rd-BEXIS-2-User-and-Developer-Conference.md ) hosts a presentation that was given on 15 June 2017 at 7am UTC. It is a contribution to the [3rd BEXIS 2 User and Developer Conference](http://fusion.cs.uni-jena.de/bexis2userdevconf2017/) taking place on 16 June 2017 in Jena, with an associated [reproducibility workshop](http://fusion.cs.uni-jena.de/bexis2userdevconf2017/workshop/) on June 15 in conjunction with [Data Science Day 2017](https://www.fmi.uni-jena.de/Fakult%C3%A4t/Aktivit%C3%A4ten+der+Fakult%C3%A4t/Veranstaltungen/Data+Science+Day+Jena/Data+Science+Day+2017.html). BEXIS (also BExIS) stands for "[Biodiversity Exploratories Information System](https://www.bexis.uni-jena.de/)" and is a research environment for managing the entire data life cycle for biodiversity data.
97 |
98 | Some impressions from the event are available [here](http://fusion.cs.uni-jena.de/bexis2userdevconf2017/impression/).
99 |
--------------------------------------------------------------------------------
/8th-Wikidata-birthday.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | As originally outliined [here](https://github.com/Daniel-Mietchen/ideas/issues/1371), I don't normally have bulk tickets for talks, but the week of [Wikidata's 8th birthday](https://www.wikidata.org/wiki/Wikidata:Eighth_Birthday) has them packed more than usual, so I need to keep things a bit more coordinated than simply on a per-talk basis. Thankfully, all of them revolve around WikiCite and Scholia, so I'll try to prepare them in a coordinated fashion as well. Since I first started that ticket, additional changes have accrued, so I am moving this to a dedicated file and including all events (currently six) that involve me speaking, including the Neuromatch conference and the Beilstein Open Science Symposium, both of which have no relationship to Wikidata birthday festivities other than their timing.
4 |
5 | - Monday, October 26, 2020
6 | - **10:00 UTC** [State of WikiCite](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference/The_State_of_WikiCite_in_2020) as a [dedicated session](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference#State_of_WikiCite) (45 min talk + 15 min Q&A) of the [2020 Virtual WikiCite conference](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference) in honour of [Wikidata's 8th birthday](https://www.wikidata.org/wiki/Wikidata:Eighth_Birthday)
7 | - Slides are up at [https://doi.org/10.5281/zenodo.4121846](https://doi.org/10.5281/zenodo.4121846).
8 | - Videos of the talk are available via [Wikimedia Commons](https://commons.wikimedia.org/wiki/File:WikiCite_2020_The_state_of_WikiCite.webm) and [YouTube](https://www.youtube.com/watch?v=TmGpJnukbYU) .
9 | - **19:00 UTC** - [Politicians and Politics in Scholia](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference/Citations_in_Swedish_Parliamentary_and_Judicial_documents_and_their_use#Workshop:_Politicians_and_Politics_in_Scholia) (60 min workshop, mostly brainstorming and Q&A) at the [Citations in Swedish Parliamentary documents](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference#Citations_in_Swedish_Parliamentary_documents) session of the [2020 Virtual WikiCite conference](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference) in honour of [Wikidata's 8th birthday](https://www.wikidata.org/wiki/Wikidata:Eighth_Birthday)
10 | - video recording available [via Wikimedia Commons](https://commons.wikimedia.org/wiki/File:WikiCite_2020_Citations_in_Swedish_Parliamentary_documents.webm#%7B%7Bint%3Afiledesc%7D%7D) (my part starts at ca. 2:00:30h in) as well as [on YouTube](https://www.youtube.com/watch?v=yMtP64yFKn0)
11 | - **22:00 UTC** [Collaborative curation via Wikidata: the case of citations and source metadata](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference/Collaborative_curation_via_Wikidata:_the_case_of_citations_and_source_metadata) (25 min talk + 5 min Q&A) as part of the [Research output items](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference#Research_output_items) session of the [2020 Virtual WikiCite conference](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference) in honour of [Wikidata's 8th birthday](https://www.wikidata.org/wiki/Wikidata:Eighth_Birthday)
12 | - video recording available [via Wikimedia Commons](https://commons.wikimedia.org/wiki/File:WikiCite_2020_Research_output_items.webm) (my part starts at about 1:10 min in) as well as [on YouTube](https://www.youtube.com/watch?v=us_yYR6tAUY) (at about 1:30 min)
13 |
14 | - Tuesday, October 27, 2020
15 | - **8:30 AM EST = 12:30 AM UTC** [Visualizing the research ecosystem of neuroscience research via Wikidata](https://github.com/Daniel-Mietchen/events/blob/master/neuromatch3.md) at [neuromatch](https://neuromatch.io/agenda) (10 min talk + 5 min Q&A)
16 | - slides and pre-recorded video up at [http://doi.org/10.5281/zenodo.4064274](http://doi.org/10.5281/zenodo.4064274)
17 | - the video is also available [on YouTube](https://www.youtube.com/watch?v=OPMoj7uMXRU)
18 | - actual recording is also up [on YouTube](https://www.youtube.com/watch?v=_bSZq22yiGU)
19 | - **ca. 16:15 CET = 15:15 UTC** - [Open Profiling of Chemical Knowledge](https://github.com/Daniel-Mietchen/events/blob/master/Beilstein-Open-Science-Symposium-2020.md) at [Beilstein Open Science Symposium 2020](http://web.archive.org/web/20201020231727/https://www.beilstein-institut.de/en/symposia/open-science/program/) (3 min lightning talk)
20 | - slides and pre-recorded video up at [http://doi.org/10.5281/zenodo.4095649](http://doi.org/10.5281/zenodo.4095649)
21 | - the video is also available [via YouTube](https://www.youtube.com/watch?v=aM2pUMvg81o)
22 | - **This is followed by a poster session from 4.45 pm until 5.15 pm CET, i.e. 15:45 UTC - 15:15 UTC — in other words, in parallel to my next session**
23 | - **15:45 UTC** [Présentation du projet WikiCite et démonstration de Scholia comme un outil ouvert d’analyse scientométrique](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference/Pr%C3%A9sentation_du_projet_WikiCite_et_d%C3%A9monstration_de_Scholia_comme_un_outil_ouvert_d%E2%80%99analyse_scientom%C3%A9trique) (45 min talk + 15 min Q&A) as part of the [WikiCite et scientométrie ouverte](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference#WikiCite_et_scientom%C3%A9trie_ouverte) session of the [2020 Virtual WikiCite conference](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference) in honour of [Wikidata's 8th birthday](https://www.wikidata.org/wiki/Wikidata:Eighth_Birthday)
24 | - pre-recorded video up at [http://doi.org/10.5281/zenodo.4139288](http://doi.org/10.5281/zenodo.4139288) and [on YouTube](https://www.youtube.com/watch?v=GtagO0XOR-A)
25 | - a video of the actual talk is also available [via Wikimedia Commons](https://commons.wikimedia.org/wiki/File:WikiCite_2020_Scientom%C3%A9trie_ouverte.webm) (my part starts at about 2h 21min) and [on YouTube](https://www.youtube.com/watch?v=PoY0cWhLOWQ#t=2h22m) (at ca. 2h 22 min)
26 |
27 | - Wednesday, October 28, 2020
28 | - **13:20 UTC** [Scholia and other Wikimedia resources/tools relevant to the Open Virus project](https://public.paws.wmcloud.org/12410844/OpenVirus/WikiCite-session-28-October-2020.ipynb) as part of the [Open Virus](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference#OpenVirus_and_Scholia_interfaces) session of the [2020 Virtual WikiCite conference](https://meta.wikimedia.org/wiki/WikiCite/2020_Virtual_conference) in honour of [Wikidata's 8th birthday](https://www.wikidata.org/wiki/Wikidata:Eighth_Birthday)
29 | - recording [on YouTube](https://www.youtube.com/watch?v=4kQnT5Yra1U#t=1h20m) (at about 1h:20min) and [on Wikimedia Commons](https://commons.wikimedia.org/w/index.php?title=File%3AWikiCite_2020_OpenVirus_and_Scholia_interfaces.webm) (at about 1h 13 min)
30 |
--------------------------------------------------------------------------------
/ASAPbio-Preprint-Curation-and-Review-Design-Sprint-2020.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts materials related to my participation in the ASAPbio Design Sprint [Encouraging Preprint Curation and Review](http://web.archive.org/web/20201023035646/https://asapbio.org/sprint) from 13 November till 3 December 2020. The accepted proposals are listed [here](https://asapbio.org/category/preprint-sprint-proposals), including [the one that was drafted here](https://asapbio.org/preprint-review-and-curation-by-content-type).
4 |
5 | # Project proposal
6 | *The structure of this section is based on the [ASAPbio Preprint Sprint Proposal Template](http://web.archive.org/web/20201020184303/https://docs.google.com/document/d/1JzMXnSk9W7W0k02MdTV2BqYhja1v6VVQ1kSk63hECpM/edit)*, which was to be submitted by 3 November 2020.
7 |
8 | ## Title
9 |
10 | Preprint review and curation by content type
11 |
12 | ## Organizer
13 |
14 | * Daniel Mietchen, School of Data Science, University of Virginia, [@EvoMRI](https://twitter.com/EvoMRI)
15 |
16 | ## Project status
17 |
18 | ongoing
19 |
20 | ## Project duration
21 |
22 | ongoing
23 |
24 | ## Project aims
25 | ### Background
26 |
27 | Peer review of preprints typically has two main components (a) general comments on parameters like the quality, scope, topicality or structure of the manuscript and (b) comments on details, e.g. inaccuracies, missing references, confusing plot parameters, unsubstantiated claims, typos. The general part is usually a synthesis that is best expressed in a new piece of text. Claims in this text are frequently substantiated with examples from the details part, though rarely in a click-through manner.
28 |
29 | Preprints may include - or be accompanied by - a variety of materials, possibly in various file formats and locations.
30 | Curation of preprints has to take into account the submitted files and any associated materials, as well as appropriate metadata.
31 |
32 | Feedback on preprints is more likely if (c) it is honoured in some way, (d) the preprint or its components appear in the workflows of potential reviewers, (e) it is clearer how to review certain kinds of materials, (f) tooling is available to support the review process, (g) a few other things. This proposal is mostly about e, partly about d and f, and it would perhaps add a nudge to c and g.
33 |
34 |
35 | ### Overview of the challenge to overcome
36 |
37 | Reviewing or curating the materials associated with preprints poses challenges that can and do vary as a function of parameters like their kind, format or location.
38 | For instance, if the preprint (i) is publicly available online in HTML format, (ii) is not versioned, (iii) does not contain non-textual elements like figures, tables, equations, code snippets or external identifiers and (iv) does not depend on things like software or data located elsewhere, then it can be reviewed by simply posting web annotations by means of a tool like Hypothesis ([example](https://via.hypothes.is/https://wellcomeopenresearch.org/articles/2-63/v1)). If any of these conditions are not met, then the review and/or curation workflows may require modification, particularly for the detailed comments. Some of these modifications can be simple (e.g. just mentioning the preprint's version ID in the review report can be enough to address the versioning problem), others may be more complex, e.g. reviewing software typically requires installing and running it, which may by complicated by dependencies or incompatibilities with respect to external software or data.
39 |
40 | ### The ideal outcome or output of the project
41 |
42 | Some best practice recommendations for preprint review and curation by content type, along with examples and validation tools that are contextualized from the perspective of these recommendations.
43 |
44 | ## Overview
45 | ### Description of the intervention
46 |
47 | Initially once: analysis of a random subset of preprints — ideally from a range of platforms — in terms of their non-textual components as well as the file formats and locations of associated materials.
48 | Ideally, such an analysis would be performed automatically on a daily basis thereafter, for all preprints meeting certain criteria.
49 |
50 | ### Plan for monitoring project outcome
51 |
52 | There are several milestones for the project to reach, in an iterative fashion
53 | - identification of the initial test corpus
54 | - identification of the initial set of criteria for analyzing the test corpus
55 | - identification of best practice examples (perhaps with further improvements) with respect to these criteria
56 | - distillation of the analysis into best practice recommendations
57 | - distillation of the recommendations into validation tools, badge system and dashboard
58 | - testing, documentation and training regarding the above
59 |
60 | ## What’s needed for success
61 | ### Additional technology development
62 |
63 | - Development of validation tools that can check — individually or in bulk — preprints or possibly also published articles for compliance with the recommendations.
64 | - Development of the technical components of a badge system that signals compliance with the recommendations at the level of individual preprints and perhaps platforms or other units of organization (e.g. journals).
65 | - Development of a dashboard to monitor adoption of the recommendations across the preprint landscape.
66 | - Tools assisting with the discovery, review and curation of specific content types.
67 |
68 | ### Feedback, beta testing, collaboration, endorsement
69 |
70 | - Collaborative development of the best practice recommendations and suitable examples.
71 | - Development and testing of the validation and badge systems.
72 | - Development and testing of mechanisms to discover, review and curate specific content types.
73 | - Documentation and training materials for authors and reviewers of preprints as well as operators of preprint platforms or other stakeholders.
74 |
75 | ### Funding
76 |
77 | - To move any of the above forward.
78 |
--------------------------------------------------------------------------------
/ArchivesSpace-Online-Forum-2019-emergencies.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a submission to the [ArchivesSpace Online Forum](https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/802127927/ArchivesSpace+Online+Forum+2019) taking place on 18 March 2019. It was submitted shortly before the deadline on February 18, 2019.
4 |
5 | # Title
6 |
7 | An archival perspective on public health emergencies
8 |
9 | # Abstract
10 |
11 | Public health emergencies require profound and swift action at scale with limited resources, often on the basis of incomplete information and frequently under rapidly evolving circumstances. While emergency-triggered sharing goes back millennia, the sharing of data and associated metadata is a relatively new flavour under this broader theme, but one that has been receiving steadily growing attention over the last few years, especially in the context of the Ebola or Zika outbreaks. By now, we have reached a point where data sharing must be considered a key component of addressing present, future and even past public health emergencies.
12 |
13 | In response, researchers, research institutions, journals, funders and others have taken steps towards increasing the sharing of data around ongoing public health emergencies and in preparation for future ones. These measures range from the adoption of open lab notebooks to modifications of policies and funding lines, and they include conversations around infrastructure and cultural change as well as around the provenance and persistence of emergency-related resources.
14 |
15 | This presentation will be given on the basis of https://github.com/Daniel-Mietchen/events/blob/master/ArchivesSpace-Online-Forum-2019-emergencies.md and provide an overview of different ways in which the sharing of data has played a role in public health emergencies, highlighting steps that have already been taken over the last decade as well as challenges still lying ahead and concluding with considerations around the potential impact of preserving and sharing data or associated metadata, or failing at that.
16 |
17 | # Notes
18 |
19 | *I will use this section to prepare the presentation.*
20 |
21 | * OECD report: [Assessing the Real Cost of Disasters](http://www.oecd.org/fr/publications/assessing-the-real-cost-of-disasters-9789264298798-en.htm)
22 | * Symposium [Leveraging and Integrating Data for Disasters](http://sites.nationalacademies.org/DBASSE/CNSTAT/DBASSE_189126)
23 | * [Disaster Risk Reduction Knowledge Service on Sustainable Development](https://www.scidatacon.org/IDW2018/sessions/164/paper/594/) ([background](https://github.com/Daniel-Mietchen/events/issues/211#issuecomment-436277039))
24 | * [#disasterdata](https://twitter.com/search?f=tweets&vertical=default&q=disasterdata)
25 |
--------------------------------------------------------------------------------
/ArchivesSpace-Online-Forum-2019-wikis.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a contribution to the [ArchivesSpace Online Forum](https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/802127927/ArchivesSpace+Online+Forum+2019) taking place on 18 March 2019. It was submitted shortly before the deadline on February 18, 2019.
4 |
5 | # Title
6 |
7 | Integrating archival workflows with Wikidata
8 |
9 | # Abstract
10 |
11 | Over the past several years, interest in leveraging [Wikidata](https://wikidata.org/) as an open knowledge base has been growing in areas ranging from cultural heritage institutions to research and technology organizations. With its inherent multilinguality, human-editable interface, community-driven approach to data modeling and curation, systemic connection to Wikipedia and sister projects and alignment with the FAIR Principles for sharing data, there is an emerging consensus that Wikidata represents a significant step for turning Linked Open Data into a practical and useful technology. It provides a bridge between the many siloed knowledge bases that have emerged since Tim Berners-Lee first proposed the notion of the semantic web. Despite this growing interest, there is still a fundamental lack of understanding of what Wikidata's strengths and weaknesses are, or those of Wikibase—the engine behind Wikidata. While experiments have been proliferating with the use of Wikibase, it is still very much an open question how to create a sustainable, federated ecosystem of knowledge bases to support open research, and what the social, technical, institutional barriers are towards this vision.
12 |
13 | This presentation will be given on the basis of https://github.com/Daniel-Mietchen/events/blob/master/ArchivesSpace-Online-Forum-2019-wikis.md and focus on how archival workflows can be integrated with Wikidata or Wikibase, particularly to foster broad accessibility to humans and machines, including for collaborative curation.
14 |
--------------------------------------------------------------------------------
/ArchivesSpace-Online-Forum-2019.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts two proposals submitted on 18 February 2019 to the [ArchivesSpace Online Forum](https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/802127927/ArchivesSpace+Online+Forum+2019) taking place on 18 March 2019.
4 |
5 | - [Integrating archival workflows with Wikidata](https://github.com/Daniel-Mietchen/events/blob/master/ArchivesSpace-Online-Forum-2019-wikis.md)
6 | - [An archival perspective on public health emergencies](https://github.com/Daniel-Mietchen/events/blob/master/ArchivesSpace-Online-Forum-2019-emergencies.md)
7 |
--------------------------------------------------------------------------------
/Beilstein-Open-Science-Symposium-2020.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a contribution to the [Beilstein Open Science Symposium 2020](https://web.archive.org/web/20201016172948/https://www.beilstein-institut.de/en/symposia/open-science/) taking place online on 27 & 28 October, 2020.
4 |
5 | Slots for talks had already been selected by the organizers, but they invited submissions for "poster demos", which is hence the intent here. My proposal was submitted on October 19, 2020, and approved the next day, for a 3-min lightning talk followed by the poster session, both on 27 October 2020.
6 |
7 | # Title
8 |
9 | Open profiling of chemical knowledge
10 |
11 | # Abstract
12 |
13 | Chemical research — like research in general — takes place in a sociotechnical ecosystem that connects researchers, institutions, funders, databases, locations, publications, methodologies and related concepts with the objects of study and the natural and cultural worlds around them.
14 |
15 | Mechanisms for describing concepts related to chemistry are growing in breadth and depth, number and popularity. In parallel, more and more chemistry-related data — and particularly metadata — are being made available under open licenses, which facilitates discoverability, reproducibility and reuse, as well as data integration.
16 |
17 | Wikidata is a community-curated open knowledge base in which concepts covered in any Wikipedia — and beyond — can be described in a structured and FAIR fashion that can be mapped to RDF and queried using SPARQL as well as various other means. Its community of over 20,000 monthly contributors oversees a corpus of currently over 90 million 'items’ for concepts that are linked amongst each other, to external databases or to specific values via over 7000 'properties'. Items and properties have persistent unique identifiers, to which labels, descriptions and dedicated lexemes and their forms and senses can be attached in over 300 natural languages.
18 |
19 | A range of open-source tools is available to interact with Wikidata — to enter information, curate and query it. In this presentation — which shall be available via https://doi.org/10.5281/zenodo.4095649 — we will outline a range of tools that allow to explore Wikidata content through frontends tailored to specific communities. Based on examples from chemistry, we will take a look at Scholia — available via https://scholia.toolforge.org/ — which allows to generate and explore Wikidata-based scholarly profiles of research topics, authors, institutions, funders and other parts of the research ecosystem, as well as of the world in which it is embedded.
20 |
21 |
22 | # See also
23 |
24 | * The [etherpad for the session](https://etherpad.wikimedia.org/p/zenodo.4095649)
25 | * Similar presentations:
26 | - [Visualizing the research ecosystem of neuroscience research via Wikidata](https://github.com/Daniel-Mietchen/events/blob/master/neuromatch3.md) on October 27, 2020
27 | - [Multilingual Structured Climate Research Data in Wikidata - The Data Perspective](data-science-in-climate-and-climate-impact-research.md) on 21 August 2020
28 | - [Visualizing the research ecosystem of ecosystem research via Wikidata](https://github.com/Daniel-Mietchen/events/blob/master/ICEI2018-research-ecosystem.md) on 27 September 2018
29 |
30 |
--------------------------------------------------------------------------------
/CCTB-2021-FAIR-Ethics.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file facilitates a talk given [online](https://uni-wuerzburg.zoom.us/j/97698479150?pwd=bzRuN0IrWCtsZTNtOFZ3WGovS0pXQT09) on 22 September 2021 at 11:00 CEST at the [Center for Computational and Theoretical Biology](https://www.biozentrum.uni-wuerzburg.de/cctb/cctb/) of the University of Würzburg on the topic "FAIR Ethics: Making Ethical Review Processes more Machine Actionable" as part of the [CCTB Seminar](https://hackmd.io/hFWFrZdbRb6VrdI0xQx_YQ?view) series.
4 |
5 | # Slides
6 |
7 | * [https://doi.org/10.5281/zenodo.5513579](https://doi.org/10.5281/zenodo.5513579)
8 |
9 | # See also
10 |
11 | * [FAIR Ethics: Making Ethical Review Processes more Machine Actionable](https://doi.org/10.5281/zenodo.2559998) — an earlier version of this talk (from 2018)
12 | * [Situating AI on the road from data sharing to societal impact](https://doi.org/10.5281/zenodo.3996019) — a 2020 talk with partial overlap
13 | * [Making ethics data FAIR](https://github.com/Daniel-Mietchen/events/blob/master/PIDapalooza-2016.md) (2016)
14 |
--------------------------------------------------------------------------------
/Creative-Commons-Summit-2015.md:
--------------------------------------------------------------------------------
1 | The [Creative Commons Global Summit 2015](https://summit.creativecommons.org/) has a [call for proposals](https://summit.creativecommons.org/cfp/) whose [submission form](https://donate.creativecommons.org/civicrm/event/register?reset=1&id=12) ([WebCite archive](http://www.webcitation.org/6a47O5pey)) asks for the following essential information as well as some metadata.
2 |
3 | # Session title
4 | Rethinking open research policies
5 |
6 | # Abstract
7 | Open access mandates and declarations, requirements for data management plans and related policy instruments have had considerable impact on the way research results are communicated between researchers, institutions and with the public. They have had much less of an effect on how research is being performed and how the research process is being shared. Based on an analysis of shortcomings in existing policies, I will outline some ways in which we could increase their individual and collective impact.
8 |
9 | # Detailed description
10 | Typical problems with existing policies include that they:
11 | 1. are hard to translate to or from concrete actions;
12 | 2. are not coupled with technical means facilitating their implementation;
13 | 3. contain stipulations that are based on assumptions rather than data;
14 | 4. focus on research results, often ignoring the process leading to them;
15 | 5. focus on regulating researchers, rather than empowering them;
16 | 6. neglect the importance of reuse rights;
17 | 7. are not openly licensed themselves.
18 |
19 | In this presentation, I will
20 | 1. explain why these problems are actually problems;
21 | 2. highlight policy examples that address them in a promising way;
22 | 3. outline how we could build on those examples to increase the individual and collective impact of open research policies.
23 |
24 | # License
25 | [CC0](http://creativecommons.org/publicdomain/zero/1.0/)
26 |
27 |
--------------------------------------------------------------------------------
/Creative-Commons-Summit-2020.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts information related to my planned participation in the [2020 Creative Commons Global Virtual Summit](https://summit.creativecommons.org/2020-call-for-proposals/).
4 |
5 | # Proposal
6 |
7 | I had considered submitting a proposal but did not get to it in time for the submission deadline on July 17, 2020.
8 |
9 |
--------------------------------------------------------------------------------
/DSI-Lunch-Learn-April-2019.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a contribution to the [Lunch & Learn series](https://datascience.virginia.edu/pages/research-lunch-and-learn-series) organized by the [Data Science Institute](https://datascience.virginia.edu/) at the University of Virginia. It is to be presented [on 19 April 2019](https://datascience.virginia.edu/pages/sharing-research-along-entire-research-cycle) from 11:30 a.m. to 1 p.m. EDT in room G006 of [Ruffner Hall](https://www.google.com/maps/place/Ruffner+Hall+(Curry+School+of+Education)/@38.0346734,-78.5116714,17z/data=!3m1!4b1!4m5!3m4!1s0x89b3865acb9c1fa7:0x96877eaa32f81e54!8m2!3d38.0346734!4d-78.5094827?shorturl=1).
4 |
5 | It is complemented by [this document](https://docs.google.com/document/d/17sEfoaK0cz45V1A58gMnwuSPqZoup7LuMn-wtkjxB2k/edit?usp=sharing) for collaborative note-taking.
6 |
7 | # Title
8 |
9 | Sharing research all along the research cycle
10 |
11 | # Abstract
12 |
13 | Human societies engage in research in order to advance their understanding and mastering of the world they live in. This involves sharing of various aspects of research. Starting from the research results and the underlying methodology, more and more aspects of research are now being shared, often with communities much broader than classical research teams.
14 |
15 | In this talk, we will zoom in on various individual steps of a number of research cycles and examine ways in which these steps have been or could have been shared, and what kinds of reuses are being enabled by such sharing. The examples will be drawn from various fields, e.g. public health emergencies, Babylonian archaeology or meteorology.
16 |
17 | # How do data science and open research go together?
18 |
19 | ## The research data life cycle
20 |
21 | - can be framed in [many ways](https://www.google.de/search?q=%22data+life+cycle%22)
22 | - ([UVA example](http://data.library.virginia.edu/data-management/lifecycle/))
23 | - key components: plan **・** get permissions **・** get funding **・** get infrastructure **・** collect metadata **・** collect data **・** process data **・** analyze data **・** *publish* **・** curate data **・** preserve data **・** reuse metadata **・** find data **・** access data **・** reuse data **・** reproduce data **・** delete data
24 | - exact arrangement can and does vary
25 | - frequent 'rinse and repeat'
26 |
27 | ## What does it mean to open it up?
28 |
29 | - no single *publishing* step within the cycle, since every intermediate step is an opportunity to share
30 | - [video](https://www.youtube.com/watch?v=LwW1-X3glak)
31 |
32 | ## Some of my activities in this space
33 |
34 | - helping to improve [data sharing in public health emergencies](http://www.who.int/bulletin/volumes/95/4/17-192096/en/)
35 | - working on [making data mangement plans machine actionable, versioned and public](https://doi.org/10.1371/journal.pcbi.1006750)
36 | - helped shape the [Open Science Prize](http://openscienceprize.org/)
37 | - helping to explore [technical aspects of preprint services in the life sciences](https://doi.org/10.3897/rio.3.e11825)
38 | - helping to [collect citations for the sum of human knowledge](https://meta.wikimedia.org/wiki/WikiCite_2018)
39 | - contributing to [data science policy in the European Union](https://doi.org/10.2777/1524)
40 | - helping to [organize events around modernizing scholarly communication](https://www.force11.org/group/force2017-organizing-committee/program-committee)
41 | - editing an open-science [journal](http://riojournal.com/browse_articles) that aims to make entire research processes visible, not just the results
42 | - building a [tool](https://tools.wmflabs.org/scholia/) for profiling research topics, organizations, awards, researchers and related concepts
43 | - running a [bot](https://commons.wikimedia.org/wiki/User:Open_Access_Media_Importer_Bot) that feeds openly licensed multimedia from PubMed Central into Wikimedia Commons for reuse on Wikipedia and elsewhere
44 | - editing the [Topic Pages](http://collections.plos.org/topic-pages) collection at PLOS Computational Biology
45 |
46 | ## Open data as a central element of an open research ecosystem
47 |
48 | [Listen to open data](http://listen.hatnote.com/#wikidata,fr,de,it,rm,en,ru,en,fa,ko,se,es,ca,pt)
49 |
50 | [](https://commons.wikimedia.org/wiki/File:Discovery_in_process.jpg)
51 |
52 | [](https://commons.wikimedia.org/wiki/File:Automated_weighbridge_for_Ad%C3%A9lie_penguins_-_journal.pone.0085291.g002.png)
53 |
54 |
55 | | [](https://commons.wikimedia.org/wiki/File:KsiegaSzkocka1.JPG) [](https://commons.wikimedia.org/wiki/File:Euromaidan_in_Kiev_2014_003.jpg) [](https://commons.wikimedia.org/wiki/File:00000003_F.jpg) [](https://en.wikipedia.org/wiki/File:IBM_Blue_Gene_P_supercomputer.jpg) [](https://commons.wikimedia.org/wiki/File:LIGO_measurement_of_gravitational_waves.svg) | [](https://commons.wikimedia.org/wiki/File:Ernst-Abbe-Denkmal_Jena_F%C3%BCrstengraben_-_20140802_125709.jpg) [](https://commons.wikimedia.org/wiki/File:Adaptive-Evolution-of-Eel-Fluorescent-Proteins-from-Fatty-Acid-Binding-Proteins-Produces-Bright-pone.0140972.g001.jpg) [](https://commons.wikimedia.org/wiki/File:Zika_EM_CDC_20541.png) [](https://commons.wikimedia.org/wiki/File:Carl_Spitzweg_021.jpg) [](https://commons.wikimedia.org/wiki/File:Road_Sign_SOLAR_ECLIPSE_TODAY_-_IMG_20170821_172443.jpg) [](https://commons.wikimedia.org/wiki/File:New_cuyama.jpg) | [](https://commons.wikimedia.org/wiki/File:Sudan_Envoy_-_Curious_Onlookers.jpg) [](https://commons.wikimedia.org/wiki/File:Everything_must_go.jpg) [](https://commons.wikimedia.org/wiki/File:In_Thought_..._(3020466221).jpg) [](https://commons.wikimedia.org/wiki/File:TGG_Icon_Color_18.png) [](https://commons.wikimedia.org/wiki/File:Wikidata_Map_July_2017_Normal.png) |
56 | |--------|--------|:---:|
57 | | [reproducibility](http://mybinder.org/repo/cranmer/ligo-binder) = f(data, metadata, code, …)| [reusability](http://tinyurl.com/ycpdwvmx) = g(data, metadata, code, …) | [open workflows are an invitation to collaborate, early and often](https://twitter.com/EvoMRI/status/928248498503417856)|
58 |
59 |
60 | # Beyond open data
61 |
62 | * FAIR: making research **F**indable, **A**ccessible, **I**nteroperable and **R**eusable for both humans and machines
63 | - *metadata* should be open by default
64 | - the corresponding *data* should be as closed as necessary
65 |
66 | # Zooming in
67 |
68 | ## How to discover research that is being *performed now* or *planned for the near future*?
69 |
70 | * [Demo of a real-time research dashboard](http://myresearch.institute/)
71 | * [data sharing in public health emergencies](https://github.com/Daniel-Mietchen/events/blob/master/Environmental-Health-Seminar-Env-H-580-on-2019-01-31.md)
72 | * [research published last week](https://github.com/Daniel-Mietchen/events/blob/master/FORCE-2018-research-published-last-week.md)
73 | * [data archaeology](https://github.com/Daniel-Mietchen/datascience/blob/master/data-archaeology.md)
74 | * [What would an efficient bus system look like for Charlottesville?](https://github.com/Daniel-Mietchen/ideas/issues/1153)
75 | * [Analyze all Jupyter notebooks mentioned in PubMed Central](https://github.com/Daniel-Mietchen/ideas/issues/2)
76 |
77 |
78 | # Image credits
79 |
80 | All images are linked to pages with metadata about them, including licensing information. The licensing is always compatible with the [CC BY-SA 4.0 license](https://creativecommons.org/licenses/by-sa/4.0/).
81 |
82 | # See also
83 |
84 | - [Open data: central element of an open research ecosystem](https://github.com/Daniel-Mietchen/events/blob/master/UVA-Datapalooza-2017.md)
85 | - [Opening up the research data life cycle](https://github.com/Daniel-Mietchen/events/blob/master/3rd-BEXIS-2-User-and-Developer-Conference.md)
86 | - [Open Science Q & A](https://openscience.ub.uni-bielefeld.de/)
87 | - I'm [@EvoMRI](https://twitter.com/EvoMRI)
88 |
89 |
--------------------------------------------------------------------------------
/DSI-Presidential-Fellows-Orientation-August-2019.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a contribution to the Orientation Day organized by the [Data Science Institute](https://datascience.virginia.edu/) at the University of Virginia for its [Presidential Fellows](https://datascience.virginia.edu/academics/presidential-fellows). It is to be presented on 23 August 2019 from about 2:30 p.m. to 3 p.m. EDT in the [Research Collaboration Corner](https://news.virginia.edu/content/new-corner-collaborative-space-boost-uva-research) (also know as the Corner Building; see [map](https://goo.gl/maps/npYxAok7SYZo3uuk9)).
4 |
5 | # Title
6 |
7 | Open & FAIR practices for sharing research all along the research cycle, both with humans and machines
8 |
9 | # Abstract
10 |
11 | Human societies engage in research in order to advance their understanding and mastering of the world they live in. This involves sharing of various aspects of research. Starting from the research results and the underlying methodology, more and more aspects of research are now being shared, often with communities much broader than classical research teams.
12 |
13 | In this talk, we will zoom in on various individual steps of a number of research cycles and examine ways in which these steps have been or could have been shared, and what kinds of reuses are being enabled by such sharing. The examples will be drawn from various fields, e.g. public health emergencies, Babylonian archaeology or meteorology.
14 |
15 | # How do data science and open research go together?
16 |
17 | ## The research data life cycle
18 |
19 | - can be framed in [many ways](https://www.google.de/search?q=%22data+life+cycle%22)
20 | - ([UVA example](http://data.library.virginia.edu/data-management/lifecycle/))
21 | - key components: plan **・** get permissions **・** get funding **・** get infrastructure **・** collect metadata **・** collect data **・** process data **・** analyze data **・** *publish* **・** curate data **・** preserve data **・** reuse metadata **・** find data **・** access data **・** reuse data **・** reproduce data **・** delete data
22 | - exact arrangement can and does vary
23 | - frequent 'rinse and repeat'
24 |
25 | ## What does it mean to open it up?
26 |
27 | - no single *publishing* step within the cycle, since every intermediate step is an opportunity to share
28 | - [video](https://www.youtube.com/watch?v=LwW1-X3glak)
29 |
30 | ## Some of my activities in this space
31 |
32 | - helping to improve [data sharing in public health emergencies](http://www.who.int/bulletin/volumes/95/4/17-192096/en/)
33 | - working on [making data mangement plans machine actionable, versioned and public](https://doi.org/10.1371/journal.pcbi.1006750)
34 | - helped shape the [Open Science Prize](http://openscienceprize.org/)
35 | - helping to explore [technical aspects of preprint services in the life sciences](https://doi.org/10.3897/rio.3.e11825)
36 | - helping to [collect citations for the sum of human knowledge](https://meta.wikimedia.org/wiki/WikiCite_2018)
37 | - contributing to [data science policy in the European Union](https://doi.org/10.2777/1524)
38 | - helping to [organize events around modernizing scholarly communication](https://www.force11.org/group/force2017-organizing-committee/program-committee)
39 | - editing an open-science [journal](http://riojournal.com/browse_articles) that aims to make entire research processes visible, not just the results
40 | - building a [tool](https://tools.wmflabs.org/scholia/) for profiling research topics, organizations, awards, researchers and related concepts
41 | - running a [bot](https://commons.wikimedia.org/wiki/User:Open_Access_Media_Importer_Bot) that feeds openly licensed multimedia from PubMed Central into Wikimedia Commons for reuse on Wikipedia and elsewhere
42 | - editing the [Topic Pages](http://collections.plos.org/topic-pages) collection at PLOS Computational Biology
43 |
44 | ## Open data as a central element of an open research ecosystem
45 |
46 | [Listen to open data](http://listen.hatnote.com/#wikidata,fr,de,it,rm,en,ru,en,fa,ko,se,es,ca,pt)
47 |
48 | [](https://commons.wikimedia.org/wiki/File:Discovery_in_process.jpg)
49 |
50 | [](https://commons.wikimedia.org/wiki/File:Automated_weighbridge_for_Ad%C3%A9lie_penguins_-_journal.pone.0085291.g002.png)
51 |
52 |
53 | | [](https://commons.wikimedia.org/wiki/File:KsiegaSzkocka1.JPG) [](https://commons.wikimedia.org/wiki/File:Euromaidan_in_Kiev_2014_003.jpg) [](https://commons.wikimedia.org/wiki/File:00000003_F.jpg) [](https://en.wikipedia.org/wiki/File:IBM_Blue_Gene_P_supercomputer.jpg) [](https://commons.wikimedia.org/wiki/File:LIGO_measurement_of_gravitational_waves.svg) | [](https://commons.wikimedia.org/wiki/File:Ernst-Abbe-Denkmal_Jena_F%C3%BCrstengraben_-_20140802_125709.jpg) [](https://commons.wikimedia.org/wiki/File:Adaptive-Evolution-of-Eel-Fluorescent-Proteins-from-Fatty-Acid-Binding-Proteins-Produces-Bright-pone.0140972.g001.jpg) [](https://commons.wikimedia.org/wiki/File:Zika_EM_CDC_20541.png) [](https://commons.wikimedia.org/wiki/File:Carl_Spitzweg_021.jpg) [](https://commons.wikimedia.org/wiki/File:Road_Sign_SOLAR_ECLIPSE_TODAY_-_IMG_20170821_172443.jpg) [](https://commons.wikimedia.org/wiki/File:New_cuyama.jpg) | [](https://commons.wikimedia.org/wiki/File:Sudan_Envoy_-_Curious_Onlookers.jpg) [](https://commons.wikimedia.org/wiki/File:Everything_must_go.jpg) [](https://commons.wikimedia.org/wiki/File:In_Thought_..._(3020466221).jpg) [](https://commons.wikimedia.org/wiki/File:TGG_Icon_Color_18.png) [](https://commons.wikimedia.org/wiki/File:Wikidata_Map_July_2017_Normal.png) |
54 | |--------|--------|:---:|
55 | | [reproducibility](http://mybinder.org/repo/cranmer/ligo-binder) = f(data, metadata, code, …)| [reusability](http://tinyurl.com/ycpdwvmx) = g(data, metadata, code, …) | [open workflows are an invitation to collaborate, early and often](https://twitter.com/EvoMRI/status/928248498503417856)|
56 |
57 |
58 | # Beyond open data
59 |
60 | * FAIR: making research **F**indable, **A**ccessible, **I**nteroperable and **R**eusable for both humans and machines
61 | - *metadata* should be open by default
62 | - the corresponding *data* should be as closed as necessary
63 |
64 | # Zooming in
65 |
66 | ## How to discover research that is being *performed now* or *planned for the near future*?
67 |
68 | * [Demo of a real-time research dashboard](http://myresearch.institute/)
69 | * [data sharing in public health emergencies](https://github.com/Daniel-Mietchen/events/blob/master/Environmental-Health-Seminar-Env-H-580-on-2019-01-31.md)
70 | * [research published last week](https://github.com/Daniel-Mietchen/events/blob/master/FORCE-2018-research-published-last-week.md)
71 | * [data archaeology](https://github.com/Daniel-Mietchen/datascience/blob/master/data-archaeology.md)
72 | * [What would an efficient bus system look like for Charlottesville?](https://github.com/Daniel-Mietchen/ideas/issues/1153)
73 | * [Analyze all Jupyter notebooks mentioned in PubMed Central](https://github.com/Daniel-Mietchen/ideas/issues/2)
74 |
75 |
76 | # Image credits
77 |
78 | All images are linked to pages with metadata about them, including licensing information. The licensing is always compatible with the [CC BY-SA 4.0 license](https://creativecommons.org/licenses/by-sa/4.0/).
79 |
80 | # See also
81 |
82 | - [Sharing research all along the research cycle](DSI-Lunch-Learn-April-2019.md) — a contribution to DSI's Lunch & Learn series
83 | - [Open data: central element of an open research ecosystem](https://github.com/Daniel-Mietchen/events/blob/master/UVA-Datapalooza-2017.md)
84 | - [Opening up the research data life cycle](https://github.com/Daniel-Mietchen/events/blob/master/3rd-BEXIS-2-User-and-Developer-Conference.md)
85 | - [Open Science Q & A](https://openscience.ub.uni-bielefeld.de/)
86 | - I'm [@EvoMRI](https://twitter.com/EvoMRI)
87 |
88 |
--------------------------------------------------------------------------------
/ECSA-2018-Citizen-science-and-Open-science.md:
--------------------------------------------------------------------------------
1 |
2 | # Title
3 |
4 | Citizen science and open science would benefit from closer interaction
5 |
6 | # Final version
7 |
8 | [](https://commons.wikimedia.org/wiki/File:Citizen_Science_and_Open_Science_would_benefit_from_closer_interaction_-_20180604_100410.jpg)
9 | A photograph of the poster. On the top right is the [Policy brief on Citizen science & Open science](https://ecsa.citizen-science.net/blog/citizen-science-open-science-policy-brief-out) ([CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)).
10 |
11 | # Abstract
12 |
13 | Even though their primary goals and motivations differ, both citizen science and open science have the potential to challenge and change the predominant ways in which research is done today. That potential is considerably enhanced when the two come together.
14 |
15 | While citizen science is focused on opening up some aspects of specific research projects and on engaging the public to contribute, open science is focused on opening up research as it proceeds through the entire research cycle, and the possibility to engage with the public is a usually welcome but rarely central aspect.
16 |
17 | Now imagine research being done in a way that allows anyone — expert or amateur — to contribute to, learn from or otherwise engage with it at any stage.
18 |
19 | In this contribution - which is to be given from https://github.com/Daniel-Mietchen/events/blob/master/ECSA-2018-Citizen-science-and-Open-science.md - I would like to outline some ways in which citizen science would benefit from wider adoption of open science practices, and vice versa, drawing on examples from multiple fields of inquiry.
20 |
21 | # About
22 |
23 | This file hosts a submission to the European Citizen Science Association (ECSA) [conference](https://www.ecsa-conference.eu/) on 3-5 June 2018 in Geneva. It was submitted by the 21 January 2018 deadline under the "Does citizen science change science?" theme
24 | and the sub-theme "Is Citizen Science just science by other means, or can it transform what counts as evidence?"
25 |
26 | On March 28, I was notified that this session had been accepted, albeit in a format (as a poster) that differed from what I had proposed (a talk). I had until April 4 to confirm, which I did. I also enquired about how to join the "digital poster session" and was told that there were no slots left.
27 |
28 | All posters have been scheduled to be on display from 8:30 until 14:00 on Monday June 4, with the poster session from 13:00-14:00 to discuss with the poster authors.
29 |
30 | # See also
31 |
32 | * [ECSA2018.md](ECSA2018.md)
33 |
--------------------------------------------------------------------------------
/ECSA-2018-IAS.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a submission to the European Citizen Science Association (ECSA) [conference](https://www.ecsa-conference.eu/) on 3-5 June 2018 in Geneva. It was submitted by the 21 January 2018 deadline under the "Scientific literacy" theme. On March 27, I was notified by the organizers that the session had been put on a waitlist:
4 | > For now, we cannot include your contribution with the Title “A framework for co-creating citizen science projects with school students” (ID285) in our programme. However, if any of the slots should become available within the next few weeks we would be happy to contact you again.
5 |
6 | # Title
7 |
8 | A framework for co-creating citizen science projects with school students
9 |
10 | # Abstract
11 |
12 | "I'm a Scientist - get me out of here" is a science engagement platform that brings together school students in the UK with researchers from various disciplines in highly interactive online contexts. Inspired in style by some popular media formats, it is thematically centred around scientific literacy, the fascination of research, and the human aspects of being (or possibly becoming) a researcher.
13 |
14 | After running for several years with a range of schools, classes and researchers in "zones" focused on general science or specific subfields, a new variation was introduced in 2017: baptized the "Enquiry Zone", the idea here is to have students co-create citizen science projects in the subject domains of the zone's researchers, to vote on which of these potential projects they would like to realize, and to do so with guidance from the corresponding researcher.
15 |
16 | Building on the experiences from 2017, another issue of the event will be run in March 2018, again with an "Enquiry Zone" focused on citizen science. In this presentation - which is to be given on the basis of https://github.com/Daniel-Mietchen/events/blob/master/ECSA-2018-IAS.md - I plan to summarize the outcomes.
17 |
18 | # See also
19 |
20 | * [ECSA2018.md](ECSA2018.md)
21 |
22 |
--------------------------------------------------------------------------------
/ECSA-2018-Usability.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a submission to the European Citizen Science Association (ECSA) [conference](https://www.ecsa-conference.eu/) on 3-5 June 2018 in Geneva. It was submitted by the 21 January 2018 deadline under the "Empowering (individual) citizens" theme and the subtheme "Contributory, collaborative, co-created and collegiate – How to understand and conceptualize the role of participants in the spectrum of Citizen Science – from bottom-up to top-down? What are the specific challenges for citizens?"
4 |
5 | On March 27, I was notified that this session was not to be included in the final program.
6 |
7 | # Title
8 |
9 | Usability of citizen science projects
10 |
11 | # Abstract
12 |
13 | This session aims to encourage its participants to try out citizen science projects of their choice, on their own laptops or other mobile devices. They will be prompted to assess the usability of the tested projects via a lightweight survey, and for a small number of specific projects (to be selected on the basis of the other sessions that make it into the program), representatives will be there to help deepen the interaction between the projects and these new test users.
14 |
15 | The main goals of the session - which is to be given on the basis of https://github.com/Daniel-Mietchen/events/blob/master/ECSA-2018-Usability.md - are to provide conference participants with a hands-on experience of citizen science projects new to them, and to provide organizers of citizen science projects with feedback on usability. An intended side effect of the preparation of the session is the creation of a simplified way to assess citizen science projects in terms of their usability by new users.
16 |
17 | # See also
18 |
19 | * [ECSA2018.md](ECSA2018.md)
20 | * [ECSA2016.md](ECSA2016.md) (a similar submission that was not accepted at the time)
21 |
--------------------------------------------------------------------------------
/ECSA2016.md:
--------------------------------------------------------------------------------
1 | # About
2 | This file hosts a session proposal for the [First International ECSA Conference 2016](http://www.ecsa2016.eu/) "Citizen Science – Innovation in Open Science, Society and Policy" that was held in Berlin on 19–21 May, 2016. The session proposal was submitted on December 14 and rejected on December 19, 2015.
3 |
4 | At the conference itself, there was an unconference session (called ThinkCamp — see [program](http://www.ecsa2016.eu/assets/ecsa2016_confguide_15052016.pdf)) on the third day. While a number of projects had been proposed for this session beforehand, it was possible to suggest additional ones on the spot. I took that opportunity and brought up the topic of usability and interoperability of citizen science projects and platforms, which then led to an interesting discussion. The group was too small to take notes and discuss at the same time, but I am confident that the topic will surface again, and looking forward to engage with whoever shares that interest.
5 |
6 | # Title
7 | Hands-on usability
8 |
9 | # Abstract
10 | This session aims to encourage its participants to try out citizen science projects of their choice, on their own laptops or other mobile devices. They will be prompted to assess the usability of the tested projects via a lightweight survey, and for a small number of specific projects (to be selected via the upcoming call for abstracts), representatives will be there to help deepen the interaction between the projects and these new test users.
11 |
12 | The main goals of the session are to provide conference participants with a hands-on experience of citizen science projects new to them, and to provide organizers of citizen science projects with feedback on usability. An intended side effect of the preparation of the session is the creation of a simplified way to assess citizen science projects in terms of their usability by new users.
13 |
14 | # Keywords
15 |
16 | - demos, usability, assessment
17 |
--------------------------------------------------------------------------------
/ECSA2018.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | The European Citizen Science Association (ECSA) are holding their next [conference](https://www.ecsa-conference.eu/) on 3-5 June 2018 in Geneva.
4 |
5 | The call for proposals had a [January 21 deadline](https://www.ecsa-conference.eu/component/k2/item/15-the-call-is-extended), by which I submitted four abstracts, three of which have a dedicated entry in this repo:
6 | * [Citizen science and open science would benefit from closer interaction](ECSA-2018-Citizen-science-and-Open-science.md) (on March 28, I was notified that this session had been accepted, albeit in a format that differed from what I had proposed. I confirmed by the April 4 deadline)
7 | * [Wikimedia projects and citizen science](https://www.wikidata.org/wiki/User:Daniel_Mietchen/ECSA_2018) (on March 28, I was notified that this session had been accepted, albeit in a format that differed from what I had proposed. I confirmed by the April 4 deadline)
8 | * [A framework for co-creating citizen science projects with school students](ECSA-2018-IAS.md) (waitlisted as of March 27)
9 | * [Usability of citizen science projects](ECSA-2018-Usability.md) (on March 27, I was notified that this session was not to be included in the final program)
10 |
11 | # See also
12 |
13 | * [ECSA2016.md](ECSA2016.md)
14 |
--------------------------------------------------------------------------------
/EGI-Community-Forum-2015.md:
--------------------------------------------------------------------------------
1 | # About
2 | This file hosts an abstract for the [EGI Community Forum 2015](https://indico.egi.eu/indico/conferenceDisplay.py?confId=2544) (to take place on 10-13 November, 2015, in Bari, Italy), which was submitted on July 12.
3 |
4 | # Title
5 | Wikidata - structured information for Wikipedia and what this means for research workflows
6 |
7 | # Abstract
8 | There have been several attempts at bringing structured information together with Wikipedia. The most recent one is Wikidata, a MediaWiki-based collaborative platform that uses dedicated MediaWiki extensions (Wikibase Repository and Wikibase Client) to handle semantic information. It started out in late 2012 as a centralized way to curate the information as to which Wikipedia languages have articles about which semantic concepts.
9 |
10 | Since then, it has been continuously expanding in scope, and it now has structured information about 14 million, including about some that do not have articles in any Wikipedia. It is not only the content that is growing in extent and usefulness, but the contributor community is expanding too, making Wikidata one of the most active Wikimedia projects.
11 |
12 | The use of Wikidata in research contexts has only begun to be explored. For instance, there are Wikidata items about all human genes, and they have been annotated with information about their interaction with other genes, with drugs and diseases, as well as with references to pertinent databases or the relevant literature. Another example is the epigraphy community, which uses Wikibase to collect information about stone inscriptions and papyruses.
13 |
14 | In this talk, I will outline different ways in which Wikidata and/ or Wikibase can and do interact with research workflows, as well as opportunities to expand these interactions in the future, especially in the context of open science and citizen science projects.
15 |
16 | # Links, references, publications, etc.
17 | * The Wikidata website is available at https://wikidata.org/ , and information about the Wikibase extensions via http://wikiba.se/ .
18 | * http://korrekt.org/page/Wikidata:_A_Free_Collaborative_Knowledgebase provides an overview of Wikidata, including its data model and general design.
19 | * A grant proposal on adapting Wikidata such that it can serve as a Virtual Research Environment is available via http://dx.doi.org/10.5281/zenodo.13906 .
20 |
21 | # Presentation type
22 | Presentation
23 |
24 | # Primary Authors
25 | Daniel Mietchen
26 |
27 | # Co-Authors
28 | None
29 |
30 | # Track classification
31 |
32 | * Community Engagement and Innovation
33 | * Open Science Commons
34 |
35 |
--------------------------------------------------------------------------------
/FORCE-2018-1-minute-madness-remote.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This is a submission to the [Force 2018 Conference](https://www.force11.org/meetings/force2018) taking place on 11-12 October 2018 in Montreal. It was submitted shortly prior to the submission deadline on May 1, 2018.
4 |
5 | # What areas does your talk cover?
6 |
7 | - [X] Research Techniques
8 | - [X] Publishing
9 | - [X] Data Publishing
10 | - [X] Global Perspectives
11 | - [X] Research and Schol Comms Policy
12 | - [X] General - Scholarly Communication
13 | - [X] Other: any other aspect of scholarly communication that submitters bring up
14 |
15 | # What is the title of your talk?
16 |
17 | 1-Minute madness (remote)
18 |
19 | # What is your talk about? (1 paragraph)
20 |
21 | *Please supply one paragraph describing your talk and how it relates to the theme of Engagement. (Please also declare any conflicts of interest. )*
22 |
23 | Many who might have something valuable to contribute to the conference will not be able to make it in person. For this session, they will be invited to submit a 1-minute video or audio file that will be presented on site along with up to 24 others in a video medley linked from https://github.com/Daniel-Mietchen/events/blob/master/FORCE-2018-1-minute-madness-remote.md .
24 |
25 | # Anything else we should know?
26 |
27 | This should be coordinated with the in-person version of this session, as per https://github.com/Daniel-Mietchen/events/blob/master/FORCE-2018-1-minute-madness.md . Ideally, the remote session would come first, and there would be a larger break after the in-person session.
28 |
29 | # See also
30 |
31 | * [FORCE-2018.md](FORCE-2018.md)
32 |
--------------------------------------------------------------------------------
/FORCE-2018-1-minute-madness.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This is a submission to the [Force 2018 Conference](https://www.force11.org/meetings/force2018) taking place on 11-12 October 2018 in Montreal. It was submitted shortly prior to the submission deadline on May 1, 2018.
4 |
5 | # What areas does your talk cover?
6 |
7 | - [X] Research Techniques
8 | - [X] Publishing
9 | - [X] Data Publishing
10 | - [X] Global Perspectives
11 | - [X] Research and Schol Comms Policy
12 | - [X] General - Scholarly Communication
13 | - [X] Other: any other aspect of scholarly communication that submitters bring up
14 |
15 | # What is the title of your talk?
16 |
17 | 1-Minute madness
18 |
19 | # What is your talk about? (1 paragraph)
20 |
21 | *Please supply one paragraph describing your talk and how it relates to the theme of Engagement. (Please also declare any conflicts of interest. )*
22 |
23 | This session will consist of up to 25 lightning talks in which presenters can bring up any topic relevant to scholarly communication in just 1 min, with the discussion taking place in an accompanying etherpad linked from https://github.com/Daniel-Mietchen/events/blob/master/FORCE-2018-1-minute-madness.md .
24 |
25 | # Anything else we should know?
26 |
27 | This should be coordinated with the remote version of this session, as per https://github.com/Daniel-Mietchen/events/blob/master/FORCE-2018-1-minute-madness-remote.md . Ideally, the remote session would come first, and there would be a larger break after the in-person session.
28 |
29 | # See also
30 |
31 | * [FORCE-2018.md](FORCE-2018.md)
32 |
--------------------------------------------------------------------------------
/FORCE-2018-jrost.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This is a submission to the [Force 2018 Conference](https://www.force11.org/meetings/force2018) taking place on 11-12 October 2018 in Montreal. It was submitted shortly prior to the submission deadline on May 1, 2018.
4 |
5 | # What areas does your talk cover?
6 |
7 | - [ ] Research Techniques
8 | - [ ] Publishing
9 | - [ ] Data Publishing
10 | - [X] Global Perspectives
11 | - [ ] Research and Schol Comms Policy
12 | - [X] General - Scholarly Communication
13 | - [X] Other: tools and infrastructure
14 |
15 | # What is the title of your talk?
16 |
17 | Integrating the ecosystem of open science tools and infrastructure
18 |
19 | # What is your talk about? (1 paragraph)
20 |
21 | *Please supply one paragraph describing your talk and how it relates to the theme of Engagement. (Please also declare any conflicts of interest. )*
22 |
23 | Just like the open science ecosystem itself, the underlying infrastructure is experiencing a period of rapid development and diversification. This creates challenges for anyone intending to use or build on such infrastructure and triggers the need for coordination. This session will outline how the Joint Roadmap for Open Science Tools is bringing together key technology organizations and researchers who are actively involved in the design and production of open scholarly infrastructure to explore shared goals and outcomes, develop cross-platform user stories, and identify areas of mutual collaboration. The talk will be given on the basis of https://github.com/Daniel-Mietchen/events/blob/master/FORCE-2018-jrost.md .
24 |
25 | # Anything else we should know?
26 |
27 | The initiative is rather fresh, as can be gleaned from the timeline at http://jrost.org/meetings . We are expecting significant momentum to develop until October, though, starting with our MozSprint project at https://github.com/OpenScienceRoadmap/mozilla-sprint-2018 .
28 |
29 | # See also
30 |
31 | * [FORCE-2018.md](FORCE-2018.md)
32 |
--------------------------------------------------------------------------------
/FORCE-2018-research-performed-last-week.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This is a submission to the [Force 2018 Conference](https://www.force11.org/meetings/force2018) taking place on 11-12 October 2018 in Montreal. It was submitted shortly prior to the submission deadline on May 1, 2018.
4 |
5 | # What areas does your talk cover?
6 |
7 | - [X] Research Techniques
8 | - [X] Publishing
9 | - [X] Data Publishing
10 | - [X] Global Perspectives
11 | - [X] Research and Schol Comms Policy
12 | - [X] General - Scholarly Communication
13 | - [X] Other: Open notebook science, open education, annotation, research funding, social media
14 |
15 | # What is the title of your talk?
16 |
17 | Research performed over the last week
18 |
19 | # What is your talk about? (1 paragraph)
20 |
21 | *Please supply one paragraph describing your talk and how it relates to the theme of Engagement. (Please also declare any conflicts of interest. )*
22 |
23 | Research is performed every day, but much of it is hidden from public view. I will provide a guided tour around public aspects of research from various fields that was performed over the week prior to the session, highlighting (i) how to find such research, (ii) what can be learned from it, (iii) how to engage with it and (iv) lessons that can be drawn from the experience. The talk will be given on the basis of https://github.com/Daniel-Mietchen/events/blob/master/FORCE-2018-research-performed-last-week.md .
24 |
25 | # Anything else we should know?
26 |
27 | This talk is closely related to the one at https://github.com/Daniel-Mietchen/events/blob/master/FORCE-2018-research-published-last-week.md , and I would strongly prefer the two to be scheduled back to back in the same room, either before a session covering scholarly communication more broadly, or before a break.
28 |
29 | # See also
30 |
31 | * [FORCE-2018.md](FORCE-2018.md)
32 | * ["If you got something good going, don't tell anybody"](https://twitter.com/NastyCSA_/status/991046895018668039)
33 |
--------------------------------------------------------------------------------
/FORCE-2018-wikidata-wikibase.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This is a submission — co-authored with Dario Taraborelli — to the [Force 2018 Conference](https://www.force11.org/meetings/force2018) taking place on 11-12 October 2018 in Montreal. It was submitted shortly prior to the extended submission deadline on May 4, 2018.
4 |
5 | # What areas does your talk cover?
6 |
7 | - [ ] Research Techniques
8 | - [ ] Publishing
9 | - [ ] Data Publishing
10 | - [X] Global Perspectives
11 | - [ ] Research and Schol Comms Policy
12 | - [X] General - Scholarly Communication
13 | - [X] Other: tools and infrastructure
14 |
15 | # What is the title of your talk?
16 |
17 | Wikidata, Wikibase, and a federated ecosystem of structured knowledge for open science
18 |
19 | # What is your talk about? (1 paragraph)
20 |
21 | *Please supply one paragraph describing your talk and how it relates to the theme of Engagement. (Please also declare any conflicts of interest. )*
22 |
23 | Over the past several years, interest in leveraging Wikidata as an open knowledge base has been growing in areas ranging from cultural heritage institutions and libraries to research and technology organizations. With its inherent multilinguality, human-editable interface, community-driven approach to data modeling and curation, systemic connection to Wikipedia and sister projects and alignment with the FAIR Principles for sharing data, there is an emerging consensus that Wikidata represents a significant step for turning Linked Open Data into a practical and useful technology. It provides a bridge between the many siloed knowledge bases that have emerged in the more than two decades since Tim Berners-Lee first proposed the notion of the semantic web. Despite this growing interest, there is still a fundamental lack of understanding of what Wikidata's strengths and weaknesses are, or those of Wikibase —the engine behind Wikidata. While experiments have been proliferating with the use of Wikibase, it is still very much an open question how to create a sustainable, federated ecosystem of knowledge bases to support open research, and what the social, technical, institutional barriers are towards this vision . We would like to use this session as an opportunity to identify and discuss user stories from researchers and practitioners working on open research infrastructure and understand what a model could be to get more groups onboard to design a possible path towards this vision. The presentation will be given on the basis of https://github.com/Daniel-Mietchen/events/blob/master/FORCE-2018-wikidata-wikibase.md .
24 |
25 | # Anything else we should know?
26 |
27 | The submission was filed by Dario.
28 |
29 | # The actual talk
30 |
31 | - [session description](https://force2018.sched.com/event/F7u7/wikidata-wikibase-and-a-federated-ecosystem-of-structured-knowledge-for-open-science)
32 | - [Slides](https://docs.google.com/presentation/d/1PtsEFgK0IuZbYn5o57mfDRaiHjluRJ4OhYgRMxdXv30/edit)
33 | - [Video recording](https://www.youtube.com/watch?v=Bdwg168elaE)
34 |
35 | # See also
36 |
37 | * [FORCE-2018.md](FORCE-2018.md)
38 |
--------------------------------------------------------------------------------
/FORCE-2018.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file is auxiliary to my submissions to the [Force 2018 Conference](https://www.force11.org/meetings/force2018) taking place on 11-12 October 2018 in Montreal, with workshops on the 10th. After the soft deadline of May 1 having passed, there was a hard one on May 4.
4 |
5 | # Submitted
6 |
7 | * [FORCE-2018-research-published-last-week.md](FORCE-2018-research-published-last-week.md) (accepted as a workshop)
8 | * [FORCE-2018-research-performed-last-week.md](FORCE-2018-research-performed-last-week.md) (accepted as a poster)
9 | * [FORCE-2018-jrost.md](FORCE-2018-jrost.md) (accepted as a poster)
10 | * [FORCE-2018-1-minute-madness.md](FORCE-2018-1-minute-madness.md) (accepted as a poster)
11 | * [FORCE-2018-1-minute-madness-remote.md](FORCE-2018-1-minute-madness-remote.md) (accepted as a poster)
12 | * [FORCE-2018-wikidata-wikibase.md](FORCE-2018-wikidata-wikibase.md) (accepted as a talk)
13 | * [How Europe can make FAIR data a reality: An Action Plan](https://force2018.sched.com/event/F7uD) (accepted as a talk)
14 |
15 | # Other potential ideas
16 |
17 | * [Open Questions](https://ask-open-science.org/1113/which-research-fields-keep-public-lists-of-open-questions)
18 | * [Collaborative FAQ](https://ask-open-science.org/)
19 | * [Author disambiguation: a collaborative approach](https://tools.wmflabs.org/sourcemd/new_resolve_authors.php?name=Jane+Smith&doit=Look+for+author)
20 | * [Scholia](https://tools.wmflabs.org/scholia/)
21 | * [DoesItFart? A case study in communicating research](https://github.com/Daniel-Mietchen/ideas/issues/199)
22 |
23 | # See also
24 |
25 | * [notes on the event](https://github.com/Daniel-Mietchen/events/issues/325)
26 |
--------------------------------------------------------------------------------
/FSCI-2017.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts ideas about what I am planning to contribute to the [FORCE11 Scholarly Communication Institute (FSCI)](https://www.force11.org/fsci) this summer (July 30 - August 4 in San Diego). This document is evolving — see [this version](https://github.com/Daniel-Mietchen/events/commit/4c2e05c48d104e6d32953c572f15000632ec8d5f#diff-e78435fc50601cd8eead924eb84c05fe) for the original submission.
4 |
5 | # Afternoon Elective Course
6 |
7 | Afternoon Elective Courses are six hours long and will be presented in three-hour sessions on consecutive afternoons (i.e. Monday-Tuesday and Wednesday-Thursday).
8 |
9 | ## Title
10 |
11 | Integrating Wikidata with research and curation workflows
12 |
13 | ## Abstract
14 |
15 | Wikidata is becoming a hub for structured data across a wide range of research fields, from cultural heritage ( cf. http://www.oxfordaspiremuseums.org/blog/wikidata ) to biomedicine (cf. http://blog.wikimedia.de/2014/10/22/establishing-wikidata-as-the-central-hub-for-linked-open-life-science-data/ ). Since it is also multilingual, it has been described as the Rosetta stone of the linked open data age (cf. http://lab.cccb.org/en/wikidata-the-new-rosetta-stone/ ).
16 |
17 | This workshop aims to introduce participants to Wikidata and to highlight how it can and does contribute to workflows in or near the participants' fields of research. It builds on similar workshops given in the past to various audiences — from librarians to economists to scientists and museum professionals — on how research workflows can be integrated with Wikimedia workflows (see https://en.wikipedia.org/wiki/User:Daniel_Mietchen/Talks/ for an overview and http://uksglive.blogspot.de/2015/04/daniel-mietchen-wikimedia-and-scholarly.html or
18 | http://www.zew.de/en/das-zew/aktuelles/dr-daniel-mietchen-wikimedia-experte-fuer-open-science-spricht-beim-zew-research-seminar/ or https://en.wikipedia.org/wiki/User:Daniel_Mietchen/Talks/ZBW_2013/Workshop
19 | or http://www.eccb12.org/T6 for examples).
20 |
21 | Since the launch of Wikidata in late 2012, the potential of integrating Wikidata with research and curation workflows has been explored through a number of activities, e.g. a grant proposal (cf. https://doi.org/10.3897/rio.1.e7573 ), several workshops (e.g.
22 | https://www.wikidata.org/wiki/Wikidata:WikiProject_Ontology/Biocuration_2016 ) as well as initiatives to collect on Wikidata the metadata of scholarly references cited on Wikimedia projects (cf.
23 | https://meta.wikimedia.org/wiki/WikiCite ) or of all notable paintings (cf. https://www.wikidata.org/wiki/Wikidata:WikiProject_sum_of_all_paintings ).
24 |
25 | The course would consist of two parts:
26 | - the first afternoon is introductory and will provide the basics in terms of research and curation-related workflows on Wikidata;
27 | - the second afternoon is more hands-on, focusing on integrating some exemplary discovery and curation workflows with Wikidata, which will be drawn from experiences shared by course participants.
28 |
29 | ## Proposed level:
30 |
31 | - Beginner
32 |
33 | ## Any limits on participation
34 |
35 | The first part assumes no prerequisites other than some familiarity with research and curation workflows. Bringing a mobile Web-enabled device (e.g. laptop, tablet, smartphone) is recommended but not required.
36 |
37 | Additional requirements for the second part are active participation in the first one, and bringing a Web-enabled device (ideally a laptop).
38 |
39 | Besides seats, tables and power outlets for everyone in the room, a stable WiFi would be needed, and for the speaker a projector and a stable Ethernet connection. Access to an A/V system would be beneficial but is not necessary.
40 |
41 | ## Intended audience
42 |
43 | - researchers and librarians from any field
44 | - curators of digital information
45 | - anyone interested in workflows
46 | - students of any of the above
47 |
48 | ## Contributions from the course to the Friday afternoon plenary session
49 |
50 | Selected outputs from the Afternoon Courses will be communicated to the full group of participants on the Friday afternoon. All participants of the course are encouraged to think about what that might be. Cross-fertilization with other courses they participate in — morning or afternoon, or even beyond FSCI — is highly encouraged.
51 |
52 | # Miscellaneous
53 |
54 | The following topics are not part of this course but additional interests of mine that I invite FSCI participants to engage with.
55 |
56 | * [Bug reports to science](https://github.com/br2s/bug-reports-to-science)
57 | * [Data sharing in public health emergencies](https://github.com/Daniel-Mietchen/events/blob/master/IMED-2016.md)
58 | * [Institutional openness](https://openscience.ub.uni-bielefeld.de/882/what-can-research-institutions-do-to-encourage-open-science)
59 | * [Machine-actionable DMPs](http://www.slideshare.net/StephanieSimms/making-dmps-actionable-and-public)
60 | * [Making ethics data FAIR](https://github.com/Daniel-Mietchen/events/blob/master/PIDapalooza.md)
61 | * [Making Jupyter notebooks reproducible](https://github.com/sparcopen/open-research-doathon/issues/25)
62 | * [Publishing the research process (as opposed to just the results)](https://doi.org/10.3897/rio.1.e7547)
63 | * [Open Science Museum](https://github.com/Daniel-Mietchen/open-science-museum)
64 | * [Open Science Q & A](https://openscience.ub.uni-bielefeld.de/)
65 | * openness as a means to reduce bureaucracy
66 | * [Organizing a doathon](https://github.com/sparcopen/Open-Research-doathon)
67 | * policy hacking, i.e. forking existing or draft policies and adapting their text and associated materials for specific needs, or drafting new policies from scratch
68 | * [Scholia](https://arxiv.org/abs/1703.04222)
69 | * [WikiCite](https://meta.wikimedia.org/wiki/WikiCite)
70 |
71 |
--------------------------------------------------------------------------------
/FSCI-2018.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts my submission to the [FORCE11 Scholarly Communication Institute (FSCI)](https://www.force11.org/fsci) in summer 2018 (July 30 - August 3) in San Diego. It is based on an afternoon elective that was given during FSCI 2017 (see [notes](https://www.wikidata.org/wiki/User:Daniel_Mietchen/FSCI_2017)) and will be evolving until FSCI 2018 and possibly beyond.
4 |
5 | Submission deadline was January 8, 2018, Pacific Time. I submitted a few hours before that.
6 |
7 | After collecting some personal information, the submission form has the following fields.
8 |
9 | # Course title
10 |
11 | *Please give a descriptive and catchy title for your course. Try to give a sense of the kind of course, what activities it will involve, the level, and subject matter. Examples include "Practical approaches to Data Management: An exercise based class for beginners" or "The cutting edge of publishing technologies: A test drive of the latest technology for advanced users".*
12 |
13 | Integrating Wikidata with your research and curation workflows
14 |
15 | # Describe the type of class you plan
16 |
17 | *FSCI has two types of courses. Long courses run in the morning Monday to Friday, for a total of 13-14 hours. Short courses run for two afternoon slots for a total of six hours on each of the Monday-Tuesday and/or Wednesday -Thursday. We expect most short courses to run twice.*
18 |
19 | - [x] Long course
20 | - [ ] Short course
21 |
22 | # Abstract
23 |
24 | *Please provide a course abstract of 250-500 words. It should describe the content of the course in detail, its target audience and the kinds of activities that will be included. Examples of course abstracts for 2017 can be found at [www.force.org/fsci/2017/course-abstract](http://www.force.org/fsci/2017/course-abstract) (note: that URL is broken now).*
25 |
26 | [Wikidata](https://wikidata.org/) is becoming a [hub](https://tools.wmflabs.org/hub/) for structured data across a wide range of research fields, from [cultural](http://blogs.bodleian.ox.ac.uk/digital/author/poulterm/) [heritage](https://medium.com/@alexstinson/wikidata-in-collections-building-a-universal-language-for-connecting-glam-catalogs-59b14aa3214c) to [biomedicine](https://www.slideshare.net/andrewsu/bosc2017-using-wikidata-as-an-open-communitymaintained-database-of-biomedical-knowledge). Since it is also multilingual, it has been described as the [Rosetta stone of the linked open data age](http://lab.cccb.org/en/wikidata-the-new-rosetta-stone/).
27 |
28 | This course aims to introduce participants to Wikidata and to highlight how it can and does contribute to workflows in or near the participants' fields of research. Prototyped at FSCI 2017, it builds on similar workshops given in the past to various audiences — from librarians to economists to scientists and museum professionals — on how research workflows can be integrated with Wikimedia workflows.
29 |
30 | Since the launch of Wikidata in late 2012, the potential of integrating it with research and curation workflows has been explored through a number of activities, e.g. initiatives to collect on Wikidata information about [paintings](https://www.wikidata.org/wiki/Wikidata:WikiProject_sum_of_all_paintings), [pathways](https://www.wikidata.org/wiki/User:ProteinBoxBot/SPARQL_Examples#Wikidata_-%3E_Wikipathways), [politicians](https://www.mysociety.org/democracy/everypolitician/), [proteins](https://www.wikidata.org/wiki/User:ProteinBoxBot/SPARQL_Examples#Uniprot_-%3E_Wikidata) or [publications](https://meta.wikimedia.org/wiki/WikiCite) as well as [workshops](https://www.wikidata.org/wiki/Wikidata:WikiProject_Ontology/Biocuration_2016) or [grant](https://doi.org/10.3897/rio.1.e7573) [proposals](http://sulab.org/2017/07/the-gene-wiki-project-looking-to-the-future-v-2017/).
31 |
32 | The course consists of the following parts:
33 | - the first morning is introductory and will provide the basics in terms of research and curation-related workflows on Wikimedia projects like Wikipedia, Wikimedia Commons, Wikisource and Wikidata;
34 | - the second morning will zoom in on Wikidata and on extracting research-related information from it;
35 | - the third morning will focus on participants contributing or otherwise curating some Wikidata content in their domains and languages of choice;
36 | - the remainder of the course will explore how various aspects of Wikidata (e.g. Wikidata identifiers, APIs, SPARQL endpoint, multilinguality, the Wikibase software, apps and tools) can be integrated with research-related workflows, drawing on scenarios provided by course participants.
37 |
38 | A version of this abstract can be found at https://github.com/Daniel-Mietchen/events/blob/master/FSCI-2018.md .
39 |
40 |
41 | # Prerequisite knowledge and experience
42 |
43 | *Please give an indication of the knowledge, experience, or interests you expect your students to have at the beginning of your course. Is this a course for beginners? For students? Faculty? Experienced researchers? People who have experience working in journals? Etc. Is there some preparatory work that will be required?*
44 |
45 | The course assumes no prerequisites other than some familiarity with research and curation workflows. It is aimed at
46 | - researchers and librarians from any field;
47 | - other curators of digital information;
48 | - anyone interested in workflows;
49 | - students of any of the above.
50 |
51 | # Requirements
52 |
53 | *Do you have any technical requirements for your course? Is there any special equipment students will need? Special software they will have to install? (we ask you to keep the requirements for students to the minimum necessary). Do you need any special teaching aids?*
54 |
55 | Participants are strongly encouraged to register a Wikidata account at least one week prior to the course (otherwise, some Wikidata functionality might not be available to them) and to bring a mobile Web-enabled device (e.g. laptop, tablet, smartphone).
56 |
57 | Besides seats, tables and power outlets for everyone in the room, a stable WiFi would be needed, and for the speaker a projector and a stable Ethernet connection. Access to an A/V system would be beneficial but is not essential.
58 |
59 | # Have you given this course previously?
60 |
61 | *Is this a new course or has it been run previously, either at FSCI or at another venue? Both new and existing courses are welcome at FSCI.*
62 |
63 | - [ ] No, this is a new course
64 | - [x] Yes, a previous version of this course was given at FSCI2017
65 | - [ ] Yes, a previous version of this course has been given elsewhere (please give details below)
66 |
67 | # If this course has been given elsewhere, please give details below
68 |
69 | # Please give a short description of your teaching experience
70 |
71 | I have taught parts of a few (mainly undergrad) courses on topics like vocal communication or brain morphometry, and given dozens of workshops on the integration between research and Wikimedia workflows.
72 |
73 | # Who else will be contributing to your course?
74 |
75 | *Please name others (if applicable) who will be contributing to this course*
76 |
77 | The course will make active use of Wikidata, so contributions from the Wikidata community are probable and could perhaps also be [solicited if needed](https://www.wikidata.org/wiki/Wikidata:Request_a_query). Furthermore, there are some active Wikidata contributors based in San Diego, and I would welcome some interaction between them and the course participants.
78 |
79 | # Support for instructor(s)
80 |
81 | *FSCI will attempt to support reasonable requests for technical support. In addition, it will provide complimentary tuition (allowing you to attend other classes when you are not teaching), housing (up to five nights, single room in a shared apartment), and meals (Mon-Fri) for 1 instructor in each course. We cannot guarantee travel reimbursement, although we are seeking funding to at least partially support travel by for instructors in need with emphasis on supporting those from Mid and Low Income Economies, and hardship cases.*
82 |
83 | - [x] I have read and understand the support FSCI can provide to instructors.
84 | - [x] I won't be able to teach a course without travel support.
85 |
86 | # Please use this space for any additional comments
87 |
88 | I would be interested in providing a Wikidata component to courses offered by other instructors.
89 |
--------------------------------------------------------------------------------
/Fachtagung-Katastrophenvorsorge-2020.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts information regarding my contributions to the [German Conference on Disaster Risk Reduction](https://www.fachtagung-katastrophenvorsorge.de/2020/index_en) — the "[Fachtagung Katastrophenvorsorge 2020](https://www.fachtagung-katastrophenvorsorge.de/2020)" — which is the 2020 edition of an annual event in Germany focused on disaster preparedness, which is to take place on 19-20 October 2020 in Berlin and online, as per [this ticket](https://github.com/Daniel-Mietchen/events/issues/678).
4 |
5 | One way to contribute to the event is to organize a workshop, for which they issued a call with an (extended) deadline of May 22 (as per [this ticket](https://github.com/Daniel-Mietchen/events/issues/679)), by which I submitted my proposal. Apart from personal data about me and potential affiliations (where I chose [Wikimedians for Disaster Response](https://meta.wikimedia.org/wiki/Wikimedians_for_Disaster_Response)), they had the following questions, which I am pasting in here in their German original, along with my responses (also in German). They also asked which language the workshop would be in, where I picked the "both English and German" option, as I plan to have the slides in English but will be flexible in using English or German as needed or as the participants prefer.
6 |
7 | On June 19, I was notified that the proposal has been accepted, that all workshops will be 90 minutes long and remote and be recorded and that plannings are underway to work out details. I replied that I am fine with these arrangements. By September 8, the program of the event was [online](https://www.fachtagung-katastrophenvorsorge.de/2020/programm), with [several workshops](https://www.fachtagung-katastrophenvorsorge.de/2020/workshops), including [this one](http://web.archive.org/web/20201018000745/https://www.fachtagung-katastrophenvorsorge.de/2020/ws_wikimedians).
8 |
9 | # Archive
10 |
11 | A copy of the presentation has been uploaded to [http://doi.org/10.5281/zenodo.4105179](http://doi.org/10.5281/zenodo.4105179).
12 |
13 | # Workshop submission form questions
14 |
15 | ## Sind noch weitere Organisationen / Partner beteiligt? Soweit bereits bekannt, bitten wir um Angabe der jeweiligen Organisation sowie den vollständigen Namen der Ansprechpartner*innen
16 |
17 | Innerhalb des Ökosystems in und um Wikipedia sind vor allem Individuen in ihrer Freizeit aktiv, die sich in verschiedensten Formen organisieren (z.B. als Wikimedians for Disaster Response oder als WikiProject COVID-19), welche nur selten eine juristische Person involvieren. Unter letzteren sind im Kontext dieser Veranstaltung vor allem Wikimedia Medicine sowie Wikimedia Deutschland zu nennen. Mit beiden bin ich in stetigem Kontakt, doch sind sie an dieser Einreichung bislang nicht beteiligt. Während die informellen Organisationen und auch Wikimedia Medicine vor allem inhaltlich tätig sind, leistet Wikimedia Deutschland vor allem Unterstützung für die Freiwilligenarbeit, z.B. durch Übernahme von Reisekosten oder Bereitstellung von Räumlichkeiten.
18 |
19 |
20 | ## Zu welchem Thema möchten Sie einen Workshop anbieten? Welche Erfahrungen haben die Organisator*innen bereits damit gesammelt?
21 |
22 | Thema: Beiträge des Wikipedia-Ökosystems zu Katastrophenvorsorge und -management
23 |
24 | Erfahrungen: Ein ähnlicher Workshop fand in Deutschland Anfang 2018 in Berlin statt - siehe https://de.wikipedia.org/wiki/Portal:Katastrophenschutz/Veranstaltungen/Workshop_zu_Wikimedia_und_Katastrophenmanagement_2018 . International gibt es noch mehrere Beispiele, die unter https://meta.wikimedia.org/wiki/Wikimedians_for_Disaster_Response/Events gelistet sind.
25 |
26 |
27 | ## Beschreibung des Zieles und der Art des Workshops
28 |
29 | Ziele: Workshop-Teilnehmer sollen durch diesen Workshop (i) einen Eindruck erhalten, auf welche Weisen das Wikipedia-Ökosystem zu Katastrophenvorsorge und -management beiträgt, (ii) angeregt werden, ihre Erfahrungen mit Kommunikation bzw. Wissensvermittlung in Katastrophenkontexten in das Wikipedia-Ökosystem einfliessen zu lassen.
30 |
31 | Zielgruppe: Tagungsteilnehmer, die beruflich oder ehrenamtlich mit Kommunikation und/ oder Wissensvermittlung rund um Katastrophenthemen zu tun haben
32 |
33 | Format: Einleitender Vortrag von mir (mit Demos, insgesamt ca. 30 Minuten), dann Gruppenarbeit (Begutachtung von Wikimedia-Inhalten, ca. 30 Minuten), anschliessend Diskussion und gemeinsame Besprechung verschiedener Praxisbeispiele aus der Katastrophenvorsorge mit Fokus auf digitale Elemente und Integrationspotential mit Wikimedia-Inhalten.
34 |
35 | # Notes
36 |
37 | ## For the workshop itself: Etherpad
38 |
39 | * [https://etherpad.wikimedia.org/p/Fachtagung-Katastrophenvorsorge-2020-Wikipedia](https://etherpad.wikimedia.org/p/Fachtagung-Katastrophenvorsorge-2020-Wikipedia)
40 | - background: [Das Etherpad-Prinzip weitergeführt: 5 Tools für spezifische Kollaborationsherausforderungen](https://ebildungslabor.de/blog/etherpadprinzip/)
41 |
42 | ## For preparing the workshop
43 |
44 | * Think about
45 | - privacy notice regarding all the tools/ channels used
46 | - spam
47 | - a round of introductions
48 | - mentimeter-like quick surveys/ "show of hands", perhaps directly in the Etherpad, using emoji
49 | - gibt es TeilnehmerInnen, die an dem Workshop nicht teilnehmen koennten, wenn er nur auf Englisch waere?
50 | - anyone not comfortable if this workshop were run in German only?
51 | - brief biosketch/ interests/ contact info, directly in the etherpad or ethercalc
52 | - [ethercalc demo](https://ethercalc.net/fpcesl1hzpl6)
53 | - little exercise
54 | - make sure everyone has something to drink
55 | - let them share where they got the vessel that they are drinking it from (e.g. coffee cup)
56 | - [ethermap test](https://getethermap.org/m/test-for-fachtagung-katastrophenvorsorge)
57 | - use this later to generate a Wikidata-powered map of locations represented at the event
58 | - the moment of silence after the end of the presentation part
59 | - could be alleviated by
60 | - encouraging Q & A in the Etherpad already during the presentation
61 | - displaying
62 | - an overview of some key images from the presentation
63 | - some version of a key issue that came up early in the presentation
64 | - pauses
65 | - in the presentation
66 | - for stretching
67 | - group work
68 | - registration form
69 | - upon registration for the conference, the registration form asked
70 | - > "In einem Satz, was interessiert sie an der Fachtagung besonders und zu welchem Thema möchten Sie sich mehr austauschen?"
71 | - to which I responded
72 | - > "🇬🇧 I am particularly interested in the integration of classical disaster preparedness and response with digital platforms, communities and workflows, especially those of the Wikipedia ecosystem, citizen science and OpenStreetMap. / 🇩🇪 Ich bin speziell an der Verzahnung klassischer Katastrophenvorsorge mit digitalen Plattformen, Communitys und Arbeitsabläufen interessiert, insbesondere mit dem Wikipedia-Ökosystem, Bürgerwissenschaften und OpenStreetMap."
73 |
74 | ## Still to consider for potential incorporation
75 |
76 | * https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Disaster_management
77 | * https://www.wikidata.org/wiki/Wikidata:WikiProject_Humanitarian_Wikidata
78 | * https://de.wikipedia.org/wiki/Wikipedia:WikiCon_2018/Programm/Katastrophen_und_Katastrophenmanagement
79 | - also [here](https://docs.google.com/presentation/d/e/2PACX-1vQJLMKVEyOX5-loE_91d5iL8TwZLflxO8RffzRzcqnPhFgSM1Bd007I18G5KEIW1ail79pMyU05afzj/pub?start=false&loop=false&delayms=3000#slide=id.g3560b8a584_2_75)
80 | * [The human cost of disasters: an overview of the last 20 years (2000-2019) ](https://www.undrr.org/publication/human-cost-disasters-overview-last-20-years-2000-2019)
81 | - [sample figure on most impactful disaster types over the last decade](https://twitter.com/UNDRR/status/1316543954125545472)
82 | * some disaster-related lexemes
83 | * https://pageviews.toolforge.org/mediaviews/?project=commons.wikimedia.org&platform=&referer=all-referers&start=2015-01-01&end=2020-10-17&files=7042_lores-Ebola-Zaire-CDC_Photo.jpg
84 | * OSM Mapathon tonight
85 | * WikiProject COVID-19
86 | - https://en.wikipedia.org/wiki/Template:COVID-19_pandemic
87 | - https://en.wikipedia.org/wiki/Wikipedia%27s_response_to_the_COVID-19_pandemic
88 | - some COVID-19 visualizations
89 | * Bing/ NYT coverage of Ebola
90 | * Wikimedians organize themselves
91 | * Bias, e.g. as per [Uneven Coverage of Natural Disasters in Wikipedia: the Case of Flood](https://arxiv.org/abs/2001.08810)
92 |
93 | # See also
94 |
95 | * [How Wikipedia became a trusted source for COVID-19 information](https://www.youtube.com/watch?v=42n6igyp-Fk)
96 | * [Wikipedia:Meetup/Online edit-a-thon SDGs September 2020](https://en.wikipedia.org/wiki/Wikipedia:Meetup/Online_edit-a-thon_SDGs_September_2020)
97 |
--------------------------------------------------------------------------------
/Force-2017-Wikimania-in-Africa.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This is a submission to the [Force 2017](https://www.force2017.org/) conference to be held on October 25-27 in Berlin.
4 |
5 | # Title
6 |
7 | Wikimania in Africa - an opportunity for engaging communities of researchers, practitioners and Wikimedians
8 |
9 | # Type of activity
10 |
11 | Session: 30-45 min time slot
12 |
13 | # Abstract
14 |
15 | Africa is often neglected in scholarly discourse, be it as a source of expertise, ideas, and technology or as a topic for study. Wikimania - the annual meeting of the people behind Wikipedia and its sister projects - will take place in South Africa in July 2018, hosted by the University of Cape Town. In this session, we want to explore ways in which this event could be used to catalyze new interactions between researchers, practitioners and Wikimedians from Africa and around the world.
16 |
17 | # URL to existing project
18 |
19 | https://github.com/Daniel-Mietchen/events/blob/master/Force-2017-Wikimania-in-Africa.md (i.e. this page here on GitHub)
20 |
21 | # Format
22 |
23 | Landscape mapping
24 |
25 | # Preferred length
26 |
27 | 60-75 min
28 |
29 | # Themes
30 |
31 | * Increasing diversity
32 | * New forms of communication
33 | * Outreach
34 |
35 | # Force11 working groups (where applicable)
36 |
37 | * Scholarly Commons Working Group
38 |
39 | # Presenters
40 |
41 | * Daniel Mietchen, University of Virginia, http://orcid.org/0000-0001-9488-1870
42 |
43 | # Additional information
44 |
45 | https://github.com/Daniel-Mietchen/events/blob/master/Force-2017-Wikimania-in-Africa.md
46 |
47 | * [session notes](https://docs.google.com/document/d/19F7ZbK6n2oYZfDMYFU8Fyf0GsG2tMULGDrp-i7fms1M/edit)
48 |
49 |
--------------------------------------------------------------------------------
/Force-2017-discovery-tools.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This is a session at the [Force 2017](https://www.force2017.org/) conference held on October 25-27 in Berlin.
4 |
5 | # Title
6 |
7 | Changing the way we discover research
8 |
9 | # Type of activity
10 |
11 | Session: 60 min time slot
12 |
13 | Thursday, 26 October 2017, 12:30-13:30
14 |
15 | Room 3, Kalkscheune, Johannisstraße 2, 10117 Berlin, Germany
16 |
17 | # Presenters
18 |
19 | * [Daniel Mietchen](https://twitter.com/PeterKraker/status/923509051044040704), University of Virginia, http://orcid.org/0000-0001-9488-1870
20 | * [Peter Kraker](https://twitter.com/StephanJanosch/status/923505017314795520), Open Knowledge Maps, https://orcid.org/0000-0002-5238-4195 ([pic]())
21 |
22 | # Abstract
23 |
24 | Open science enables new discovery tools and processes by providing open resources and an ever-growing digital infrastructure to build upon. However, we haven’t seen the paradigmatic change that has happened in other steps of the research cycle. In this workshop, we want to review the discovery workflow for an open science, and develop concrete recommendations for next steps. Through hands-on exercises using tools such as Scholia and Open Knowledge Maps, we will explore the emerging ecosystem around open discovery, define needs and requirements, and extract missing functionality and interoperability. Starting from the formally published research literature, we will look beyond and analyse the role and potential of grey literature as well as initiatives such as open annotation, data and software citation, collaborative reference management and resource identification for discovery.
25 |
26 | With an emerging landscape of both commercial and non-profit offers, we will also discuss what it means to be open in terms of exploration and discovery. In addition, we will take a look at collaborative solutions for what is currently a mostly individualistic process. The outcome of the workshop will be a model for the discovery process in the age of open science, complete with a mapping of current and emerging practices and tools, as well as missing links and low-hanging fruits. With this, we want to set out a roadmap for open discovery for the immediate future.
27 |
28 | # Format
29 |
30 | Presentations and demos, scenario and workflow building
31 |
32 | # Themes
33 |
34 | Building new workflows
35 |
36 | # Schedule
37 |
38 | #### 12:30 - 12:40 Welcome and warm-up
39 |
40 | * **Exercise:** Get together in groups of two/three and discuss the following questions: How do you get an overview of a unknown research field? What are the problems and challenges that you are facing?
41 |
42 | * Record problems and challenges here: https://is.gd/force2017
43 |
44 | #### 12:40 - 12:50 Introduction to discovery
45 |
46 | * **Presentation (Peter):**
47 | * Publication Feeds and BuRST: a personal story about discoverability
48 | * Dark knowledge - hidden in plain sight
49 | * Insights from a survey on discovery
50 | * Open Knowledge Maps and collaborative discovery
51 |
52 | #### 12:50 - 13:00 Discovery in an open science
53 |
54 | * **Presentation (Daniel):**
55 | * [Wikidata as a reference management platform](https://meta.wikimedia.org/wiki/WikiCite)
56 | * [Scholia](https://tools.wmflabs.org/scholia/): resource discovery via SPARQL
57 |
58 | #### 13:00 - 13:15 Discovery tools
59 |
60 | * **Exercise:** In your group, inspect a discovery tool (sourced from e.g. 101 Innovations database) and rate it on several aspects of openness:
61 | * accessibility
62 | * source code
63 | * data
64 | * content
65 | * shareability of the results of the discovery process
66 | * annotation/comments
67 | * collaborative features
68 | * other
69 |
70 | * Record your answers here: https://is.gd/force2017
71 |
72 | #### 13:15 - 13:30 Open discovery workflow
73 |
74 | * **Exercise:** Describe an open discovery scenario (a model workflow) for a typical discovery task, e.g.:
75 | * Getting an overview of a field
76 | * Collecting a body of evidence for a certain question
77 | * Keeping an overview of a field
78 | * ...
79 |
80 | * Record the scenario here: https://is.gd/force2017
81 |
82 |
83 | # URL to existing project
84 |
85 | https://github.com/Daniel-Mietchen/events/blob/master/Force-2017-discovery-tools.md (i.e. this page here on GitHub)
86 |
87 | # Force11 working groups (where applicable)
88 |
89 | # Additional information
90 |
91 | https://github.com/Daniel-Mietchen/events/blob/master/Force-2017-discovery-tools.md
92 |
93 |
--------------------------------------------------------------------------------
/ICEI2018-SDGs.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a contribution to the [10th International Conference on Ecological Informatics](http://icei2018.uni-jena.de/) taking place on 24-28 September 2018 in Jena and specifically the Session S3.6 ["Efficient data and workflow management for reaching Sustainable Development Goals (SDGs) targets associated to biodiversity and ecosystems"](https://icei2018.uni-jena.de/session/s3-6-sustain-development-goals-sdg/) at 10:30 - 12:30 on Tuesday 25 September 2018 in Lecture Hall 5.
4 |
5 | # Title
6 |
7 | * Community-curated Linked Open Data about the Sustainable Development Goals, their targets and indicators
8 |
9 | # Submission abstract
10 |
11 | The targets and indicators associated with the [Sustainable Development Goals](https://sustainabledevelopment.un.org/sdgs) form a complex network of relationships between policy and practice, aspirations and achievements across domains and around the globe. This poses challenges for monitoring, evaluating and communicating progress towards these goals. Wikidata is a Linked Open Data platform that is developed and curated collaboratively by the Wikimedia community as a sister project to Wikipedia. Extending across disciplinary boundaries, it contains information about many of the concepts related to the Sustainable Development Goals, and the community has begun to map the network of relationships between these concepts.
12 |
13 | Focusing on examples related to biodiversity and ecosystems, this presentation will explore how Wikidata, its semantic core Wikibase and its global multilingual community can be leveraged to represent and contextualize the Sustainable Development Goals as well as the associated targets and indicators in a way that allows people to make use of that information in the language of their choice, for a given country or on a global level. It will be given on the basis of https://github.com/Daniel-Mietchen/events/blob/master/ICEI2018-SDGs.md , which will be updated until and possibly after the event. Special emphasis will be given to practical examples for how Wikidata and Wikibase can help integrate information about efforts addressing different components of the SDGs, or in different contexts.
14 |
15 | # Outline
16 |
17 | 1. [Unstructured representation of information related to the SDGs](ICEI2018-SDGs.md#unstructured-representation-of-information-related-to-the-sdgs)
18 | 2. [Structured representation of information related to the SDGs](ICEI2018-SDGs.md#structured-representation-of-information-related-to-the-sdgs)
19 | 3. [Making SDG-related data FAIR](ICEI2018-SDGs.md#making-sdg-related-data-fair)
20 | 4. [First steps](https://github.com/Daniel-Mietchen/events/blob/master/ICEI2018-SDGs.md#first-steps)
21 | 5. [Outlook](ICEI2018-SDGs.md#outlook)
22 |
23 | # Unstructured representation of information related to the SDGs
24 |
25 | - SDG-related pages at the United nations, e.g. https://www.un.org/sustainabledevelopment/sustainable-development-goals/
26 | - Wikimedia sites
27 | - e.g.
28 | - https://en.wikipedia.org/wiki/Sustainable_Development_Goals
29 | - https://meta.wikimedia.org/wiki/WikiProject_UNESCO/Global_Goals_Discussion
30 | - many other places
31 |
32 | # Structured representation of information related to the SDGs
33 |
34 | - some sites about the SDGs as a group, e.g. http://www.sdgindex.org/
35 | - sites specialized in individual SDGs, targets or indicators, e.g.
36 | - http://childmortality.org/ for Target 3.2 (reducing child mortality)
37 | - https://hi-knowledge.org/invasion-biology/ for Target 15.8 (reducing the impact of invasive species)
38 | - set of ca. 40 key hypotheses in invasion biology
39 | - set of ca. 1000 papers that have been annotated as to the degree to which they support or question any of these hypotheses
40 | - [Ontology Plays a Part in United Nations Sustainable Development Goals Project](http://www.dataversity.net/ontology-has-big-part-to-play-in-united-nations-sustainable-development-goals-project/)
41 | - [Sustainable Development Goals Interface Ontology (SDGIO)](https://github.com/SDG-InterfaceOntology/sdgio)
42 | - imports several existing ontologies (overview on slide 14 of [this presentation](http://ncgia.buffalo.edu/OntologyConference/PPT/Jensen.pdf))
43 | - e.g. [Environmental Ontology (ENVO)](http://bioportal.bioontology.org/ontologies/ENVO)
44 | - some of these are in Wikidata, but not all
45 | - [has no license](https://github.com/SDG-InterfaceOntology/sdgio/issues/112)
46 | - [part of a bigger problem](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/285)
47 |
48 | # Making SDG-related data FAIR
49 |
50 | - FAIR Data Principles: [Findable, Accessible, Interoperable, Reusable](https://doi.org/10.1038/sdata.2016.18)
51 | - [Wikidata is a FAIR platform](https://www.wikidata.org/wiki/Wikidata:WikidataCon_2017/Submissions/Using_Wikidata_to_make_research_data_FAIR)
52 | - Further characteristics of Wikidata
53 | - editable by anyone, including machines
54 | - reusable by anyone for any purpose (as per [CC0](https://creativecommons.org/publicdomain/zero/1.0/))
55 | - multilingual (can handle, integrate and expose data across ca. 300 languages)
56 | - community-driven (ca. [20k contributors per month](https://www.wikidata.org/wiki/Special:Statistics))
57 | - has substantial content about most of the topics covered by SDGs, targets and indicators
58 | - e.g. [recent disasters](https://www.wikidata.org/wiki/Wikidata:WikiProject_Humanitarian_Wikidata/Recent_disasters)
59 |
60 | # First steps
61 |
62 | Multiple SDG-relevant community initiatives (also known as "WikiProjects") have been created, e.g.:
63 | - [WikiProject Sustainable Development](https://www.wikidata.org/wiki/Wikidata:WikiProject_Sustainable_Development)
64 | - [WikiProject Humanitarian Wikidata](https://www.wikidata.org/wiki/Wikidata:WikiProject_Humanitarian_Wikidata)
65 | - [WikiProject Invasive Species](https://www.wikidata.org/wiki/Wikidata:WikiProject_Invasive_Species)
66 | - [WikiProject Ontology](https://www.wikidata.org/wiki/Wikidata:WikiProject_Ontology)
67 | - includes mapping to existing ontologies, e.g.
68 | - [Environment Ontology ID (P3859)](https://www.wikidata.org/wiki/Property:P3859)
69 | - [WikiProject Medicine](https://www.wikidata.org/wiki/Wikidata:WikiProject_Medicine)
70 | - [WikiCite](https://meta.wikimedia.org/wiki/WikiCite)
71 | - allows Wikidata-based literature overviews, e.g. for
72 | - [invasive species](https://tools.wmflabs.org/scholia/topic/Q183368)
73 | - [Zika virus](https://tools.wmflabs.org/scholia/topic/Q202864)
74 | - [child mortality](https://tools.wmflabs.org/scholia/topic/Q61559)
75 | - [maternal mortality](https://tools.wmflabs.org/scholia/topic/Q1339474)
76 | - [waster water](https://tools.wmflabs.org/scholia/topic/Q336191)
77 | - see also talk on Thursday 27 September 2018:
78 | - [Visualizing the research ecosystem of ecosystem research via Wikidata](ICEI2018-research-ecosystem.md)
79 | - Lecture Hall 4, ca. 13:15.
80 | - Session S1.6 [Semantics for biodiversity and ecosystem research](https://icei2018.uni-jena.de/session/s1-6-semantics/), 10:30-14:15
81 |
82 | # Outlook
83 |
84 | - Automatically updated maps that are interactive and editable and come with full provenance
85 | - [demo](https://commons.wikimedia.org/wiki/File:Map_of_disasters_color-coded_by_disaster_type_-_Wikidata_Query_Service_as_of_2018-07-14.png)
86 | - Addressing bias in the data
87 | - [demo](https://commons.wikimedia.org/wiki/File:Wikidata_Map_July_2018_Big.png)
88 | - Collaborative inquiries into the data
89 | - [demo](https://www.wikidata.org/wiki/Wikidata:Request_a_query)
90 |
91 | # See also
92 |
93 | * [ICEI2018.md](ICEI2018.md)
94 | * [ICEI2018-research-ecosystem.md](ICEI2018-research-ecosystem.md)
95 |
96 | # History
97 |
98 | The call for proposals had an [April 15 deadline](http://icei2018.uni-jena.de/calls/), by which I submitted the abstract, which received submission number 147. On May 15, I was notified of its acceptance.
99 |
100 | # Name of the authors
101 |
102 | Daniel Mietchen
103 |
104 | # e-mail-address (please mark corresponding author)
105 |
106 | daniel.mietchen[at]virginia.edu*
107 |
108 | # Affiliations
109 |
110 | Data Science Institute, University of Virginia, Charlottesville, VA, USA
111 |
112 | # Keywords (max. 5)
113 |
114 | - Wikidata
115 | - Wikibase
116 | - multilinguality
117 | - Linked Open Data
118 | - SPARQL
119 |
--------------------------------------------------------------------------------
/ICEI2018-citizen-science.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 |
4 | This file hosts a contribution to the [10th International Conference on Ecological Informatics](http://icei2018.uni-jena.de/) taking place on 24-28 September 2018 in Jena and specifically the Session S3.2 ["Citizen science meets informatics: Data science challenges in ecological research with public participation"](https://icei2018.uni-jena.de/session/s3-2/) at 14:00 - 16:15 on Monday 24 September 2018 in Lecture Hall 5.
5 |
6 | # Title of the abstract/talk
7 |
8 | * Wikimedia projects as citizen science platforms
9 |
10 | # Slide(s)
11 |
12 | * https://www.wikidata.org/wiki/User:Daniel_Mietchen/Talks/ICEI_2018
13 | - A simple way to get there is to just type WD:ICEI2018 into the search box at [https://www.wikidata.org/](https://www.wikidata.org/).
14 |
15 | # Submission abstract
16 |
17 | When searching the web for information on a given topic — say, citizen science — Wikipedia will often come up high in the search results. What is less known is that Wikipedia forms the nucleus of an entire ecosystem of Wikimedia projects that are roughly organized by information channel. Besides the encyclopedia, this includes an archive (Wikisource) and a dictionary (Wiktionary), along with sites dedicated to quotes (Wikiquote), taxa (Wikispecies), media files (Wikimedia Commons), books (Wikibooks), coursework (Wikiversity), news (Wikinews), structured data (Wikidata), software (MediaWiki) or technical infrastructure (Wikimedia Labs).
18 |
19 | While citizen science-related topics form only a small sliver of the content found on these open knowledge platforms, the practice of contributing is similar to that of many citizen science projects: contributors are volunteers who participate in areas of their own interest, in a language of their choice and on their own timeline. The similarities go further, with community-driven collaborations forming around issues that are also in the focus of citizen science projects: the identification and disambiguation of taxa, people or locations, the collection and categorization of photographs, audiovisual materials and historic records, the transcription and translation of such records, the integration and visualization of data, or identifying and locating suitable resources that can help verify information related to any of the above.
20 |
21 | This contribution is intended as a guided tour around such citizen science activities taking place in the framework of Wikimedia projects, both within and across domains of knowledge. Focusing on examples from biodiversity and ecosystems research, it will highlight some data-related issues (e.g. data and metadata quality, data integration) and how they are handled in Wikimedia contexts. The presentation will be given on the basis of https://github.com/Daniel-Mietchen/events/blob/master/ICEI2018-citizen-science.md , which is complemented by https://www.wikidata.org/wiki/User:Daniel_Mietchen/Talks/ECEI_2018 . Participants are encouraged to bring their laptops, as they will be invited to actively engage with Wikimedia-based information in their domain, as well as to entertain and share ideas on how they could integrate it with their own activities.
22 |
23 | # Notes from drafting
24 |
25 | - Wikidata
26 | - Wikibase
27 | - games
28 | - exists in about 300 languages
29 | - OSM
30 | - [example](https://twitter.com/wolfgang8741/status/980932826441928704)
31 |
32 | # See also
33 |
34 | * [ICEI2018.md](ICEI2018.md)
35 | * [ICEI2018-research-ecosystem.md](ICEI2018-research-ecosystem.md)
36 | * [Wikimedia projects and citizen science](https://www.wikidata.org/wiki/User:Daniel_Mietchen/ECSA_2018)
37 |
38 | # History
39 |
40 | The call for proposals had an [April 15 deadline](http://icei2018.uni-jena.de/calls/), by which I submitted the abstract, which received the submission number 144. It was accepted on May 9, though that message reached me only on May 16.
41 |
42 | # Name of the authors
43 |
44 | Daniel Mietchen
45 |
46 | # e-mail-address (please mark corresponding author)
47 |
48 | daniel.mietchen[at]virginia.edu*
49 |
50 | # Affiliations
51 |
52 | Data Science Institute, University of Virginia, Charlottesville, VA, USA
53 |
54 | # Keywords (max. 5)
55 |
56 | - Wikipedia
57 | - Wikimedia Commons
58 | - Wikidata
59 | - collaboration
60 | - open knowledge
61 |
--------------------------------------------------------------------------------
/ICEI2018.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | The [10th International Conference on Ecological Informatics](http://icei2018.uni-jena.de/) is taking place on 24-28 September 2018 in Jena.
4 |
5 | # Presentations
6 |
7 | I am giving the following three presentations:
8 |
9 | * [Wikimedia projects as citizen science platforms](ICEI2018-citizen-science.md)
10 | - Monday 24 September 2018, Lecture Hall 5, ca. 16:00.
11 | - Session S3.2 [Citizen science meets informatics: Data science challenges in ecological research with public participation](https://icei2018.uni-jena.de/session/s3-2/), 14:00 - 16:15.
12 | * [Community-curated Linked Open Data about the Sustainable Development Goals, their targets and indicators](ICEI2018-SDGs.md)
13 | - Tuesday 25 September, Lecture Hall 5, ca. 11:15.
14 | - Session S3.6 [Efficient data and workflow management for reaching Sustainable Development Goals (SDGs) targets associated to biodiversity and ecosystems](https://icei2018.uni-jena.de/session/s3-6-sustain-development-goals-sdg/), 10:30-12:30
15 | * [Visualizing the research ecosystem of ecosystem research via Wikidata](ICEI2018-research-ecosystem.md)
16 | - Thursday 27 September, Lecture Hall 4, ca. 13:15.
17 | - Session S1.6 [Semantics for biodiversity and ecosystem research](https://icei2018.uni-jena.de/session/s1-6-semantics/), 10:30-14:15.
18 |
19 | # Notes
20 |
21 | My notes on the event sit at https://github.com/Daniel-Mietchen/events/issues/338 . I will also keep an eye on the [#ICEI2018](https://twitter.com/search?f=tweets&vertical=default&q=ICEI2018) hashtag.
22 |
23 | # History
24 |
25 | The call for proposals had an [April 15 deadline](http://icei2018.uni-jena.de/calls/), by which I submitted the abstracts to the above sessions, as sketched out in [this ticket](https://github.com/Daniel-Mietchen/events/issues/339).
26 |
27 |
--------------------------------------------------------------------------------
/IDCC17.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file is a contribution to the [12th International Digital Curation Conference (IDCC17)](http://www.dcc.ac.uk/drupal/events/idcc17) taking place in Edinburgh on 20 - 23 February 2017, and specifically its Workshop 1, "[A postcard from the future: tools and services from a perfect DMP world](http://www.dcc.ac.uk/events/idcc17/workshops#workshop1)" (DMP stands for [Data Management Plan](https://en.wikipedia.org/wiki/Data_management_plan)).
4 |
5 | The workshop organisers have asked participants for various input beforehand, including responses to the following three questions:
6 |
7 | 1. Why are you motivated / excited / required to work on data management / DMPs?
8 | - I am interested in integrating research workflows with the Web to facilitate collaboration amongst and between humans and machines. Data form a key component of such workflows, and data management plans can assist in handling research data all along their life cycle.
9 |
10 | 1. What are your pain points?
11 | - DMPs are often treated as yet another bureaucratic layer in the research ecosystem, while their potential to actually make research more efficient through better data management remains largely untapped.
12 | - DMPs are usually neither machine actionable nor properly versioned nor public. In contrast, in ever more contexts of our lives, it is becoming routine to have almost instant and occasionally even user-friendly access to information about things of interest. Take trains, for example: in many areas, the course of railways and the location of train stations along the way can easily be looked up using various means, and the same goes for time tables and itineraries as well as for delays or detours. Basically any person or machine can look that up for any train, be they on a train or not. Now replace the trains by research objects like data: their whereabouts are typically only known to their train's driver and not, e.g., to the stations or to drivers of other trains, at least not until months or years have gone by. I see machine actionable, versioned and public DMPs as a way to move research closer to the transport scenario and beyond.
13 | - I am not aware of anyone having tested the extent to which aggregation of multiple DMPs or parts thereof could provide new opportunities to discover and engage with the underlying data, including at scale.
14 |
15 | 1. What do you hope to get out of this workshop?
16 | - Getting a better overview of what others are doing in this space.
17 | - Ideas for next steps in terms of assessing the usefulness of DMPs that are any, neither or all of machine actionable, versioned and public.
18 |
--------------------------------------------------------------------------------
/International-Data-Week-2018.md:
--------------------------------------------------------------------------------
1 | [International Data Week 2018](http://internationaldataweek.org/programme-overview) combined a number of events around data, particularly research data.
2 |
3 | I was mainly involved in three of them
4 | - [SciDataCon 2018](https://www.scidatacon.org/IDW2018/programme/) — see the SciDataCon sessions in the schedule below
5 | - see my notes specifically on this at [SciDataCon-2018.md](SciDataCon-2018.md)
6 | - [12th Plenary of the Research Data Alliance](http://www.internationaldataweek.org/rda-12th-plenary) — see the RDA sessions in the schedule below
7 | - [World Data Science Data Repositories Day 2018](https://www.icsu-wds.org/events/wds-events/data-repositories-day-2018) — see the WDS session in the schedule below
8 |
9 | but also attended parts of [UVA/DSI Data Palooza 2018](https://dsi.virginia.edu/datapalooza2018) remotely.
10 |
11 | See [here](https://github.com/Daniel-Mietchen/events/issues/211) for my notes taken throughout the week.
12 |
13 | # Sessions I was involved in
14 |
15 | *Times marked in **bold** indicate an overlap*
16 |
17 | - [Poster session](https://www.scidatacon.org/IDW2018/posters/)
18 | - Monday, 5 November at 17:30-20:00
19 | - [My posters](https://www.wikidata.org/wiki/User:Daniel_Mietchen/International_Data_Week_2018):
20 | - RDA poster 7 ["Ten principles for machine-actionable data management plans"](https://doi.org/10.5281/zenodo.1461712) ([in action](https://twitter.com/GigaScience/status/1059447556684607488)) and RDA breakout 3 session "[Use cases for machine-actionable data management plans](https://www.rd-alliance.org/wg-dmp-common-standards-rda-12th-plenary-meeting)" on Tuesday
21 | - SciDataCon poster 168: [WikiCite and Scholia - a Linked Open Data approach to exploring the scholarly literature and related resources](https://www.scidatacon.org/IDW2018/sessions/264/poster/168/) (General SciDataCon Poster Session with ID 264, taking place on 5 November at 17:30-20:00 in Room Tsodilo A and Entrance)
22 | - SciDataCon poster 150: [A wiki approach to collecting, curating and managing citizen science data](https://doi.org/10.5281/zenodo.2560018) (see SciDataCon session 211)
23 | - SciDataCon poster 208: [A wiki perspective on an Open Science Commons](https://www.scidatacon.org/IDW2018/sessions/252/poster/208/) (see SciDataCon session 252)
24 | - RDA breakout 3 — [Use cases for machine-actionable data management plans](https://www.rd-alliance.org/wg-dmp-common-standards-rda-12th-plenary-meeting)
25 | - Tuesday, 6 November at 9:30 - 11:00 in Room Tsodilo A
26 | - SciDataCon [Session 222: Health Databases across the African Continent: What do we have and what do we need for Sustainable Development?](https://www.scidatacon.org/IDW2018/sessions/222/) (merged from [Session 262: Open Data from Cell Biology of Infectious Pathogens, how far are we?](https://www.scidatacon.org/IDW2018/sessions/262/))
27 | - Tuesday, 6 November at **14:00–15:30** in Serondela 1 and 2
28 | - oral presentation 853: [Data sharing as a new component of addressing and preparing for disease outbreaks](https://www.scidatacon.org/IDW2018/sessions/262/paper/853/)
29 | - [slides](https://github.com/Daniel-Mietchen/events/blob/master/SciDataCon-2018-data-sharing.md)
30 | - SciDataCon [Session 229: Turning FAIR Data Into Reality: discussion, critique and implementation](https://www.scidatacon.org/IDW2018/sessions/229/)
31 | - Tuesday, 6 November at **14:00–15:30** in Okavango 1
32 | - panel contribution, "Action Plan for Research Infrastructures"
33 | - [slides](https://drive.google.com/file/d/1xpSt52_I-EspQl4x_ttI5XxaWqp_W6Vz/view?usp=sharing)
34 | - the final report has been published on 23 November 2018 and is available [here](http://doi.org/10.2777/1524)
35 | - SciDataCon [Session 196: Democratising Data Publishing: A Global Perspective](https://www.scidatacon.org/IDW2018/sessions/196/)
36 | - Tuesday, 6 November at **14:00–15:30** and **16:00 - 17:30** in Serondela 4
37 | - oral presentation 849: [Wikidata and Wikibase as global platforms for democratizing data publishing](https://www.scidatacon.org/IDW2018/sessions/196/paper/849/)
38 | - [slides](https://docs.google.com/presentation/d/1lqrgbA-Z0BQmkXDqDZtdR6EbHqDl0MM9POeyqmHG6KE/edit)
39 | - SciDataCon [Session 164: Scientific Data Challenges for Sustainable Development](https://www.scidatacon.org/IDW2018/sessions/164/)
40 | - Tuesday, 6 November at **16:00–17:30** in Tsodilo B3
41 | - oral presentation: [To what extent can machine-actionable data management plans help automate disaster-related workflows?](https://www.scidatacon.org/IDW2018/sessions/164/paper/926/)
42 | - [slides](SciDataCon-2018-maDMPs-for-disaster-data-management.md)
43 | - RDA breakout 5 — [Data Reuse Ethics : Specifying Roles and Responsibilities](https://www.rd-alliance.org/ig-ethics-and-social-aspects-data-rda-12th-plenary-meeting)
44 | - Wednesday, 7 November at 14:00 - 15:30 in Room Tsodilo B1
45 | - oral presentation: Making Ethical Review Processes more Machine Actionable
46 | - [slides](https://doi.org/10.5281/zenodo.2559997)
47 | - SciDataCon [Session 252: Delivering a Global Open Science Commons](https://www.scidatacon.org/IDW2018/sessions/252/)
48 | - Thursday, 8 November at **11:30 - 13:00** in Room Serondela 3
49 | - poster: [A wiki perspective on an Open Science Commons](https://www.scidatacon.org/IDW2018/sessions/252/poster/208/)
50 | - SciDataCon [Session 211: Citizen Science Data – from Collection to Curation to Management](https://www.scidatacon.org/IDW2018/sessions/211/)
51 | - Thursday, 8 November at **11:30 - 13:00** and 14:00–15:30 in Room Serondela 4
52 | - poster: [A wiki approach to collecting, curating and managing citizen science data](https://www.scidatacon.org/IDW2018/sessions/211/poster/150/)
53 | - [WDS ](https://www.icsu-wds.org/files/data-repositories-day-draft-agenda.pdf)
54 | - Friday, 9 November, University of Botswana
55 | - [EU FAIR Data Expert Group Report](https://drive.google.com/drive/folders/1gky1sajZnp0PwHQUpA24ylvcvfW-8o_7)
56 |
57 |
--------------------------------------------------------------------------------
/JROST-2020.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts information related to my participation in the [JROST 2020](https://web.archive.org/web/20201103004144/https://investinopen.org/community/jrost-2020-conference/) conference taking place online on 14-16 December 2020. My proposal below for a lightning talk was submitted on November 2 and accepted on November 20. It is now scheduled for Tuesday, December 15th at 12:00pm EST (17:00 UTC).
4 |
5 | The slides and a copy of the video are available on Zenodo via https://doi.org/10.5281/zenodo.4321982 . The video is also up [on YouTube](https://youtu.be/SZH7JGawsrY).
6 |
7 | # Call for session proposals
8 |
9 | The call is for three types of contributions:
10 | - lightning talks
11 | - breakout sessions
12 | - panel sessions
13 |
14 | The relative time afforded to the different session types has already been sketched out in the [preliminary agenda](web.archive.org/web/20201103004337/https://investinopen.org/jrost2020-agenda/).
15 |
16 | In the following, I will provide the key questions from the [submission form](https://docs.google.com/forms/d/e/1FAIpQLSe7iKPRgNEKGogVd9xdKNL8JzzwkYw6MuENA-rYU8AmrK2mgw/viewform?usp=sf_link), as well as my responses. The form is designed such that it allows a maximum of one per session type.
17 |
18 | ## Lightning talks
19 |
20 | *There will be two sessions of lightning talks (5 minutes each). These talks are great ways to share out your work, problems you’re wrestling with, and other ideas for collaboration.*
21 |
22 | ### Proposed talk title
23 |
24 | *(15 words)*
25 |
26 | * **The Wikimedia ecosystem as a key component of an open science landscape**
27 |
28 | ### What's your talk about?
29 |
30 | *(250 words)*
31 |
32 | As Wikipedia is approaching its 20th anniversary, this talk will provide a brief overview of the myriad of ways in which the ecosystem around it - including platforms like [Wikidata](https://wikidata.org/), initiatives like [WikiCite](https://meta.wikimedia.org/wiki/WikiCite) or tools like [Scholia](https://scholia.toolforge.org/) - is benefiting from open research, contributing to it, amplifying it or paving the way for it. On that basis, I will outline some opportunities to intensify these interactions to mutual benefit and to that of the research ecosystem and society at large, and I would like to encourage active contributors to the open research ecosystem to reflect on their interactions with the Wikimedia ecosystem and on how these could be improved.
33 |
34 |
35 | ## “Open in Practice” Breakout Discussions
36 |
37 | *Part of JROST is being able to have smaller conversations with your peers to learn with and from one another. We are looking for a few participants to lead smaller breakout discussions (~45 min each), and share tactics and experiences with the group. Key topics to think about include Funding and Sustainability, Technical Development and Interoperability, and Operational Support.*
38 | *(Example: Diversifying your funding streams, building integrations with partners, pivoting your project - and what you’ve learned, choosing an organizational home, etc.)*
39 |
40 | ### Proposed breakout title
41 |
42 | *(15 words)*
43 |
44 | * **Calling home: hello open world!**
45 |
46 | ### What would you like to share?
47 |
48 | *(250 words)*
49 |
50 | One way of building a strong community is by linking creators and maintainers of infrastructures, services and other resources with their users, and various mechanisms have evolved for that in a range of communities. What I want to explore in this session is standard mechanisms by which open tools, services and individual users could be encouraged (but not forced) to ping other members of the open research ecosystem, and potential recipients of such pings encouraged to listen in on at least a reasonable subset of those pings, provided that there is decent spam protection. For instance, many infrastructures or services are providing resources like tutorials that encourage users to familiarize themselves with the offerings. For new users, the first steps are often the most difficult, yet if the community around them were more aware of their efforts, help would be more readily available. Likewise, creators and maintainers as well as experienced users could perhaps learn from the use cases presented by new users, and consider adapting their offerings accordingly. So what I would like this session to explore is something like a mixture of a "Hello World" in programming with a log book as used on mountain summits and geocaches or indeed for version control in software repos or wiki pages, yet it should work across systems that meet some basic JROST standards. On that basis, further community-wide communication standards could be pondered, e.g. a button to thank someone for any of their contributions to the open ecosystem.
51 |
52 |
53 | ## Panel Discussions
54 |
55 | *We would love ideas for diverse panels (2-3 speakers + a moderator) to include in our program on Collaboration in Action (~45 min - 1 hour). Have ideas for panels you’d like to see? Want to lead one yourself? Please let us know.*
56 |
57 |
58 | ### Proposed panel title
59 |
60 | *(15 words)*
61 |
62 | * **["Open data matters most when the stakes are high"](https://web.archive.org/web/20150906201924/https://medium.com/@WhiteHouse/ten-years-after-katrina-new-orleans-recovery-and-what-data-had-to-do-with-it-3df0bb2467e9)**
63 |
64 | ### What's the panel about?
65 |
66 | *(250 words)*
67 |
68 | In response to disasters, humanity often responds by sharing more than usual. This sharing takes place in a myriad of ways, some of which have not evolved much in millennia, while others evolve at every occasion or are unique to a particular event. The point of this panel would be to explore mechanisms by which open infrastructures could be leveraged more quickly, more routinely and more comprehensively to reduce disaster risk, to prepare for disasters, to respond to disasters and to share lessons learned from them. The main motivation behind that is that some of the key features of open research — e.g. speed, verifiability and scalability — are especially important in disaster contexts, yet the overlap between the open research and the disaster mitigation communities is currently rather limited, so that potential often cannot be fully leveraged.
69 |
70 |
71 | ### Panelist suggestions--please list
72 |
73 | *(50 words)*
74 |
75 | I don't have this fully worked out but think that combining some people from the JROST community with representatives from organizations like the following would be a promising recipe:
76 |
77 | - [Humanitarian Data Exchange](https://humdata.org/)
78 | - [Humanitarian OpenStreetMap](https://www.hotosm.org/)
79 | - [Global Indigenous Data Alliance](https://www.gida-global.org/)
80 | - [PreventionWeb](https://www.preventionweb.net)
81 | - [Open Data for Resilience Initiative](https://opendri.org/)
82 |
83 | ### Do you want to moderate/lead this panel?
84 |
85 | * [ ] Yes (I or someone I identify will lead)
86 | * [ ] No (I'm hoping someone else might run with this!)
87 | * [X] Maybe (I could be convinced with the right support)
88 |
89 | # Candidate topics
90 |
91 | ## Proposed
92 |
93 | - Calling home
94 | - proposed as a breakout session
95 | - Disaster risk reduction
96 | - proposed as a panel
97 | - The Wikimedia ecosystem as a key component of an open science landscape
98 | - proposed as a lightning talk
99 |
100 | ## Topics I would also consider useful
101 |
102 | - Thank you button
103 | - mentioned in breakout session proposal
104 | - RIO Journal: Publishing all along the research cycle
105 | - The importance of documentation
106 | - Open learning
107 | - Doathon
108 |
109 |
110 | # See also
111 |
112 | * My [posters for International Data Week 2018](https://www.wikidata.org/wiki/User:Daniel_Mietchen/International_Data_Week_2018)
113 |
--------------------------------------------------------------------------------
/July-2020-Climate-Reality-Leadership-Corps-Global-Training.md:
--------------------------------------------------------------------------------
1 | The content of this file has been moved to [Summer-2020-Climate-Reality-Leadership-Corps-Global-Training.md](Summer-2020-Climate-Reality-Leadership-Corps-Global-Training.md).
2 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | CC0 1.0 Universal
2 |
3 | Statement of Purpose
4 |
5 | The laws of most jurisdictions throughout the world automatically confer
6 | exclusive Copyright and Related Rights (defined below) upon the creator and
7 | subsequent owner(s) (each and all, an "owner") of an original work of
8 | authorship and/or a database (each, a "Work").
9 |
10 | Certain owners wish to permanently relinquish those rights to a Work for the
11 | purpose of contributing to a commons of creative, cultural and scientific
12 | works ("Commons") that the public can reliably and without fear of later
13 | claims of infringement build upon, modify, incorporate in other works, reuse
14 | and redistribute as freely as possible in any form whatsoever and for any
15 | purposes, including without limitation commercial purposes. These owners may
16 | contribute to the Commons to promote the ideal of a free culture and the
17 | further production of creative, cultural and scientific works, or to gain
18 | reputation or greater distribution for their Work in part through the use and
19 | efforts of others.
20 |
21 | For these and/or other purposes and motivations, and without any expectation
22 | of additional consideration or compensation, the person associating CC0 with a
23 | Work (the "Affirmer"), to the extent that he or she is an owner of Copyright
24 | and Related Rights in the Work, voluntarily elects to apply CC0 to the Work
25 | and publicly distribute the Work under its terms, with knowledge of his or her
26 | Copyright and Related Rights in the Work and the meaning and intended legal
27 | effect of CC0 on those rights.
28 |
29 | 1. Copyright and Related Rights. A Work made available under CC0 may be
30 | protected by copyright and related or neighboring rights ("Copyright and
31 | Related Rights"). Copyright and Related Rights include, but are not limited
32 | to, the following:
33 |
34 | i. the right to reproduce, adapt, distribute, perform, display, communicate,
35 | and translate a Work;
36 |
37 | ii. moral rights retained by the original author(s) and/or performer(s);
38 |
39 | iii. publicity and privacy rights pertaining to a person's image or likeness
40 | depicted in a Work;
41 |
42 | iv. rights protecting against unfair competition in regards to a Work,
43 | subject to the limitations in paragraph 4(a), below;
44 |
45 | v. rights protecting the extraction, dissemination, use and reuse of data in
46 | a Work;
47 |
48 | vi. database rights (such as those arising under Directive 96/9/EC of the
49 | European Parliament and of the Council of 11 March 1996 on the legal
50 | protection of databases, and under any national implementation thereof,
51 | including any amended or successor version of such directive); and
52 |
53 | vii. other similar, equivalent or corresponding rights throughout the world
54 | based on applicable law or treaty, and any national implementations thereof.
55 |
56 | 2. Waiver. To the greatest extent permitted by, but not in contravention of,
57 | applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and
58 | unconditionally waives, abandons, and surrenders all of Affirmer's Copyright
59 | and Related Rights and associated claims and causes of action, whether now
60 | known or unknown (including existing as well as future claims and causes of
61 | action), in the Work (i) in all territories worldwide, (ii) for the maximum
62 | duration provided by applicable law or treaty (including future time
63 | extensions), (iii) in any current or future medium and for any number of
64 | copies, and (iv) for any purpose whatsoever, including without limitation
65 | commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes
66 | the Waiver for the benefit of each member of the public at large and to the
67 | detriment of Affirmer's heirs and successors, fully intending that such Waiver
68 | shall not be subject to revocation, rescission, cancellation, termination, or
69 | any other legal or equitable action to disrupt the quiet enjoyment of the Work
70 | by the public as contemplated by Affirmer's express Statement of Purpose.
71 |
72 | 3. Public License Fallback. Should any part of the Waiver for any reason be
73 | judged legally invalid or ineffective under applicable law, then the Waiver
74 | shall be preserved to the maximum extent permitted taking into account
75 | Affirmer's express Statement of Purpose. In addition, to the extent the Waiver
76 | is so judged Affirmer hereby grants to each affected person a royalty-free,
77 | non transferable, non sublicensable, non exclusive, irrevocable and
78 | unconditional license to exercise Affirmer's Copyright and Related Rights in
79 | the Work (i) in all territories worldwide, (ii) for the maximum duration
80 | provided by applicable law or treaty (including future time extensions), (iii)
81 | in any current or future medium and for any number of copies, and (iv) for any
82 | purpose whatsoever, including without limitation commercial, advertising or
83 | promotional purposes (the "License"). The License shall be deemed effective as
84 | of the date CC0 was applied by Affirmer to the Work. Should any part of the
85 | License for any reason be judged legally invalid or ineffective under
86 | applicable law, such partial invalidity or ineffectiveness shall not
87 | invalidate the remainder of the License, and in such case Affirmer hereby
88 | affirms that he or she will not (i) exercise any of his or her remaining
89 | Copyright and Related Rights in the Work or (ii) assert any associated claims
90 | and causes of action with respect to the Work, in either case contrary to
91 | Affirmer's express Statement of Purpose.
92 |
93 | 4. Limitations and Disclaimers.
94 |
95 | a. No trademark or patent rights held by Affirmer are waived, abandoned,
96 | surrendered, licensed or otherwise affected by this document.
97 |
98 | b. Affirmer offers the Work as-is and makes no representations or warranties
99 | of any kind concerning the Work, express, implied, statutory or otherwise,
100 | including without limitation warranties of title, merchantability, fitness
101 | for a particular purpose, non infringement, or the absence of latent or
102 | other defects, accuracy, or the present or absence of errors, whether or not
103 | discoverable, all to the greatest extent permissible under applicable law.
104 |
105 | c. Affirmer disclaims responsibility for clearing rights of other persons
106 | that may apply to the Work or any use thereof, including without limitation
107 | any person's Copyright and Related Rights in the Work. Further, Affirmer
108 | disclaims responsibility for obtaining any necessary consents, permissions
109 | or other rights required for any use of the Work.
110 |
111 | d. Affirmer understands and acknowledges that Creative Commons is not a
112 | party to this document and has no duty or obligation with respect to this
113 | CC0 or use of the Work.
114 |
115 | For more information, please see
116 |
117 |
118 |
--------------------------------------------------------------------------------
/MozOpenLeaders-2017.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts the free-text parts of my application for [MozOpenLeaders 2017](https://medium.com/read-write-participate/are-you-building-in-the-open-join-forces-with-mozilla-a791dbb5c74b) (the rest were basically multiple-choice questions or about personal information). It was [submitted](https://twitter.com/EvoMRI/status/817180729432018944) on January 6, 2017, to a January 20th deadline.
4 |
5 | On March 16, I was notfied that I had been shortlisted but did not make it into the final list.
6 |
7 | # Your Project
8 |
9 | > Tell us about your open project!
10 | >
11 | > The project doesn’t have to be technical! It can be curriculum (open educational resource), an open data project or report, an open source software project, or anything else that has:
12 | >
13 | > 1. a way for others to get involved
14 | > 2. a feature, release, or MVP (minimum viable product) to work on publicly with community members for the duration of the program
15 |
16 | # Project Name
17 |
18 | WikiProject Open Access
19 |
20 | # Project Description
21 |
22 | Leveraging the open-access literature in the context of Wikimedia projects
23 |
24 | # What problem(s) are you solving with this project?
25 |
26 | Integrating information from open-access resources into Wikimedia projects (especially Wikipedias, Wikisources, Wikimedia Commons and Wikidata), i.e. locations and languages that people (and, increasingly, machines) use to look for such information; making readers aware of the openness of such information; curate bibliographic metadata of open-access publications.
27 |
28 | # What feature, release, or product can you work on during the program?
29 | > March - June 2017
30 |
31 | A Wikidata-based open bibliography of open-access articles cited on Wikimedia projects as a basis for new mechanisms for knowledge discovery, scientific collaboration and research assessment (demos at https://tools.wmflabs.org/scholia/venue/Q564954 or https://tools.wmflabs.org/scholia/topic/Q202864 or https://tools.wmflabs.org/scholia/publisher/Q463494 ).
32 |
33 | # How can others join you on this project?
34 |
35 | Multiple ways, e.g. https://github.com/wpoa or https://commons.wikimedia.org/wiki/User:Open_Access_Media_Importer_Bot or https://www.wikidata.org/wiki/Wikidata:WikiProject_Source_MetaData or https://meta.wikimedia.org/wiki/WikiCite .
36 |
37 | # Why do you want to work open?
38 |
39 | Every day makes me aware of the limitations of my knowledge, skills and resources. When these limitations stand in the way of moving forward, working openly makes it much easier to bring in others, including people who I neither know personally nor via my network.
40 |
41 | # What challenges have you faced working open?
42 | > OR what has kept you from working open
43 |
44 | Lots, e.g. non-open or unclear licensing of the things I'd like to work with; non-open formats; incomplete or inaccurate metadata; inconsistent usage of standards; conservative colleagues and institutional inertia.
45 |
46 | # Is there anything else you'd like us to know?
47 |
48 | I am interested in ways in which technology could be leveraged in the context of open knowledge projects. While an experienced contributor to open knowledge projects (e.g. https://meta.wikimedia.org/wiki/User:Daniel_Mietchen/European_Commission_Open_Science_Policy_Platform or http://sparcopen.org/our-work/innovator/ or https://github.com/Daniel-Mietchen/open-science-prize ) and a mentor on matters of open science (e.g. https://meta.wikimedia.org/wiki/Wikimedia_Deutschland/Open_Science_Fellows_Program ), I have rather limited coding skills (cf. https://github.com/Daniel-Mietchen/learning2code ) and would like to tap into the technical expertise at Mozilla to guide my learning process here in a way that helps advance the open projects that I am engaging with.
49 |
50 | Information on Wikimedia and Open Access is summarized in https://blog.wikimedia.org/2014/01/15/wikimedia-and-open-access/ , with monthly updates in https://outreach.wikimedia.org/wiki/Category:This_Month_in_GLAM_Open_Access_reports .
51 |
52 | I participated in past MozSprints. In 2016, I had suggested a project (cf. https://github.com/mozillascience/global-sprint-2016/issues/53 ) but did not find others who wanted to join in, so I contributed to a related project (cf. https://github.com/mozillascience/global-sprint-2016/issues/36 ).
53 |
54 | My application is also available via https://github.com/Daniel-Mietchen/talks/blob/master/MozOpenLeaders-2017.md .
55 |
--------------------------------------------------------------------------------
/New-Arctic-Bridging.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This is an abstract for a poster presented as part of the conference "[Bridging Science, Art, and Community in the New Arctic](https://github.com/Daniel-Mietchen/events/issues/593)" on 23-25 September 2019 in Charlottesville. It was submitted on 29 August 2019. The poster was presented on 24 September 2019.
4 |
5 | # Poster title
6 |
7 | Bridging Science, Art, and Community in the New Arctic through Wikimedia projects
8 |
9 | # Poster abstract
10 |
11 | Wikipedia and its sister Wikimedia projects like Wikidata, Wikisource and Wikimedia Commons form a popular and multilingual ecosystem of websites and communities dedicated to sharing the world’s knowledge, including about science, art, the New Arctic and its communities. This poster will highlight some Wikimedia content and initiatives relevant to the New Arctic that span across the natural and social sciences, humanities and arts. The poster will be accompanied by a demo that illustrates how conference participants and their activities could leverage these resources or contribute to enriching them.
12 |
13 |
14 | # Poster author
15 |
16 | Daniel Mietchen
17 |
18 | # Poster
19 |
20 | The poster can be found at https://doi.org/10.5281/zenodo.3459315 . It is embedded below based on a [copy of it on Wikimedia Commons](https://commons.wikimedia.org/wiki/File:Bridging_Science_Art_and_Community_in_the_New_Arctic_through_Wikimedia_projects.pdf).
21 |
22 | [](https://commons.wikimedia.org/wiki/File:Bridging_Science_Art_and_Community_in_the_New_Arctic_through_Wikimedia_projects.pdf)
23 |
--------------------------------------------------------------------------------
/OpenCon-2016.md:
--------------------------------------------------------------------------------
1 | #About
2 | This file hosts the free-text parts of my application for [OpenCon 2016](http://www.opencon2016.org/) (the rest were basically multiple-choice questions or about personal information).
3 |
4 | # Describe yourself in 1-2 sentences.
5 |
6 | > Maximum 280 characters (~40 words). It’s up to you what information to provide. Many people write something similar to their Twitter or Facebook bio.
7 |
8 | An evolutionary biophysicist working on integrating research workflows with the Web, all along the research cycle.
9 |
10 | Often thinks about how the research ecosystem would look like if it had a public version history and open licensing by default, and what we have to do to get there.
11 |
12 | # Why are you interested in Open Access, Open Education and/or Open Data and how does it relate to your work? If you are already involved in these issues, tell us how.
13 |
14 | > Maximum 1600 characters (~250 words). There are many reasons why Open is important. This question is asking specifically why Open is important to *you*. Please use your own words to describe your perspective and experience.
15 |
16 | I got involved with Open because it addressed problems I had: lack of read access to the research literature, lack of permissions to tinker with software or to analyze data whose existence was advertised in those parts of the literature that I could read.
17 |
18 | Once I dug deeper into the matter, I discovered open licenses that provide more than read access: the rights to reuse, revise, remix and redistribute, which are the basis for doing and building new things and thus very close to my mindset as a researcher and life-long learner. I feel empowered by such additional degrees of freedom and am now exercising them on a daily basis, e.g. by using FLOSS libraries when developing software, by building workflows around open data and by repurposing open research materials in educational contexts.
19 |
20 | I also enjoy pondering about the generativity that is enabled by such freedoms. Having explored a range of different life forms as part of my research, I am quite conscious that their diversity is the result of a delicate interplay between their degrees of freedom and the restrictions placed upon them. When these restrictions are different - think deep sea vs. desert, day vs. night or fog vs. mosquito spraying - this is reflected in the observable biodiversity.
21 |
22 | Translating this back to the research ecosystem, its freedoms and restrictions around sharing and doing new things with its basic elements - knowledge, ideas and methods - determine the diversity of potential research outcomes and thus the way in which research can help society move forward or appreciate how that worked in the past.
23 |
24 |
25 | # The biggest goal of OpenCon is to catalyze action. What ideas do you have for advancing Open Access, Open Education and/or Open Data, and how would you use your experience at OpenCon to have an impact?
26 |
27 | > Maximum 1600 characters (~250 words).
28 |
29 | Open knowledge writ large has been the focus of my volunteer activities for more than a decade now.
30 |
31 | For example, I am an active contributor to Wikipedia and its sister projects. Apart from the usual editing there, I am leading a project to automatically upload multimedia files from open-access articles into Wikimedia Commons. This project is currently being expanded to full texts, with Wikisource doubling as an open-access repository that enhances the verifiability of statements made in Wikipedia articles, and Wikidata emerging as an open bibliography of the cited scholarly literature.
32 |
33 | I contributed to the Wikimedia Foundation's Open Access policy, co-founded an open-science journal (Research Ideas and Outcomes) and am engaged around digitally preserving our natural and cultural heritage. I am documenting many of my activities in the open, e.g. my talks (cf. https://git.io/vKZOa ) as well as my attempts to learn Python (cf. https://git.io/vKZOw ) or this very OpenCon application (cf. https://git.io/vKZOr ).
34 |
35 | The personal interactions I have had at OpenCon, its satellites and similar events have contributed much to these activities: they inspired me, motivated me to go the next step, or even to retry. I hope for this to continue this year, and that I can give back a bit too.
36 |
37 | Open knowledge has become an integral part of my professional activities as well, most notably in my current role at the NIH, which is focused on policy and technical aspects of biomedical data science (notes at https://git.io/vKZOK ) and included contributing to the design of the Open Science Prize.
38 |
39 | # For [Open Access Week, Open Education Week, Open Data Day], please explain how you participated and/or how you plan to participate.
40 |
41 | > Maximum 600 characters (~100 words).
42 |
43 | I participated in the “synchro-blogging” on the occasion of Open Access Day 2008 (cf.
44 | http://legacy.earlham.edu/~peters/fos/2008/10/roundup-of-blog-posts-on-oa-day-part-3.html ) and contributed to every Open Access Week since, e.g. by blogging (cf. http://blogs.plos.org/yoursay/2012/10/23/reusing-revising-remixing-and-redistributing-research/ ), by starting https://en.wikipedia.org/wiki/Open_Access_Week or by participating in Wikimedia editathons or hackathons on the topic. I contributed similarly - though less frequently - to the other two events (as well as similar ones like Copyright week).
45 |
46 | # Comments Box (Optional)
47 |
48 | > Use this box for any additional information you would like to share about yourself, projects you work on, or other information that could impact your attendance or participation at OpenCon 2016, if invited. Maximum 900 characters, ~150 words.
49 |
50 | I think I have said enough in the other fields, but if you'd like to dig deeper, then https://meta.wikimedia.org/wiki/User:Daniel_Mietchen/European_Commission_Open_Science_Policy_Platform or
51 | https://twitter.com/search?f=tweets&vertical=default&q=%28openaccess%20OR%20openscience%20OR%20opendata%20OR%20oer%20OR%20opencon%29%20AND%20evomri would be good starting points.
52 |
--------------------------------------------------------------------------------
/PIDapalooza-2019.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a contribution to [PIDapalooza 2019](https://pidapalooza.org). It was submitted on 21 September 2018 and accepted on 5 November 2018. In the end, I could not attend, but remain interested in comments and exchanges related to making ethics processes more FAIR, and on the role that persistent identifiers can play in such contexts.
4 |
5 | # Title
6 |
7 | Persisting on making ethics processes Findable, Accessible, Interoperable and Reusable
8 |
9 | # Abstract
10 |
11 | Many research projects require ethical review, and publications resulting from approved ones usually refer to the approval in some fashion, which may or may not involve persistent identifiers. If present, such identifiers are associated with information about certain aspects of the ethics process, which are usually neither public nor FAIR but often could be either or both.
12 |
13 | Here, we will look at examples taken from a range of ethics processes from various disciplines and highlight use cases for identifiers in such contexts, as well as the potential for automation, especially in terms of generating, curating and following up on ethics statements in scholarly communications like grant proposals, data management plans or publications. This submission builds on a [PIDapalooza 2016](PIDapalooza-2016.md) talk and will be given from https://github.com/Daniel-Mietchen/events/blob/master/PIDapalooza-2019.md .
14 |
15 | # Session philosophy
16 |
17 | *How would you run the session to support the spirit of PIDapalooza as a laid-back, welcoming, energetic and exciting, sociable and serious gathering? (Optional)*
18 |
19 | - Examples will be drawn from across disciplines, with a certain preference to phrasings that can be interpreted in a funny way.
20 |
21 | # Your bio
22 |
23 | * https://en.wikipedia.org/wiki/User:Daniel_Mietchen/Biographical_sketch
24 |
25 | # See also
26 |
27 | * [Making Ethical Review Processes more Machine Actionable](https://docs.google.com/presentation/d/1weJvgcMYgJ1vfhyJ6SE5hHDwrSZ7dk_DkfLIKO1f5kU/edit) — talk at the [12th RDA Plenary on 7 November 2018 in Gaborone](https://www.rd-alliance.org/ig-ethics-and-social-aspects-data-rda-12th-plenary-meeting)
28 | * [Deon](http://deon.drivendata.org/) — data science ethics checklist
29 | * [Federal Policy for the Protection of Human Subjects](https://www.federalregister.gov/documents/2017/01/19/2017-01058/federal-policy-for-the-protection-of-human-subjects)
30 | * [Dynamic jurisdiction mapping](https://cleanapp.io/cleanappmap/) — see also [this discussion](https://twitter.com/EvoMRI/status/1064055126795657216)
31 | * [PIDs for policy elements](https://github.com/Daniel-Mietchen/events/blob/master/PIDapalooza-2018.md) — a presentation given at [PIDapalooza 2018](https://doi.org/10.5438/11.0002)
32 |
--------------------------------------------------------------------------------
/PIDapalooza-2021.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts materials related to my contribution to [PIDapalooza 2021](http://web.archive.org/web/20201106021021/https://www.pidapalooza.org/upcoming-festival), taking place online for 24h starting at 2.30pm UTC on January 27, 2021. The session proposal was [submitted](https://twitter.com/EvoMRI/status/1324820104060805128) on 6 November 2020.
4 |
5 | # Questions from the PIDapalooza 2021 Proposal Form
6 | * ```*``` Required
7 |
8 | ## Your name(s) *
9 |
10 | Daniel Mietchen
11 |
12 | ## How does your session tie in with the overall theme of PIDs and the open research infrastructure? *
13 |
14 | Words and phrases convey meaning and as such are key components of human communication or research about it. [Wikidata](https://wikidata.org/) is an open knowledge graph built around persistent and machine-actionable identifiers for millions of concepts that are organized in a nearly language-independent manner and linked to the words and phrases expressing the corresponding meanings in potentially any human language. It is collaboratively curated by a global multilingual community of over 20 thousand monthly contributors as well as a range of automated tools.
15 |
16 |
17 | ## Which theme inspired your session? *
18 |
19 | PID Communities International
20 |
21 |
22 | ## Session title *
23 |
24 | Wikidata: Persistent identifiers as the basis for multilingual and human-machine collaboration
25 |
26 |
27 | ## Session description (please note, this will be used in the program so make it good!) *
28 |
29 | Bring some words or phrases that you find interesting, in a language that you can type into an etherpad or speak into your computer's microphone. Feel free to [sing them](https://commons.wikimedia.org/wiki/File:Citation_sound_effect_-_the_English_word_citation_sung_by_a_soprano_singer.wav) too! Then let's explore them together and see how they are related to meanings or to words and phrases in other languages, and at what points in that network of interactions the introduction of persistent identifiers would be beneficial.
30 |
31 | The session's etherpad sits at [https://etherpad.wikimedia.org/p/zenodo.4253308](https://etherpad.wikimedia.org/p/zenodo.4253308) . Further materials related to the session shall be available via https://10.5281/zenodo.4253308 when the session starts.
32 |
33 |
34 | ## Which language(s) would your session be in? *
35 |
36 | The main part would be in English, with examples drawn from about a dozen other languages, including optionally some spoken or written by people in attendance, not necessarily by me.
37 |
38 |
39 | ## How would you run the session to support the spirit of PIDapalooza as a laid-back, welcoming, energetic and exciting, sociable and serious gathering? *
40 |
41 | The session would be seeded with a demo by me of how words and phrases, word forms and meanings can be encoded in Wikidata and to what extent this has already been done. We will then use some audience-suggested examples to explore the Wikidata knowledge graph, the interactions between nodes within the graph and with external resources like monolingual databases, as well as the role of identifiers in all of that. Towards the end, there will also be a demo of recording individual words and phrases and of integrating such recordings into the knowledge graph.
42 |
43 |
44 | ## We encourage audience participation. This can be done in many ways: Q&A, polling the audience, etc. Please describe which tactics you would use to engage the audience.*
45 |
46 | Session participants would be encouraged to contribute - via the [etherpad](https://etherpad.wikimedia.org/p/zenodo.4253308) - words or phrases in any language they master, or concepts or identifiers for any of these.
47 |
48 |
49 | ## Speaker bio(s) (this will also appear in the program) *
50 |
51 | By the time I was about 9, the persistent identifiers I had seen on buses, cars, trams or trains during the last few hours or sometimes days would often get stuck in my head and entertain my thoughts about where the vehicles or their passengers were from, where they were heading and whether there was an interesting pattern in or a meaning behind those character sequences.
52 |
53 | At about the same time, I began to learn my first foreign language at school. I did not know anyone who did not speak my mother tongue, so my motivation to learn that new one was limited. One day, the teacher gave me a book in that language and told me I should read it and give a talk about it the following week. I had never read a book in another language, and it took me about two hours to work my way through the wall of text on the first page, so I had no idea whether or how I would make it through that book in a week's time.
54 |
55 |
56 | ## Which of the following time slots can you be available in (please check all that apply)? *
57 | * [x] January 27, 2021 15:00 - 18:00 UTC
58 | * [x] January 27, 2021 20:00 UTC - January 28, 00:00 UTC
59 | * [x] January 28, 2021 01:00 - 02:00 UTC
60 | * [x] January 28, 2021 04:00 - 07:00 UTC
61 | * [x] January 28, 2021 08:00 - 11:00 UTC
62 | * [x] January 28, 2021 12:00 - 15:00 UTC
63 |
64 |
65 | ## Your email address *
66 |
67 | * dm7gn /at/ virginia.edu
68 |
69 |
70 | ## Your Twitter handle
71 |
72 | * https://twitter.com/EvoMRI
73 |
74 |
75 | ## Please sum up your session in a tweet (280 characters or less)
76 |
77 | * https://twitter.com/EvoMRI/status/1324820104060805128
78 |
79 |
80 | ## Would you like to suggest a song for the PIDapalooza 2021 playlist?
81 |
82 | * https://soundcloud.com/geraldo-moratta/altai-kai-turkic-throat-singing
83 | * https://soundcloud.com/cyrille-totozafy/08-uutai-passing
84 |
85 |
86 | # See also
87 |
88 | * [PIDapalooza-2019.md](https://github.com/Daniel-Mietchen/events/blob/master/PIDapalooza-2019.md)
89 | * [PIDapalooza-2018.md](https://github.com/Daniel-Mietchen/events/blob/master/PIDapalooza-2018.md)
90 | * [PIDapalooza-2016.md](https://github.com/Daniel-Mietchen/events/blob/master/PIDapalooza-2016.md)
91 | * [Wikidata:Lexicographical_data](https://www.wikidata.org/wiki/Wikidata:Lexicographical_data)
92 | * [Ordia](https://ordia.toolforge.org/)
93 | * [Lexeme forms](https://tools.wmflabs.org/lexeme-forms/)
94 | * [MakesSense](https://machtsinn.toolforge.org/)
95 | * [LinguaLibre](https://lingualibre.org/)
96 |
--------------------------------------------------------------------------------
/PIDapalooza.md:
--------------------------------------------------------------------------------
1 | [PIDapalooza](https://pidapalooza.org/) is a conference focused on [persistent identifiers](https://en.wikipedia.org/wiki/Persistent_identifier), and my contributions to individual shindings can be found via
2 |
3 | - [PIDapalooza-2019.md](PIDapalooza-2019.md) (Persisting on making the ethics process FAIR)
4 | - [PIDapalooza-2018.md](PIDapalooza-2018.md) (PIDs for policy elements)
5 | - [PIDapalooza-2016.md](PIDapalooza-2016.md) (Making ethics data FAIR)
6 | - [PIDapalooza-2021.md](PIDapalooza-2021.md) (Wikidata: Persistent identifiers as the basis for multilingual and human-machine collaboration)
7 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # About
2 | Many conferences and other events require submissions of proposals, but very few of these are being made public in a timely fashion or at all. Plus, many of these submission systems have technical issues or do not provide submitters with a copy of their submission. I have thus started this repo to keep track of my submissions to such closed systems, and I will also use it for hosting the materials for some invited talks. Many more of my talks are available elsewhere, as detailed [here](https://en.wikipedia.org/wiki/User:Daniel_Mietchen/Talks). Some of them have been [recorded](recordings.md).
3 |
--------------------------------------------------------------------------------
/SORTEE-2021.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts materials related to my potential participation in the [Society for Open Reliable Transparent Ecology and Evolutionary biology (SORTEE) 2021](http://web.archive.org/web/20210601224641/https://www.sortee.org/events/) online conference on 12-14 July 2021. My session proposal "Why SORTEE session proposals should default to being open upon submission" was submitted on June 1 and approved on June 10 as Unconference session 11, to take place on 13th July 2021, 16:00-17:00 UTC.
4 |
5 | * Topic: The closed nature of submissions to events organized under an open flag
6 | * Abstract: The discussion should sharpen the participants' thoughts on the relative merits of conference submission processes defaulting to open or closed. To this end, I will briefly introduce some open examples and then stimulate discussion of the advantages and disadvantages of such open approaches, particularly in the context of SORTEE.
7 |
8 | # Etherpad
9 |
10 | * https://etherpad.wikimedia.org/p/SORTEE-2021-U11-open-proposals
11 |
12 | # Backchannels
13 |
14 | * SORTEE 2021 Slack: #conf2021-u11-open-proposals
15 | * Twitter: [SORTEE2021 OR sortecoevo](https://twitter.com/search?q=SORTEE2021%20OR%20sortecoevo&src=typed_query&f=live)
16 |
17 |
18 | # Archive
19 | *Content in this section has been used at some point in the past but is not actively maintained any more.*
20 |
21 | ## Call for proposals
22 |
23 | The call for proposals lists four potential submission types, all of which are potential fits for me, so I am jotting down some notes on them here to explore whether to submit something, and what.
24 |
25 | ## Unconferences
26 |
27 | - Valid reasons not to share data
28 | - Variants:
29 | - What are typical arguments for not being open, and how to respond to them?
30 | - Arguments against open science, and how to respond to them
31 | - When was research that was published last week actually performed?
32 | - Why SORTEE session proposals should default to being open upon submission
33 | - submitted
34 |
35 | ## Hackathons
36 |
37 | - Teaching machines to search for evidence for or against a given hypothesis
38 | - The ecological footprint of computational replication attempts
39 |
40 | ## Workshops
41 |
42 | - Visualizing the research ecosystem of ecosystem research via Wikidata
43 | - variants:
44 | - Building open scholarly profiles via Scholia
45 | - Scholia: Building scholarly profiles via open-source visualizations of open data
46 |
47 | ## Short Presentations
48 |
49 | - Insights from publishing all along the research cycle
50 | - Ask Open Science: an open Q & A site for questions all around open science
51 |
52 |
53 | # See also
54 |
55 | * My contributions to [10th International Conference on Ecological Informatics (ICEI) 2018](https://github.com/Daniel-Mietchen/events/blob/master/ICEI2018.md):
56 | - Wikimedia projects as citizen science platforms
57 | - Community-curated Linked Open Data about the Sustainable Development Goals, their targets and indicators
58 | - Visualizing the research ecosystem of ecosystem research via Wikidata
59 | * [Notes on SORTEE advocacy](https://docs.google.com/document/d/1GUj02L83TJ6fFjA7NrSRaNYGoXoJGBiXk0vtwJua1Ck/edit#)
60 | * [Notes on Open Science & Science Communication session](https://app.mural.co/t/scicommnceas4064/m/scicommnceas4064/1625095929635/41edd90cdcc564ff97b509b3cc7f612d08f644ec?sender=a474ac0d-d235-49e0-a860-e1d99f4fc4e1)
61 |
--------------------------------------------------------------------------------
/Sage-Assembly-2017.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | On April 20-22, the [2017 Sage Assembly](http://sageassembly.org/?page_id=13) (hashtag: [#SageAssembly](https://twitter.com/search?vertical=default&q=sageassembly%20OR%20(sage%20AND%20(assembly%20OR%20congress%20PR%20bio))%20OR%20sagebio)) is taking place in Seattle. In preparation for the event, the organizers have asked for a "Link to your work that best fits the Assembly", which will be linked from the [list of participants](http://sageassembly.org/?page_id=48). I think the best way to address that is to set up a dedicated document here that I can update before, during and possibly after the Assembly, whose theme this year is "Mapping Open Research Ecosystems".
4 |
5 | From the [homepage](http://sageassembly.wpengine.com/):
6 | > In 2017, we will bring the Assembly to Seattle, Sage Bionetworks’ home base, and back to the themes closest to us: open innovation in science, and the acceleration of health research through open systems, incentives and standards. Together, we will explore how open ecosystems form, where they work, and what boundaries are necessary to operate them successfully. We will also address the consequences, intended or otherwise, of living in more open ways. As always you can expect the unexpected at a Sage Assembly – with a focus on participant interaction, engaging panels, lots of interaction, and an afternoon outside the venue where we will work in teams on projects that explore our themes in non-traditional ways.
7 |
8 | # Some of my activities in this space
9 |
10 | * At work
11 | - helping to improve [data sharing in public health emergencies](https://doi.org/10.2471/BLT.17.192096)
12 | - working on [making data mangement plans machine actionable, versioned and public](https://doi.org/10.3897/rio.3.e13086)
13 | - helped shape the [Open Science Prize](http://openscienceprize.org/)
14 | - organising events like [this open research do-a-thon](https://github.com/sparcopen/Open-Research-doathon) to help bring people together around data-centric research workflows
15 | - helping to explore [technical aspects of preprint services in the life sciences](https://doi.org/10.3897/rio.3.e11825)
16 | - More complete documentation [here](https://github.com/Daniel-Mietchen/datascience/)
17 | * Elsewhere
18 | - helping to [collect citations for the sum of human knowledge](https://meta.wikimedia.org/wiki/WikiCite_2017)
19 | - contributing to [data science policy in the European Union](http://ec.europa.eu/transparency/regexpert/index.cfm?do=groupDetail.groupDetail&groupID=3464)
20 | - helping to [organize events around modernizing scholarly communication](https://www.force11.org/group/force2017-organizing-committee/program-committee)
21 | - editing an open-science [journal](http://riojournal.com/browse_articles) that aims to make entire research processes visible, not just the results
22 | - running a [bot](https://commons.wikimedia.org/wiki/User:Open_Access_Media_Importer_Bot) that feeds openly licensed multimedia from PubMed Central into Wikimedia Commons
23 | - editing the [Topic Pages](http://collections.plos.org/topic-pages) collection at PLOS Computational Biology
24 |
25 | # 3-min talks
26 |
27 | The organizers invited me to contribute to "a series of talks in a rapid-learning format with each speaker providing a three minute talk on their work and experience as they relate to the themes of the Assembly".
28 |
29 | I [decided](https://twitter.com/EvoMRI/status/855207956899430400) to invite the audience to think about a long-term vision for Open Research Ecosystems, perhaps on the 2030 timescale, as per several ongoing strategy processes (e.g. [National Institute of Dental and Craniofacial Research (NIDCR)](https://nidcr2030.ideascale.com/), [Wikimedia](https://2030.wikimedia.org/), [Gathering for Open Source Hardware (GOSH)](https://openscience.ub.uni-bielefeld.de/1025/how-to-make-open-science-hardware-ubiquitous-by-2025)) and [What we know about the future](https://meta.wikimedia.org/wiki/Template:Strategy/Wikimedia_movement/2017/navbox).
30 |
31 | To get things started, I'll be pointing out some things that I am missing in current ways of "Mapping Open Research Ecosystems", for which the following topics are good candidates:
32 | - **Map**: How to map any research ecosystem?
33 | - [map of science based on paper clickstream data from a decade ago](https://doi.org/10.1371/journal.pone.0004803.g005)
34 | - neither data nor tools are open
35 | - not updatable
36 | - no zoom
37 | - [map of topics co-occurring with "Zika virus" in the literature](https://query.wikidata.org/#%23defaultView%3AGraph%0A%23defaultView%3ATable%0Aselect%20distinct%20%3Ftopic1%20%3Ftopic1Label%20%3Ftopic2%20%3Ftopic2Label%20where%20{%0A%20%20{%20%3Fwork%20wdt%3AP921%2Fwdt%3AP31*%2Fwdt%3AP279*%20wd%3AQ202864%20.%20}%0A%20%20union%20{%20%3Fwork%20wdt%3AP921%2Fwdt%3AP361%2B%20wd%3AQ202864%20.%20}%0A%20%20union%20{%20%3Fwork%20wdt%3AP921%2Fwdt%3AP1269%2B%20wd%3AQ202864%20.%20}%0A%20%20%3Fwork%20wdt%3AP921%20%3Ftopic1%2C%20%3Ftopic2%20.%20%0A%20%20filter%20(wd%3AQ202864%20!%3D%20%3Ftopic1%20%26%26%20wd%3AQ202864%20!%3D%20%3Ftopic2%20%26%26%20%3Ftopic1%20!%3D%20%3Ftopic2)%0A%20%20SERVICE%20wikibase%3Alabel%20{%0A%20%20%20%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%2Cfr%2Cde%2Cru%2Ces%2Czh%2Cjp%22.%0A%20%20}%0A}%0A%0A)
38 | - from [Scholia profile for topic "Zika virus"](https://tools.wmflabs.org/scholia/topic/Q202864)
39 | - open data, open tools, open API, updatable
40 | - "zooming" possible by changing the topic
41 | - still mainly limited to "papers", since citation metadata to, from and between other research objects is scarce at best
42 | - **How to map research that is being *performed now* or *planned for the near future*?**
43 | - some inspiration: real-time [visualization](http://wikistream.wmflabs.org/#namespace=article&robot=true&user=true&wiki=all) and [sonification](http://listen.hatnote.com/#en,fa,ar,sa,es,de,ru,jp,zh,ko) of Wikimedia edits
44 | - What about [doing this for research](https://github.com/sparcopen/open-research-doathon/issues/34)?
45 | - [As it happens](https://www.youtube.com/watch?v=LwW1-X3glak)?
46 | - [All along the research cycle](https://doi.org/10.3897/rio.1.e7547)?
47 | - with appropriate filtering, something like this could serve as the basis for researchers, funders, public and others to engage with a given research topic
48 | - particularly relevant in the case of public health emergencies, which also provide a context where "open by default" is actually within reach
49 | - works best if data and metadata are [FAIR](https://doi.org/10.1038/sdata.2016.18) by default
50 | - publicly versioned [machine actionable data (or project) management plans](https://doi.org/10.3897/rio.3.e13086) as a way to connect research projects (past, ongoing and future) with relevant individuals, communities, institutions and their respective resources and workflows
51 | - **Queriability**: How can data from different parts of the research ecosystems best be integrated in a way that allows to address issues that cut across research fields?
52 | - Wikidata as a hub for structured open knowledge across domains, with biomedicine being one of the pilot areas
53 | - **Ethics**: making ethics data FAIR
54 | - [talk on the topic](https://github.com/Daniel-Mietchen/events/blob/master/PIDapalooza.md)
55 | - [further notes](https://github.com/Daniel-Mietchen/datascience/blob/master/ethics.md)
56 | - **Sustainability**: How to better align the priorities within the research ecosystems (open or not) with the needs of humanity as a whole?
57 | - **Lean administration**: How can openness be used to reduce bureaucracy?
58 | - e.g. [self-organized fund allocation](https://doi.org/10.1007/s11192-016-2110-3)
59 | - **Effective policies**: How can different policies and infrastructures be made better aware of each other?
60 |
61 | # Demo
62 |
63 | The organizers also invited suggestions for demos of up to 15 min. I had suggested to demo Wikimedia-based open research workflows, i.e. how Wikimedia platforms can be used to cover a broad range of digital research workflows in a wide array of disciplines (see [here](https://en.m.wikipedia.org/wiki/User:Daniel_Mietchen/Talks/UKSG_2015) for a talk covering part of this topic), but this suggestion was not taken.
64 |
65 | # ORCID
66 |
67 | I find it interesting that none of the participants has provided their ORCID as the "Link to your work that best fits the Assembly". In any case, mine is [0000-0001-9488-1870](http://orcid.org/0000-0001-9488-1870).
68 |
69 | # Notes on the individual sessions
70 |
71 | - Editing a file like this (i.e. larger than my screen) is a bit tedious, so my notes on the individual sessions are posted in the [ticket](https://github.com/Daniel-Mietchen/events/issues/8) I opened for this event.
72 |
73 | # Contact
74 |
75 | [@EvoMRI](https://twitter.com/EvoMRI)
76 |
--------------------------------------------------------------------------------
/SciDataCon-2018-Wikidata.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a submission to [SciDataCon 2018](https://www.scidatacon.org/IDW2018/).
4 |
5 | # Title
6 |
7 | Workshop: Integrating Wikidata with research and curation workflows
8 |
9 | # Session description
10 |
11 | Wikidata is a platform that brings together a global community of people from all walks of life - as well as tools of various degrees of automation - to engage in the collaborative collection and curation of structured data that is in the public domain. It is also multilingual, and has been described as the Rosetta stone of the linked open data age.
12 |
13 | Launched in 2012, it has since become a hub for structured data across many domains of knowledge, including research fields from cultural heritage to biomedicine. Since its beginnings, the potential of integrating Wikidata with research and curation workflows has been explored through a number of activities, e.g. initiatives to collect on Wikidata information about paintings, pathways, politicians, proteins or publications as well as through workshops or grant proposals.
14 |
15 | Data in Wikidata is Findable, Accessible, Interoperable and Reusable (FAIR) by design, which opens up new perspectives in terms of the discoverability of research data, its incorporation into applications and education, and the potential to harness data curation efforts taking place in distant corners of the research data ecosystem for collaboration within and across fields.
16 |
17 | This two-part workshop aims to introduce participants to Wikidata and to highlight how it can and does contribute to workflows in or near the participants' fields of research. It builds on similar workshops given in the past to various audiences — from librarians to economists to scientists and museum professionals — on how research workflows can be integrated with the workflows of Wikidata and its sister Wikimedia projects.
18 |
19 | The workshop is arranged in two main parts:
20 | - the first part is introductory and will provide the basics about Wikidata and the research and curation-related workflows around it;
21 | - the second part is more hands-on, focusing on integrating some exemplary discovery and curation workflows with Wikidata, which will be drawn from SciDataCon abstracts and experiences shared by course participants.
22 |
23 | Throughout the workshop, active participation by attendees will be encouraged through a discursive presentation style, quizzes and group work. At the end of the session, all participants are expected to have added some specific bits of knowledge to Wikidata, and to have reviewed contributions made by others.
24 |
25 | This submission addresses all four of the [high-level themes of SciDataCon 2018](https://www.scidatacon.org/conference/IDW2018/conference_themes_and_scope/):
26 | - The digital frontiers of global science;
27 | - a global and inclusive data revolution;
28 | - applications, progress and challenges of data intensive research;
29 | - data infrastructure and enabling practices for international and collaborative research.
30 |
31 | A version of this abstract can be found at https://github.com/Daniel-Mietchen/events/blob/master/SciDataCon-2018-Wikidata.md .
32 |
--------------------------------------------------------------------------------
/SciDataCon-2018-maDMPs-for-disaster-data-management.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a contribution in form of an oral presentation to SciDataCon 2018 [session 164: Scientific Data Challenges for Sustainable Development](https://www.scidatacon.org/IDW2018/sessions/164/) taking place on Tuesday, 6 November at 16:00–17:30 in room Tsodilo B3.
4 |
5 | See [here](International-Data-Week-2018.md) for my schedule and notes around the event more generally.
6 |
7 | # Title
8 |
9 | [To what extent can machine-actionable data management plans help automate disaster-related workflows?](https://github.com/Daniel-Mietchen/events/issues/337#issuecomment-400886404)
10 |
11 | # Abstract
12 |
13 |
14 | As highlighted in the session description, disaster reduction and mediation efforts are closely linked to the Sustainable Development Goals and have a broad range of data needs. These data needs include coping with a variety of kinds of data, zero to many resources that provide such data, long-term versus real-time data, data quality issues, the ethics of sharing (or not) and how, management of data-related resources (or the lack thereof) and various degrees of uncertainties around any of this and integration across or zooming in on various aspects thereof.
15 |
16 | In this session, I would like to explore some avenues towards a higher degree of automation to address these data needs, focusing on how the concept of a Data Management Plan or the more general notion of an output management plan that has been put forward by the Wellcome Trust can be used to inform policies, workflows and infrastructure around disaster reduction and response. In particular, I will highlight the potential of making such plans machine-actionable, versioned, FAIR and public. This would allow to aggregate, visualize and reslice the information contained in such plans and to use it to interact with disaster-related infrastructure, policies or actors, or as a basis for people, organizations or machines to learn from data gathered about ongoing or past disasters.
17 |
18 | For any specific future disaster, many details are of course unknowable at present, but depending on the kind of disaster, certain characteristic data needs are predictable to some extent. Disease outbreaks, for instance, may require different responses based on whether the respective pathogens and their potential modes of transmission are known or not, what their zoonotic potential is, where their host species live, whether the affected animal or human populations have any degree of immunity, whether travel or migration are involved, and so forth. On the basis of initial responses to these questions, decisions can be made as to whether additional information is needed, how to gather it, how to process, aggregate and communicate what is known, how to derive recommendations (e.g. with respect to vaccine campaigns or travel recommendations, or what research to fund), and what the corresponding resource needs are in terms of humans, machines, infrastructure, finances and logistics, where and on what time scales.
19 |
20 | Similar questions can be asked for other disaster scenarios like earthquakes, wildfires, storms or oil spills, and information related to such questions already forms the backbone of institutionalized disaster response and prevention mechanisms in many contexts. What is often missing, though, is the interoperability - on both long and short time scales - of such existing mechanisms across actors, jurisdictions, disaster types, or research disciplines. Some pockets of basic interoperability exist in various places, e.g. emergency phone numbers are harmonized within most nations and across EU member states, tsunami warnings can be broadcast nationally or regionally within seconds of an earthquake, and high-speed trains can come to a stop in response. How can we achieve similar harmonization around disaster-related data, repositories, APIs, data models, simulations and related issues, how would that affect humans and machines, and how can we track relevant progress with respect to the Sustainable Development Goals?
21 |
22 | # Presentation
23 |
24 | This talk will not have slides beyond this page. Instead, I will walk the audience through a set of online resources linked below and comment on them from the perspective of how the concept of data/ output management plans that is popularized in research data contexts can be enhanced by ideas about making those plans machine actionable and then applied in the context of managing disaster-related data:
25 | - Michener WK (2015) Ten Simple Rules for Creating a Good Data Management Plan. PLoS Comput Biol 11(10): e1004525. https://doi.org/10.1371/journal.pcbi.1004525
26 | - The piece is written with research data management in mind, which we will replace with disaster-related data in our minds for the purpose of this session.
27 | - Miksa, Tomasz, Simms, Stephanie, Mietchen, Daniel, & Jones, Sarah. (2018). Ten principles for machine-actionable data management plans. Zenodo. http://doi.org/10.5281/zenodo.1461713
28 | - This piece outlines ten principles for making data management plans machine actionable, which we will apply to disaster contexts.
29 | - See also [RDA poster 7 "Ten principles for machine-actionable data management plans"](https://www.rd-alliance.org/rdas-12th-plenary-poster-session) ([in action](https://twitter.com/GigaScience/status/1059447556684607488)) and RDA breakout session "[Use cases for machine-actionable data management plans](https://www.rd-alliance.org/wg-dmp-common-standards-rda-12th-plenary-meeting)" this morning
30 | - [Data sharing as a new component of addressing and preparing for disease outbreaks](SciDataCon-2018-data-sharing.md)
31 | - talk given in the session "[Health Databases across the African Continent: What do we have and what do we need for Sustainable Development?](https://www.scidatacon.org/IDW2018/sessions/222/)" earlier this afternoon
32 | - We will look at some of the examples presented in there from the perspective of generalizing from (past and present) disease outbreaks to (past and present) disasters more generally and how that can inform future data-related activities in disaster contexts.
33 |
--------------------------------------------------------------------------------
/SciDataCon-2018.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file collects information related to my participation in [SciDataCon 2018](https://www.scidatacon.org/IDW2018/), which is part of [International Data Week](International-Data-Week-2018.md) (see my schedule there).
4 |
5 | # Submitted session proposals
6 |
7 | - submitted as per deadline of [February 19, 2018](https://github.com/Daniel-Mietchen/events/issues/321)
8 | - Topics
9 | - [Data sharing in public health emergencies](SciDataCon-2018-data-sharing.md)
10 | - merged into [Session 262: Open Data from Cell Biology of Infectious Pathogens, how far are we?](https://www.scidatacon.org/IDW2018/sessions/262/)
11 | - [Workshop: Integrating Wikidata with research and curation workflows](SciDataCon-2018-Wikidata.md)
12 | - [Turning FAIR Data Into Reality: discussion, critique and implementation ](https://www.scidatacon.org/IDW2018/sessions/229/)
13 | - accepted
14 |
15 | # Submitted contributions to accepted sessions
16 |
17 | - submission deadline was [28 June 2018](https://github.com/Daniel-Mietchen/events/issues/337)
18 | - Topics
19 | - [To what extent can machine-actionable data management plans help automate disaster-related workflows?](https://github.com/Daniel-Mietchen/events/issues/337#issuecomment-400886404)
20 | - submitted as a talk, accepted as poster 141, then converted back into an oral presentation
21 | - [Data sharing as a new component of addressing and preparing for disease outbreaks](https://github.com/Daniel-Mietchen/events/issues/337#issuecomment-400867604)
22 | - accepted as an oral presentation
23 | - [Wikidata and Wikibase as global platforms for democratizing data publishing](https://github.com/Daniel-Mietchen/events/issues/337#issuecomment-400858737)
24 | - accepted as an oral presentation
25 | - [A wiki approach to collecting, curating and managing citizen science data](https://github.com/Daniel-Mietchen/events/issues/337#issuecomment-400861223)
26 | - accepted as a poster
27 | - [A wiki perspective on an Open Science Commons](https://github.com/Daniel-Mietchen/events/issues/337#issuecomment-400864289)
28 | - accepted as a poster
29 | - [WikiCite and Scholia - a Linked Open Data approach to exploring the scholarly literature and related resources](https://github.com/Daniel-Mietchen/events/issues/337#issuecomment-400893901)
30 | - accepted as a poster
31 |
32 | # Other topics I had considered for submissions
33 |
34 | - Citizen science and open science
35 | - Wikidata as a FAIR data platform
36 | - Making ethics data FAIR
37 | - machine-actionable policies
38 | - a data management plan for a disease outbreak
39 | - Wikidata and the SDGs
40 |
41 | # See also
42 |
43 | * [SciDataCon 2016 talk](SciDataCon2016.md)
44 |
--------------------------------------------------------------------------------
/Summer-2020-Climate-Reality-Leadership-Corps-Global-Training.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts materials related to my participation in a [Climate Reality Global Training](https://climaterealityproject.org/apply/globaltraining) in summer 2020, for which there was an application process.
4 |
5 | Apart from lots of personal information, their application form also asked "What do you hope to get out of the Climate Reality Leadership Corps training?", for which a field with a maximum of 1000 characters was allocated but the form would not let me submit it if I had any text in that field. So here is what I wanted to put in there (slightly reformatted):
6 |
7 | 1. Further systematic progress with my first [New Year Resolution for 2020](https://github.com/Daniel-Mietchen/ideas/blob/master/new-year-resolutions/2020.md), which is to "review all of my major professional, volunteer and family activities from the perspective of their sustainability"
8 | 1. Increasing my climate-related contact network within and beyond the circles through which I usually engage in climate matters, i.e. open science, open data, open knowledge and open collaboration, including via Wikipedia and its sister projects
9 | 1. Getting new inspiration for what I can do in my volunteer, professional and personal realms to address climate change and related issues
10 | 1. Getting a better idea of what to do myself versus where to build on what others are doing
11 | 1. Finding new collaborators, learning about what they do and how they go about finding and enriching their niche in terms of addressing climate change
12 | 1. Something to inspire my social circles, especially my children and students
13 | 1. Applying my skills in a broader context than usual
14 |
15 | # History
16 |
17 | I initially applied to join the training on July 18-26, 2020, but on July 7, I was notified that my slot would rather be in the follow-up training on August 28-September 3, 2020. On July 30, I received an RSVP request for the latter event, to which I responsed affirmatively on August 1. While this file was originally created as July-2020-Climate-Reality-Leadership-Corps-Global-Training.md, I then changed it to Summer-2020-Climate-Reality-Leadership-Corps-Global-Training.md.
18 |
19 | # About me
20 |
21 | * [Biographical sketch](https://en.wikipedia.org/wiki/User:Daniel_Mietchen/Biographical_sketch)
22 | * [Scholia](https://scholia.toolforge.org/author/Q20895785)
23 |
--------------------------------------------------------------------------------
/UVA-Datapalooza-2017.md:
--------------------------------------------------------------------------------
1 | # Open data: central element of an open research ecosystem
2 | *You can watch the [video recording](https://www.youtube.com/watch?v=6qDEeRsMv7s#t=10m) of the presentation.*
3 |
4 | ["Open data … can help create $3 trillion a year"](https://www.mckinsey.com/business-functions/digital-mckinsey/our-insights/open-data-unlocking-innovation-and-performance-with-liquid-information)
5 | - "[underestimate](https://twitter.com/hudsonhollister/status/928996816640794628)"
6 |
7 | [Listen to open data](http://listen.hatnote.com/#en,fa,ar,sa,es,de,ru,jp,zh,ko)
8 |
9 | [](https://commons.wikimedia.org/wiki/File:Discovery_in_process.jpg)
10 |
11 | [](https://commons.wikimedia.org/wiki/File:Automated_weighbridge_for_Ad%C3%A9lie_penguins_-_journal.pone.0085291.g002.png)
12 |
13 |
14 | | [](https://commons.wikimedia.org/wiki/File:KsiegaSzkocka1.JPG) [](https://commons.wikimedia.org/wiki/File:Euromaidan_in_Kiev_2014_003.jpg) [](https://commons.wikimedia.org/wiki/File:00000003_F.jpg) [](https://en.wikipedia.org/wiki/File:IBM_Blue_Gene_P_supercomputer.jpg) [](https://commons.wikimedia.org/wiki/File:LIGO_measurement_of_gravitational_waves.svg) | [](https://commons.wikimedia.org/wiki/File:Ernst-Abbe-Denkmal_Jena_F%C3%BCrstengraben_-_20140802_125709.jpg) [](https://commons.wikimedia.org/wiki/File:Adaptive-Evolution-of-Eel-Fluorescent-Proteins-from-Fatty-Acid-Binding-Proteins-Produces-Bright-pone.0140972.g001.jpg) [](https://commons.wikimedia.org/wiki/File:Zika_EM_CDC_20541.png) [](https://commons.wikimedia.org/wiki/File:Carl_Spitzweg_021.jpg) [](https://commons.wikimedia.org/wiki/File:Road_Sign_SOLAR_ECLIPSE_TODAY_-_IMG_20170821_172443.jpg) [](https://commons.wikimedia.org/wiki/File:New_cuyama.jpg) | [](https://commons.wikimedia.org/wiki/File:Sudan_Envoy_-_Curious_Onlookers.jpg) [](https://commons.wikimedia.org/wiki/File:Everything_must_go.jpg) [](https://commons.wikimedia.org/wiki/File:In_Thought_..._(3020466221).jpg) [](https://commons.wikimedia.org/wiki/File:TGG_Icon_Color_18.png) [](https://commons.wikimedia.org/wiki/File:Wikidata_Map_July_2017_Normal.png) |
15 | |--------|--------|:---:|
16 | | [reproducibility](http://mybinder.org/repo/cranmer/ligo-binder) = f(data, metadata, code, …)| [reusability](http://tinyurl.com/ycpdwvmx) = g(data, metadata, code, …) | [open workflows are an invitation to collaborate, early and often](https://twitter.com/EvoMRI/status/928248498503417856)|
17 | | [remote Doathon](http://doathon.opencon2017.org/) | [November Data Science Meetup](https://www.meetup.com/CharlottesvilleDataScience/events/244483558/) | [on-site Doathon](https://github.com/UVA-DSI/2017-doathon/) |
18 |
19 | # Image credits
20 |
21 | All images are linked to pages with metadata about them, including licensing information. The licensing is always compatible with the [CC BY-SA 4.0 license](https://creativecommons.org/licenses/by-sa/4.0/).
22 |
23 | # See also
24 |
25 | - [Slides of the other Research Highlights talks](https://docs.google.com/presentation/d/1gWa2N8yjVetzDO6g6GQj8-Wbho4QZsjZHrcgsa2d4VU/edit), including the report from the [Biomedical Data Science hackathon](https://github.com/databio/bds_hackathon).
26 | - A [video introduction to open research](https://www.youtube.com/watch?v=LwW1-X3glak)
27 | - [Open Science Q & A](https://openscience.ub.uni-bielefeld.de/)
28 | - [The event app](http://goo.gl/qLkj9h).
29 | - My number is 441.
30 | - Twitter:
31 | - hashtag: [#Datapalooza2017](https://twitter.com/hashtag/datapalooza2017?f=tweets&vertical=default), not [#Datapalooza](https://twitter.com/hashtag/datapalooza?f=tweets&vertical=default), but [here are both](https://twitter.com/search?f=tweets&vertical=default&q=datapalooza2017%20OR%20datapalooza)
32 | - I'm [@EvoMRI](https://twitter.com/EvoMRI)
33 | - Two recent papers on Wikidata as an open data hub for research-related information
34 | - [WikiPathways: a multifaceted pathway database bridging metabolomics to other omics research](https://doi.org/10.1093/nar/gkx1064)
35 | - [came out of a rejected proposal](https://twitter.com/egonwillighagen/status/929002491928301568)
36 | - [Scholia, Scientometrics and Wikidata](https://doi.org/10.1007/978-3-319-70407-4_36)
37 |
38 | # About
39 |
40 | This file is facilitating a presentation at the [Datapalooza 2017](https://dsi.virginia.edu/datapalooza-2017-agenda) taking place at the University of Virginia on November 10, 2017. The presentation is part of the "Research Highlights" session at 10:30 am EST in the Newcomb Ball Room, and it will be given on the basis of this file here on GitHub. The session is being recorded, and the recordings will be made available afterwards.
41 |
--------------------------------------------------------------------------------
/WCSE.md:
--------------------------------------------------------------------------------
1 | # About
2 | This file is a submission to the World Conference of Scientists and Engineers (세계과학기술인대회), to take place on July 13-14, 2016, in Seoul.
3 |
4 | # Submission
5 |
6 | ## Title
7 | Sharing as an enabler of scholarship
8 |
9 | ## Author
10 | Daniel Mietchen
11 |
12 | ## Affiliation
13 | Open Knowledge Foundation Germany
14 |
15 | ## Email
16 | daniel.mietchen (at) okfn.org
17 |
18 | ##Keywords
19 | open science, networked science, sharing, science policy, research communication
20 |
21 | ##Abstract
22 | Research is the process of systematically collecting information to expand the boundaries of scholarly knowledge. With the ongoing transition towards digital and Web-based research communication, the scholarly record has broadened in scope to include data, software and other research artifacts. Conversely, the Web has given rise to new forms of scholarship that transcend traditional boundaries between disciplines, jurisdictions, economic sectors or professional and amateur researchers.[1]
23 |
24 | A key enabler of these new forms of scholarship is sharing: more research is shared more widely and more openly now than just a decade ago.[2] On the other hand, the incentive structures in academia – both globally and in Korea – are heavily biased against broad and open sharing.
25 |
26 | In this contribution, I will examine examples of such open and sharing-enabled scholarship – like the Polymath Projects [3] in mathematics, the FoldIt project [4] in structural biology, the Zooniverse projects [5] in astronomy, the Praziquantel project [6] in drug discovery or the genome annotation of the 2011 E. coli O104:H4 outbreak [7] – to highlight factors that determine the success of such projects from the perspective of the different stakeholders as well as society as a whole. I will end by exploring the implications for research communication [8] as well as research policy [9].
27 |
28 | ##References
29 | [1] Patil C, Siegel V (2009) This revolution will be digitized: online tools for radical collaboration. Disease Models & Mechanisms 2: 201‑205. doi: [10.1242/dmm.003285](http://doi.org/10.1242/dmm.003285)
30 | [2] Watson M. When will ‘open science’ become simply ‘science’?. Genome Biology. 2015 May 19;16(1):101. doi: [10.1186/s13059-015-0669-2](http://doi.org/10.1186/s13059-015-0669-2)
31 | [3] Gowers T, Nielsen M (2009) Massively collaborative mathematics. Nature 461(7266): 879‑881. doi: [10.1038/461879a](http://doi.org/10.1038/461879a)
32 | [4] Eiben CB, Siegel JB, Bale JB, Cooper S, Khatib F, Shen BW, Players F, Stoddard BL, Popovic Z, Baker D. Increased Diels-Alderase activity through backbone remodeling guided by Foldit players. Nature Biotechnology. 2012 Feb 1;30(2):190-2. doi: [10.1038/nbt.2109](http://doi.org/10.1038/nbt.2109)
33 | [5] Cardamone C, Schawinski K, Sarzi M, Bamford SP, Bennert N, Urry CM, Lintott C, Keel WC, Parejko J, Nichol RC, Thomas D. Galaxy Zoo Green Peas: discovery of a class of compact extremely star-forming galaxies. Monthly Notices of the Royal Astronomical Society. 2009 Nov 1;399(3):1191-205. doi: [10.1111/j.1365-2966.2009.15383.x](http://doi.org/10.1111/j.1365-2966.2009.15383.x)
34 | [6] Woelfle M, Olliaro P, Todd M (2011) Open science is a research accelerator. Nature Chemistry 3(10): 745‑748. doi: [10.1038/nchem.1149](http://doi.org/10.1038/nchem.1149)
35 | [7] Rohde H, Qin J, Cui Y, Li D, Loman NJ, Hentschke M, Chen W, Pu F, Peng Y, Li J, Xi F. Open-source genomic analysis of Shiga-toxin–producing E. coli O104: H4. New England Journal of Medicine. 2011 Aug 25;365(8):718-24. doi: [10.1056/NEJMoa1107643](http://doi.org/10.1056/NEJMoa1107643)
36 | [8] Mietchen D, Mounce R, Penev L (2015) Publishing the research process. Research Ideas and Outcomes 1: e7547. doi: [10.3897/rio.1.e7547](http://doi.org/10.3897/rio.1.e7547)
37 | [9] Alberts B, Kirschner MW, Tilghman S, Varmus H. Rescuing US biomedical research from its systemic flaws. Proceedings of the National Academy of Sciences. 2014 Apr 22;111(16):5773-7. doi: [10.1073/pnas.1404402111](http://doi.org/10.1073/pnas.1404402111)
38 |
--------------------------------------------------------------------------------
/WeMissiPRES-2020.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a submission to [WeMissiPRES](https://www.dpconline.org/events/wemissipres), the virtual iPRES conference on 22-24 September 2020 that replaces the canceled in-person one. I submitted it shortly before the deadline on 19 August 2020, and the content I entered in their form is also available below. On August 26, I was informed of the acceptance of the submission, and we were requested to confirm our intention to present, which we did.
4 |
5 | For the presentation itself, I ended up not being connected, so Mark Graham [presented](https://www.youtube.com/watch?v=i2p0OTE5ZHM#t=2h28m).
6 |
7 | # Questions from the submission form
8 |
9 | ## Title
10 |
11 | Digital preservation of catastrophic events
12 |
13 |
14 | ## Keywords
15 | disaster management, link rot, disaster preparedness, disaster communication
16 |
17 | ## Length of Presentation (max of 10 mins) *
18 |
19 | 10
20 |
21 | ## Please list any other contributors who will be making the presentation along with you
22 |
23 | Mark Graham, Internet Archive
24 |
25 | ## Please submit a 100 word description of your presentation, thinking about the theme which best fits your proposal and how you would like to present it. *
26 |
27 | In catastrophic events, be they natural or human-triggered, circumstances can change profoundly, quickly and with long-lasting effects on potentially broad swaths of the affected populations as well as their surroundings, including physical and digital infrastructure. In such situations, efficient communication is key but may have to be improvised or adapted to the situation at hand. This often means that the channels used for that tend to be ephemeral, so their digital preservation provides additional challenges. In this talk, we will discuss examples of disaster communication, highlight opportunities for the future and outline how the digital preservation community can get involved.
28 |
29 | ## Please describe the intended format for your presentation e.g. slides with voice over, lecture with camera on, demo, multiple presenters, live survey etc (50 words max) *
30 |
31 | Slides and demo with voiceover, by both presenters and with a live survey
32 |
33 | # See also
34 |
35 | * [COVID-19: The duty to document does not cease in a crisis, it becomes more essential](https://www.dpconline.org/news/the-duty-to-document-covid)
36 | - mentions "ephemeral technologies", linked to [The 'Bit List' of Digitally Endangered Species](https://www.dpconline.org/digipres/champion-digital-preservation/bit-list), which seems worth combing through from the perspective of technologies used in disaster contexts
37 |
--------------------------------------------------------------------------------
/WikiCite-Cologne-2020.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This page details my contributions to [WikiCite Satellite Cologne 2020](https://www.wikidata.org/wiki/Wikidata:WikiCite_Satellite_Cologne_2020) taking place in late 2020 (postponed from an original time of 6-8 May 2020) in Cologne.
4 |
5 | # Keynote
6 |
7 | ## Title
8 |
9 | WikiCite as a hub for collaborative curation of bibliographic and citation metadata
10 |
11 | ## Abstract
12 |
13 | The Wikimedia community has always appreciated the value of reliable sources and built lots of workflows and tools around that. The WikiCite community helps in bringing these initiatives closer together across wikis, languages and disciplines. Right from its start, it has also welcomed participation from others interested in bibliographic and citation information, and built workflows that allow to curate such information collaboratively at Wikimedia scale.
14 |
15 | This contribution will be given on the basis of https://github.com/Daniel-Mietchen/events/blob/master/WikiCite-Cologne-2020.md and zoom in on implications that this role as a hub for collaborative curation might have for WikiCite, the Wikimedia community and others engaged in curating bibliographic and citation information.
16 |
17 | # Workshops
18 |
19 | I have proposed the following two workshops:
20 |
21 | - [Scholia workshop](https://www.wikidata.org/wiki/Wikidata:WikiCite_Satellite_Cologne_2020/Submission/Scholia_workshop)
22 | - [Planning remote-first WikiCite events](https://www.wikidata.org/wiki/Wikidata:WikiCite_Satellite_Cologne_2020/Submission/Planning_remote-first_WikiCite_events)
23 |
24 | # Editathon
25 |
26 | As a satellite to the official event, I have proposed an [editathon](https://de.wikipedia.org/wiki/Wikipedia:Lokal_K/WikiCite_2020) in the local Wikimedia premises, focused on WikiCite activities with some connection to Cologne.
27 |
--------------------------------------------------------------------------------
/Wikimania-2016.md:
--------------------------------------------------------------------------------
1 | # About
2 | This is a submission for [Wikimania 2016](https://wikimania2016.wikimedia.org/wiki/Submissions), co-authored with [@DarTar](https://github.com/dartar). It was rejected on February 1, 2016.
3 |
4 | # Title
5 | Citations needed for the sum of all human knowledge
6 |
7 | # Abstract
8 | The idea of a repository to store all citations and source metadata across Wikimedia projects has been proposed in different forms for the past 10 years. Wikipedia is one of the most popular entry points into the scientific literature and ranges among the top 5 referrers of scholarly citations. However, as of today, references and source metadata are still a second-class citizen in Wikimedia projects.
9 |
10 | References are one of the most fundamental building blocks of every Wikipedia article, but:
11 | - they are still served by fragile mechanisms such as citation templates;
12 | - they are inconsistently represented across (and sometimes within) articles, languages and projects;
13 | - the data they store is curated in multiple places and often ill-formed, incomplete and not machine-readable;
14 | - they often fail to use identifiers such as DOIs or PubMed IDs, even when such identifiers are available for the cited source.
15 |
16 | Reusing sources across articles, languages or projects is still a complex task, and conducting research on the use of references and citations in Wikimedia projects requires sophisticated information extraction skills. In addition to that, a large number of statements in Wikidata are currently not sourced at all or generically sourced to a Wikimedia site rather than specific references.
17 |
18 | In this session, we will review the state of citations and source metadata in Wikimedia projects. We will discuss in particular progress made so far towards the vision of building a centralized database of all citations and source metadata through Wikidata. Focusing on scholarly journal articles, the session builds on initiatives that go back to Wikimania London 2014 and have continued over the years via a number of "Citathons" and events, thanks to the dedication of several Wikipedians, Wikidatans, librarians, software developers, and partner organizations. The technology needed to sustain this effort is maturing, the modeling of a schema to represent scholarly article metadata is nearly completed, and Wikidata already counts over 20,000 items for individual scholarly works that are identified by unique identifiers, have begun to be used as references for Wikidata statements and could be used to improve the handling of references on other Wikimedia projects .
19 |
20 | The time is ripe for the Wikimedia movement and our partners to identify the necessary steps towards achieving this vision.
21 |
22 | # Keywords
23 | references
24 | sources
25 | citations
26 | bibliographic metadata
27 | author disambiguation
28 | altmetrics
29 | Wikidata
30 | Wikischolar
31 | Wikicite
32 | Librarybase
33 | GLAMwiki
34 |
35 | # Topics
36 | Technical
37 | Projects
38 | Research
39 |
40 |
--------------------------------------------------------------------------------
/data-science-in-climate-and-climate-impact-research.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file supports a contribution to the Workshop "[Data Science in Climate and Climate Impact Research](https://wcr.ethz.ch/news-and-events/events/workshop--data-science-in-climate-and-climate-impact-research-.html)" taking place on 20-21 August 2020 in Zurich and online.
4 |
5 | # Title
6 |
7 | Multilingual Structured Climate Research Data in Wikidata - The Data Perspective
8 |
9 | # Abstract
10 |
11 | Climate research — like research in general — takes place in a sociotechnical ecosystem that connects researchers, institutions, funders, databases, locations, publications, methodologies and related concepts with the objects of study and the natural and cultural worlds around them.
12 |
13 | Mechanisms for describing concepts related to climate research are growing in breadth and depth, number and popularity. In parallel, more and more climate-related data — and particularly metadata — are being made available under open licenses, which facilitates discoverability, reproducibility and reuse, as well as data integration.
14 |
15 | Wikidata is a community-curated open knowledge base in which concepts covered in any Wikipedia — and beyond — can be described in a structured and FAIR fashion that can be mapped to RDF and queried using SPARQL as well as various other means. Its community of over 20,000 monthly contributors oversees a corpus of currently over 80 million ‘items’ for concepts that are linked amongst each other, to external databases or to specific values via over 7000 'properties'. Items and properties have persistent unique identifiers, to which labels, descriptions and dedicated lexemes and their forms and senses can be attached in over 300 natural languages.
16 |
17 | A range of open-source tools is available to interact with Wikidata — to enter information, curate and query it. In this presentation — available via https://github.com/Daniel-Mietchen/events/blob/master/data-science-in-climate-and-climate-impact-research.md — we will outline a range of tools that allow to explore Wikidata content through frontends tailored to specific communities. In particular, we will take a look at Scholia, which is available via https://tools.wmflabs.org/scholia/ and allows to generate and explore scholarly profiles of authors, institutions, funders and other parts of the research ecosystem, as well as of the world in which it is embedded, from geomorphological features to economic indicators and environmental policies, from natural ecosystems and disasters to biogeochemical cycles.
18 |
19 | # Citation
20 |
21 | Mietchen, Daniel, & Sarasua, Cristina. (2020, August). Multilingual Structured Climate Research Data in Wikidata - The Data Perspective. Zenodo. [http://doi.org/10.5281/zenodo.3994266](http://doi.org/10.5281/zenodo.3994266).
22 |
23 | # History
24 |
25 | The submission was co-authored by Cristina Sarasua from University of Zurich and submitted on 6 April 2020 before the extended deadline. On 20 April, I was notified of its acceptance.
26 |
27 | # Companion talk
28 |
29 | * There is an accompanying submission (also accepted on 20 April) led by Cristina and co-authored by me, entitled "Multilingual Structured Climate Research Data in Wikidata - The Community Perspective". Its abstract reads as follows:
30 | * > Empirical sciences experience a transformation enabled by a myriad of technological solutions that facilitate collecting, sharing and analyzing large- and small-scale research data. Citation networks can be mined, scientific workflows can be reproduced and extended, and data-driven search portals allow scientists to dive into a sea with millions of data sets. While technology is crucial, the success of this transformation heavily depends on social change and commitment. At the core of such a social response, the Open Science movement promotes values such as participation and collaboration. Tightly connected to Open Science, the Free Knowledge initiative advocated by Wikimedia has succeeded in bringing scientific output (and general human knowledge) closer to the global population through platforms like Wikipedia. Wikidata is a community-supported knowledge base, where thousands of volunteers enter, complete, link, monitor and correct data. Wikidata is connected to Wikipedia articles and images in Wikimedia Commons, and it can be queried as machine-readable Linked Data. In this presentation, we would like to showcase Wikidata’s special features in terms of collaborative knowledge management. We will demonstrate how ranks and references allow Wikidata to portray a plural reality in which contradictory statements might have been published by different sources. We will also demonstrate the way federated queries can facilitate data comparison. Moreover, we will describe the process that editors follow to address schema and data quality management collectively, as well as human-bot cooperation. We will also talk about the possibility of transferring many of Wikidata’s features to self-organized communities via Wikibase. Through concrete examples and descriptive statistics, we aim to show the benefits that a community-based data management cycle can provide to many disciplines, including the field of Climate Research.
31 | * Citation: Sarasua, Cristina, & Mietchen, Daniel. (2020, August). Multilingual Structured Climate Research Data in Wikidata - The Community Perspective. Zenodo. [http://doi.org/10.5281/zenodo.3994272](http://doi.org/10.5281/zenodo.3994272).
32 |
33 | # Presentation
34 |
35 | * [Slides for both talks](https://docs.google.com/presentation/d/1EbocwNrGq6f_YyLnbkqbjiHdC-J6q8OZU2Aowfr9-0A/edit)
36 | * Zenodo snapshots:
37 | * [Multilingual Structured Climate Research Data in Wikidata - The Community Perspective (DOI: 10.5281/zenodo.3994272)](https://doi.org/10.5281/zenodo.3994272)
38 | * [Multilingual Structured Climate Research Data in Wikidata - The Data Perspective (DOI: 10.5281/zenodo.3994266)](https://doi.org/10.5281/zenodo.3994266)
39 | * Backup copy on YouTube: [https://youtu.be/ntI6hmT-rRc](https://youtu.be/ntI6hmT-rRc)
40 | * [Scholia entry for the event](https://scholia.toolforge.org/event/Q98457439)
41 |
42 | # See also
43 |
44 | * [Etherpad for the event](https://etherpad.wikimedia.org/p/data-science-in-climate-workshop) — contains links to several slide sets
45 | * I gave a presentation "[Visualizing the research ecosystem of ecosystem research via Wikidata](ICEI2018-research-ecosystem.md)" at the [10th International Conference on Ecological Informatics](http://icei2018.uni-jena.de/) (ICEI 2018) on 27 September 2018 in Jena, co-authored by Finn Årup Nielsen and Egon Willighagen. That event was also attended by Markus Reichstein, one of the keynote speakers at the climate workshop.
46 | * Presentation "[Visualizing the research ecosystem of neuroscience research via Wikidata](neuromatch3.md)" at [neuromatch 3.0](https://neuromatch.io/) in October 2020
47 |
48 |
--------------------------------------------------------------------------------
/neuromatch3.md:
--------------------------------------------------------------------------------
1 | # About
2 |
3 | This file hosts a contribution to the [neuromatch 3.0](https://neuromatch.io/) conference taking place online on October 26-30, 2020, as per [this ticket](https://github.com/Daniel-Mietchen/events/issues/701). The contribution has been submitted on October 2, 2020, in response to their call for proposals with a deadline of October 7, 2020, as per [this ticket](https://github.com/Daniel-Mietchen/events/issues/702).
4 |
5 | # Abstract
6 |
7 | *300 words maximum*
8 |
9 | Visualizing the research ecosystem of neuroscience research via Wikidata
10 |
11 | Neuroscience research — like research in general — takes place in a sociotechnical ecosystem that connects researchers, institutions, funders, databases, locations, publications, methodologies and related concepts with the objects of study and the natural and cultural worlds around them.
12 |
13 | Mechanisms for describing concepts related to neuroscience research are growing in breadth and depth, number and popularity. In parallel, more and more neuroscience-related data — and particularly metadata — are being made available under open licenses, which facilitates discoverability, reproducibility and reuse, as well as data integration.
14 |
15 | Wikidata is a community-curated open knowledge base in which concepts covered in any Wikipedia — and beyond — can be described in a structured and FAIR fashion that can be mapped to RDF and queried using SPARQL as well as various other means. Its community of over 20,000 monthly contributors oversees a corpus of currently over 90 million 'items’ for concepts that are linked amongst each other, to external databases or to specific values via over 7000 'properties'. Items and properties have persistent unique identifiers, to which labels, descriptions and dedicated lexemes and their forms and senses can be attached in over 300 natural languages.
16 |
17 | A range of open-source tools is available to interact with Wikidata — to enter information, curate and query it. In this presentation — which shall be available via https://doi.org/10.5281/zenodo.4064274 — we will outline a range of tools that allow to explore Wikidata content through frontends tailored to specific communities. Based on examples from the neurosciences, we will take a look at Scholia — available via https://scholia.toolforge.org/ — which allows to generate and explore Wikidata-based scholarly profiles of research topics, authors, institutions, funders and other parts of the research ecosystem, as well as of the world in which it is embedded.
18 |
19 |
20 | # See also
21 |
22 | * The [etherpad for the session](https://etherpad.wikimedia.org/p/zenodo.4064274)
23 | * Similar presentations:
24 | - [Open profiling of chemical knowledge](https://github.com/Daniel-Mietchen/events/blob/master/Beilstein-Open-Science-Symposium-2020.md)
25 | - [Multilingual Structured Climate Research Data in Wikidata - The Data Perspective](data-science-in-climate-and-climate-impact-research.md) on 21 August 2020
26 | - [Visualizing the research ecosystem of ecosystem research via Wikidata](https://github.com/Daniel-Mietchen/events/blob/master/ICEI2018-research-ecosystem.md) on 27 September 2018
27 |
28 |
--------------------------------------------------------------------------------