> For the complete documentation index, see [llms.txt](https://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/~/changes/536/policies-projects-evaluation-workflow/communicating-results.md).

# Communicating results

## Curating and publishing evaluations, linked to research

* [Unjournal PubPub page](https://unjournal.pubpub.org/)
  * Previous/less emphasized: Society[ Group: curating evaluations and papers](https://sciety.org/groups/the-unjournal/about)
* Evaluations and author response are given DOI's, enter the bibliometric record
  * Future consideration: 
    * "publication tier" of authors' responses as a workaround to encode aggregated evaluation
    * Hypothes.is annotation of hosted and linked papers and projects (aiming to integrate: see: [hypothes.is for collab. annotation](/the-unjournal-project-and-communication-space/~/changes/536/tech-tools-and-resources/other-tech-and-tools/hypothes.is-for-collab.-annotation.md))
* Sharing evaluation data on public Github repo (see [data reporting here](https://unjournal.github.io/unjournaldata/))

## Aggregating evaluators' ratings and predictions

We aim to elicit the experiment judgment from *Unjournal* evaluators efficiently and precisely. We aim to communicate this quantitative information concisely and usefully, in ways that will inform policymakers, philanthropists, and future researchers.

In the short run (in our pilot phase), we will attempt to present simple but reasonable aggregations, such as simple averages of midpoints and confidence-interval bounds. However, going forward, we are consulting and incorporating the burgeoning academic literature on "aggregating expert opinion." (See, e.g., [Hemming et al, 2017](https://besjournals.onlinelibrary.wiley.com/doi/10.1111/2041-210X.12857); [Hanea et al, 2021](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8412308/); [McAndrew et al, 2020](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7996321/); [Marcoci et al, 2022](https://bmcresnotes.biomedcentral.com/articles/10.1186/s13104-022-06016-0).)

*We are working on this in our public data presentation (Quarto notebook)* [*here*](https://unjournal.github.io/unjournaldata/)*.*

## Other communication

We are considering...

* Syntheses of evaluations and author feedback
* Input to prediction markets, replication projects, etc.
* Less technical summaries and policy-relevant summaries, e.g., for the [EA Forum](https://forum.effectivealtruism.org/), [Asterisk magazine](https://asteriskmag.com/), or mainstream long-form outlets


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/~/changes/536/policies-projects-evaluation-workflow/communicating-results.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.