> For the complete documentation index, see [llms.txt](https://coalitions-trp-survey.cwts.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coalitions-trp-survey.cwts.nl/survey/efficiency-of-peer-review-and-effort-recognition.md).

# Efficiency of peer review and effort recognition

The following questions apply only to those respondents who have performed peer review in the past three years

### Question 23

#### Do you feel that the amount of peer review requests you receive is

{% embed url="<https://public.tableau.com/views/cOAlitionSSurvey-Peerreviewrequests/Dashboard1320?:display_count=n&:language=en-GB&:origin=viz_share_link&:sid=&publish=yes>" %}

***

### Question 24

#### Do you feel the current researcher recognition and reward mechanisms motivate you to undertake peer review?

{% embed url="<https://public.tableau.com/views/cOAlitionSSurvey-Peerreviewrecognition/Dashboard1322?:display_count=n&:language=en-GB&:origin=viz_share_link&:sid=&publish=yes>" %}

***

### Question 25

#### To what extent would the following practices encourage you to participate more actively in peer review?

{% embed url="<https://public.tableau.com/views/cOAlitionSSurvey-Peerreviewmotivation/Dashboard1323?:display_count=n&:language=en-GB&:origin=viz_share_link&:sid=&publish=yes>" %}

***

### Question 26

#### Publishing peer review reports may help to improve the efficiency of peer review. For example, if a journal rejects an article that is then submitted to a different journal, the latter journal may reuse (parts of) the previous review reports in its decision-making, thereby reducing the need to find new reviewers. As a reviewer, would you support the publication of your peer review reports?

{% embed url="<https://public.tableau.com/views/cOAlitionSSurvey-Openingpeerreview/Dashboard1324?:display_count=n&:language=en-GB&:origin=viz_share_link&:sid=&publish=yes>" %}


---

# 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://coalitions-trp-survey.cwts.nl/survey/efficiency-of-peer-review-and-effort-recognition.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.