Science for DRM 2020: Open call for authors/reviewers/advisors

Source(s): European Commission Joint Research Centre

The Disaster Risk Management Knowledge Centre (DRMKC) is starting to prepare the second Report in the "Science for Disaster Risk Management" flagship series, to be finalised by the end of 2020.

In order to ensure a participated, holistic and transparent selection process, the DRMKC has the pleasure to open this public Call for Expression of Interest from Authors, Reviewers and Advisors wishing to contribute to the Science for DRM 2020: acting today, protecting tomorrowReport.

Every interested contributor can apply either as:

  • Coordinating Lead Author,
  • Lead Author,
  • Contributing Author,
  • Reviewer,
  • Advisor,

By filling and submitting the 'Contributor template' before 20 February 2018. Each interested expert may apply for different categories across the various Chapters and Sub-chapter open in this Call, as long as different roles do not overlap on the same Chapter / Sub-chapter.

For more detailed information, the following guide documents are available for download on the side bar:

  • Terms of Reference, defining the Background, Expectations, Scope, Organizational Structure (including the roles and guidelines to be followed by each category of contributor) and the Assessment Criteria for selecting the contributors;
  • Table of Contents description, with a short overview of each Chapter and Sub-Chapter expected contents;
  • Table of Contents matrix, with a global overview of the proposed Index and expected contributors;
  • Workplan, with a draft calendar of key milestones towards the publication of the Report.

Attachments

Document links last validated on: 16 July 2021

Explore further

Country and region Algeria
Share this

Please note: Content is displayed as last posted by a PreventionWeb community member or editor. The views expressed therein are not necessarily those of UNDRR, PreventionWeb, or its sponsors. See our terms of use

Is this page useful?

Yes No
Report an issue on this page

Thank you. If you have 2 minutes, we would benefit from additional feedback (link opens in a new window).