Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 

Repository files navigation

EcoWeaver & TReK Community

Introduction

The need for effective action on the global biodiversity crisis has never been more dire. Globally, nations are taking action to counteract severe landscape degradation. The United Nations launched its Decade on Ecosystem Restoration in 2021, kicking off further large-scale initiatives including the recently adopted EU Nature Restoration Law and the Kunming-Montreal Global Biodiversity Framework. However, despite global action, restoration activities remain scattered, disparate, and only loosely grounded in the bulk of available evidence. In order to conduct effective restoration and for ecological science to inform land management at the scale required, we need to develop a broad and deep evidence base that can be used for guiding effective restoration and management.

There are several reasons why no accessible, integrated evidence base exists yet. Even though restoration is a relatively young field, there is a vast trove of Grey literature and associated materials – professional reports, mapping, monitoring data, project summaries, and more. However, these are often uncatalogued and thus unavailable. Increasing volumes of peer-reviewed scientific literature contain knowledge useful for restoration as well, but much of it is not openly accessible. Further, traditional publications are not easily interpretable by non-scientists. These texts usually lack semantic annotations and therefore cannot be interpreted by machines, making automated information extraction challenging. Lastly, even if all these sources of information were readily available, it would still be challenging to decide how knowledge gathered in one specific ecosystem or location can be transferred to a different situation.

In theory, there is a lot of information that could be used for building up an encompassing knowledge base. Other fields (e.g. biomedicine) have started tackling the challenge of scattered knowledge using modern computer science practices (i.e. knowledge graphs, ontologies, AI), but ecology broadly lags behind. The EcoWeaver & TReK Community is an international and interdisciplinary collaborative that includes ecologists, computer scientists and philosophers, aiming at bringing these technologies to the field. The goal is to develop and implement a Toolkit for Restoration Knowledge (TReK) that will provide a deep and useful evidence base for ecological restoration. TReK will be the first core application of EcoWeaver, which is envisioned as the backbone infrastructure that collects and stores ecological knowledge and offers diverse options for on-demand synthesis, model development and data visualization for a variety of ecological sub-disciplines. It aims at supporting scientific progress, making scientific knowledge accessible and comprehensible, thus increasing trust in science and supporting decision making. It will allow making the most of the existing body of ecological knowledge.

Joint vision

EcoWeaver and the Toolkit for Restoration Knowledge (TReK): From ecological knowledge to restoration action

Our vision is to weave together, with the help of latest computational technologies, ecological knowledge from diverse sources, thus creating the EcoWeaver, a FAIR and openly accessible knowledge base that supports the generation of novel insights, enhances ecological understanding and empowers people to make informed decisions. The Toolkit for Restoration Knowledge, the core application of the EcoWeaver, is tailored for significantly enhancing the efficiency and effectiveness of ecosystem restoration. Communities of Practice, consisting of diverse teams of practitioners, scientists and local knowledge holders, are participating in the development of the EcoWeaver and TReK, ensuring their just and meaningful implementation.

Positionality Statement

Positionality
Acknowledging positionality recognizes the potential influence of a researcher's social position and identity on various aspects of their research. Positionality refers to an individual's worldview and the stance they take in relation to research and its context (Holmes, 2020). It encompasses beliefs about reality, knowledge, and values, which in turn influence the approach to research. These beliefs are shaped by personal experiences and various self-identifications, including national origin, geographic location, gender, ethnicity, disability status, social class, and other factors that contribute to the social position or location.
We express our positionality to provide the reader with a clear understanding of our background and identity. By being transparent, we aim to provide essential context for users of our research, acknowledging how our perspectives shape our approaches and outcomes. By offering a positionality statement, we strengthen our work through promoting transparency and reflexivity in our research.

Our team shares the scientifically backed and evidence-based perspective that we are living in a triple planetary crisis and that we want to help tackle it. All members have a tertiary education, and work within an interdisciplinary space. Collectively we combine a variety of disciplinary backgrounds, including ecology, computer science, philosophy and social sciences. Team members consist of a diversity of career stages (e.g. Professors, senior and early career scientists, PhD, and MSc). As a team we have diverse cultural backgrounds, but with a majority of team members of European descent.

Our research affiliations are mostly in the Northern hemisphere, with project instigators based in Germany and Canada. We also acknowledge that to some extent the development of our ideas and outcomes are influenced by funding opportunities.

Figures in construction

Our positionality has impacted our research, for example shaping our understanding of causality. Furthermore, the selection of problems to solve could be biased and not reflect different local issues. Similarly, the solutions proposed underestimate local contexts with a risk to be irrelevant for certain populations, communities and local situations. Moreover, our position comports the risk to overlook certain stakeholders that would have been relevant to frame certain solutions. Furthermore, within subgroups of the team there are underlying interests in advancing the respective disciplines, for example, philosophers have adopted a practice-oriented approach with an interest in the approach of “Philosophy in Science” where the results of the philosophical investigation should be relevant to science. While ecologists in the group have a focus on advancing theory, e.g. understanding ecological mechanisms, and how these relate to practical implementation. Together, we have a common goal of making knowledge more accessible. Finally, for now, we have considered mostly English-language scientific literature in our work, but continue to be in discussion on ways to also include other languages and resources.

To minimize the impact of these biases we have adopted a specific approach. We organized interactive workshops with a core group designing the workshop process and invited broad participation from researchers within the different disciplines and from various geographical and institutional locations. These workshops created a safe space of exchange where ideas and opinions from everyone were heard, valued and considered in the project development. This interactivity also led to a collection of envisioned end ‘users’ with heterogeneous profiles, expanding to practitioners from various fields. We intend to reach out to some of these persons/communities to invite them to contribute input for further development of our work, and generally welcome expressions of interest. Since the initiation of the tool being developed by our group, special attention has been given to collective benefit and responsibility, following core ideas of the CARE principles (e.g., see our approach to incorporating grey literature - tab in construction).

Topics

For developing EcoWeaver and TReK in accordance with the vision [link], it is essential to address questions that go beyond issues directly related to the technical implementation of the required software. The group focuses on three overlapping areas of research: (i) Understanding users and user needs, (ii) causal and mechanistic modeling, and (iii) information acquisition and integration.

Understanding users and user needs

Key objectives:

  • Tailoring the EcoWeaver and TReK to the needs of potential users
  • Exploring values and worldviews of potential users to guarantee implementations that are just and equitable

Research questions:

  • Which questions do potential users have?
  • Which answers do they expect?
  • What are the relevant user groups?

Approach:

  • The aim is to form Communities of practice, consisting of diverse teams of practitioners, scientists and local knowledge holders
  • Within these communities of practice, we will make efforts to
    • Deeply understand the needs and expertise of a genuinely diverse range of restoration practitioners (e.g. projects from very small to very large scales, different degrees of involvements from one-off to centuries long indigenous or other local maintenance of lands)
    • Engage community members in the co-development of the EcoWeaver and TReK to ensure their just and meaningful implementation

[Intersections with the other topics?]

Causal and mechanistic modeling

Key objectives:

  • Represent the available knowledge in the form of mechanistic and causal models
  • Collect and integrate existing mechanistic and causal models relevant for ecology and restoration

Research questions:

  • What are the best ways to represent causal knowledge for ecological research and restoration practice?

[Approach]

Intersection with other topics:

  • Understanding user groups and their differing epistemic needs is a prerequsite to ensure that models are fit for purpose.

Information acquisition and integration

Key objectives:

  • Identification of sources of knowledge relevant for ecological research and restoration practice
  • Turning unstructured into structured information that is machine actionable
  • Integrating information in ways that allow for user tailored knowledge synthesis and representation

Research questions:

  • Which types of information are relevant for ecological research and restoration practice?
  • How can technology help with making this information FAIR?
  • How can ecological evidence be synthesized despite context dependence?

[Approach]

Intersection with other topics

  • How could local and indigenous knowledge be integrated with scientific and Western knowledge?

Community guidelines for involvement

Collaboration

Given that the vision [link] is a very ambitious one, a single project could never be large enough to realize it. The idea is therefore to strive for a number of projects and individual activities all working in parallel towards this joint vision. The Venn diagram is meant as an overview, allowing localizing the diverse contributions within the overall effort.

We invite everyone interested in collaborative efforts towards the joint vision to take the initiative, and contribute with their own projects or activities.

[To be discussed: If you want to actively contribute, please ## [contact Tina Heger t.heger@tum.de ?? Join the github?]

  • Transparency
    • Please let others know about your paper projects and proposal ideas in the context of the EcoWeaver and TReK early on, by adding them in the github
    • This way, we can identify synergies and avoid situations of competition
  • Different publication practices across disciplines
    • When discussing co-authorship, author order etc. for joint publications, please take into account that publication practices differ amongst disciplines
    • Examples:
      • In Philosophy, single author papers are much more common than in ecology. Important positions on the paper are only the first ones; the last position has no meaning (other than in ecology)
      • In Computer Science, a quite common way to publish are conference papers. ###
  • Different needs across career stages
    • When discussing co-authorship, author order, proposal contributions etc., please take into account different needs across career stages
    • Early career researchers will probably usually be very happy to be included in paper projects – but please make sure to share the workload in a fair and transparent way
    • Ideally, establish mentoring relationships with your co-workers (peer mentoring, regular mentoring)
  • Avoid overcommitting
    • Before adding your name to a development project, paper project or proposal, please carefully consider your availability
    • The teams deserve a fair sharing of workload
    • Think about regular check-ins to avoid conflicts due to overcommitments
  • Communicate dependencies and act upon them
    • In cases where papers or proposals build on each other in some respect, make sure the dependencies are clearly communicated
  • Joint publications
    • We differentiate between open and closed papers
    • For open papers that are in the planning, everyone is invited to join the team that prepares the manuscript. Conditions for co-authorship should be specified in the description of the paper on github.
    • For closed papers, the first author builds a team (or writes the paper themselves). Some basic information should be provided on the github, to let others know that this is happening.
  • Joint proposals
    • For proposals, the leading PI builds a team (or writes the proposal themselves).
    • Here, transparency is essential, to avoid that two proposals from within our collaboration are competing with each other
    • Everyone involved in proposal writing should be aware of the risks (e.g. rejection rates). The workload should be shared in a transparent and fair manner.
    • If a proposal is funded, the leading PI is in full control of how the money is spent, but is asked to be very transparent about all decisions.
    • Ideally, open positions will be announced within the collaboration; there should be a regular and transparent application process

About

test

Resources

Stars

1 star

Watchers

1 watching

Forks

Releases

Packages

Contributors