# data[].attributes.body
It's key that we kick off the workshop with a focus on evidence-users and the real-world impacts we are working towards, to ensure this is the centre of our delivery (and not just our design). This could be a precursor to the Alive model and living partnerships sessions.

# data[].attributes.custom_properties.eJY4MNSA
Everyone - suggest this is a plenary session if possible

# data[].attributes.body
A blue sky / whiteboard session where we consider what we need to do next to optimise the repository for finding studies for specific reviews / maps (esp. those in living mode). Solutions may include developing an embeddings model / retrieving a proportion (or all?) full texts / developing a hybrid keyword / vector search.

# data[].attributes.body
The repository has been designed to support multiple projects / downstream applications. We need to develop a strategy for considering when it's ready for additional use cases and how they should be supported / admitted etc

# data[].attributes.body
I am not sure how but we need to be accountable to each other and have some honest conversations about the work that each organization needs to deliver for the success of the collaboration

# data[].attributes.body
Focus for the next few months: developing methods & tools for extracting data from PDF files (and other formats where needed). Description of task; discussion about what's needed; discussion about how to obtain the right datasets to develop the tools.

# data[].attributes.body
What do we need to do to move from the map we have to impact case study 1?

# data[].attributes.body
Presentation of the scope of the demonstrator and its architecture. Then invite discussion around how we obtain feedback on: 1) scope; 2) taxonomy; 3) functionality; 4) UI

# data[].attributes.body
As a means of communicating evidence - defining a blueprint application in DESTINY

# data[].attributes.headline
Building a living evaluation infrastructure

# data[].attributes.subject
Building a living evaluation infrastructure

# data[].attributes.body
we need further work on what is a gold standard DEST evaluation and what is a gold standard DEST evaluation dataset

# data[].attributes.body
Reviewing progress and planning ahead

# data[].attributes.body
Finding suitable evidence when it is locally scare

# data[].attributes.headline
Taxonomy / definitions / boundaries / vocabulary management

# data[].attributes.subject
Taxonomy / definitions / boundaries / vocabulary management

# data[].attributes.body
expanding the methods toolkit for climate & health

# data[].attributes.body
Building an evidence map for climate & health in cities and human settlements

# data[].attributes.headline
Impact case dissemination and publication plans

# data[].attributes.subject
Impact case dissemination and publication plans

# data[].attributes.body
Discuss and confirm where and how we plan to publish and disseminate the different impact cases (protocols, reviews, etc.)

# data[].attributes.custom_properties.eJY4MNSA
WP4, WP5 (with online attendance from Toby Lasserson and Vivian Welch).

# data[].attributes.body
To include what are the expectations and timelines for mainstreaming ICs, what are the synergies and dependencies across the WPs, what overlap is there with CoP, and start developing plans for Impact Case 1.

# data[].attributes.body
Following the evaluation framework, we need to map out the tasks for the following year and get commitments w.r.t. human resources. At the moment WP3 is just a side-quest for most.

# data[].attributes.body
Review results from survey on expectations of accuracy requirements when automating evidence synthesis

# data[].attributes.body
What is the purpose of WP3? Is it just a facilitator between WP2 and others? Starting from the current evaluation framework, we need to define a clear scope of this workpackage and a shared understanding

# data[].attributes.custom_properties.eJY4MNSA
People that can make decisions from each work package with real-world experience

# data[].attributes.body
The human–repository interface is where we are currently lacking a lot of focus. We need to find the low-hanging fruit to improve basic capabilities like query development and searching. Doing so, we need to make sure to not get distracted with shiny features that don't actually speed up or otherwise improve work-flows. What are the big wins we can focus on next? We should not get distracted chasing LLMs—at the end of the day we need to present the data to humans?

# data[].attributes.custom_properties.eJY4MNSA
WP4 input as users/curators of evidence; WP1 to clarify how we can get decision-maker needs; WP5 for community feedback; WP2 to listen in

# data[].attributes.body
We need a good strategy to share and collect data within and beyond the consortium. What data do we need? We need to define clear formats and requirements so that we can efficiently collect and archive relevant data

# data[].attributes.headline
Evaluation across WPs - doesn't necessarily belong here / doesn't need to be led by WP1

# data[].attributes.subject
Evaluation across WPs - doesn't necessarily belong here / doesn't need to be led by WP1

# data[].attributes.body
Coordinate our evaluation efforts to avoid duplication, ensure we are all aligned and coordinated, especially in data/information gathering across WPs and from those in the communities of pratices (the users)

# data[].attributes.body
Planning, topic, interest holders mapping, timelines

# data[].attributes.headline
Engagement plans for CoPs (communities of practice)

# data[].attributes.subject
Engagement plans for CoPs (communities of practice)

# data[].attributes.body
How do we work with the interest holders: first steps to input into the DEST, what considerations to make it living, how to support over time, what does the comms, asks and meetings schedule look like

# data[].attributes.custom_properties.eJY4MNSA
WP4, WP2 and WP3 (Tim?) - link to session 2 below in WP3 (interface evaluation)

# data[].attributes.body
Brief overview of what living means and implications, key elements to include in the protocols, and how we work with interest holders throughout the span of the project

# data[].attributes.body
Brief overview of the Alive approach, implications for how we work with WP4 across all impact cases, ways of working, engagement of interest holders