Skip to content

Latest commit

 

History

History
75 lines (59 loc) · 8.44 KB

Sage-Assembly-2017.md

File metadata and controls

75 lines (59 loc) · 8.44 KB

About

On April 20-22, the 2017 Sage Assembly (hashtag: #SageAssembly) 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. 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".

From the homepage:

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.

Some of my activities in this space

3-min talks

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".

I decided 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), Wikimedia, Gathering for Open Source Hardware (GOSH)) and What we know about the future.

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:

  • Map: How to map any research ecosystem?
  • How to map research that is being performed now or planned for the near future?
    • some inspiration: real-time visualization and sonification of Wikimedia edits
    • What about doing this for research?
    • with appropriate filtering, something like this could serve as the basis for researchers, funders, public and others to engage with a given research topic
    • particularly relevant in the case of public health emergencies, which also provide a context where "open by default" is actually within reach
    • works best if data and metadata are FAIR by default
    • publicly versioned machine actionable data (or project) management plans as a way to connect research projects (past, ongoing and future) with relevant individuals, communities, institutions and their respective resources and workflows
  • 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?
    • Wikidata as a hub for structured open knowledge across domains, with biomedicine being one of the pilot areas
  • Ethics: making ethics data FAIR
  • Sustainability: How to better align the priorities within the research ecosystems (open or not) with the needs of humanity as a whole?
  • Lean administration: How can openness be used to reduce bureaucracy?
  • Effective policies: How can different policies and infrastructures be made better aware of each other?

Demo

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 for a talk covering part of this topic), but this suggestion was not taken.

ORCID

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.

Notes on the individual sessions

  • 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 I opened for this event.

Contact

@EvoMRI