<?xml version="1.0" encoding="UTF-8"?>
<modsCollection xmlns="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd">
  <mods>
    <titleInfo>
      <title>Policy brief as a knowledge transfer tool : to "make a splash", your policy brief must first be read</title>
    </titleInfo>
    <name type="personnal">
      <namePart type="family">Dagenais</namePart>
      <namePart type="given">C.</namePart>
      <role>
        <roleTerm type="text">auteur</roleTerm>
        <roleTerm type="code" authority="marcrelator">aut</roleTerm>
      </role>
      <affiliation>IRD</affiliation>
    </name>
    <name type="personnal">
      <namePart type="family">Ridde</namePart>
      <namePart type="given">Valéry</namePart>
      <role>
        <roleTerm type="text">auteur</roleTerm>
        <roleTerm type="code" authority="marcrelator">aut</roleTerm>
      </role>
      <affiliation>IRD</affiliation>
    </name>
    <typeOfResource>text</typeOfResource>
    <genre authority="local">journalArticle</genre>
    <language>
      <languageTerm type="code" authority="iso639-2b">eng</languageTerm>
    </language>
    <physicalDescription>
      <internetMediaType>text/pdf</internetMediaType>
      <digitalOrigin>reformatted digital</digitalOrigin>
      <reformattingQuality>access</reformattingQuality>
    </physicalDescription>
    <abstract>Since 2010, the research teams that we work with have produced dozens of policy briefs (PB) with the purpose of informing the various stakeholders of the results of our studies and their usefulness regarding public health practices, decision-making and policy change. Because they are only aids to decision-making, "A policy brief is just a piece of paper, it doesn't DO anything on its own", preparing these PBs should always form part of a broader knowledge transfer process. Therefore, they often serve as discussion tools during deliberative workshops focusing on the manner in which the results could be incorporated into practices and public policies. Based on these experiences, we have developed a guide for preparing policy briefs, which we have used with researchers over and over again in our training workshops. This training was offered in different formats lasting from three hours to two days. In this editorial, we use our different experiences to put forward a PB format intended for a non-scientific audience, to act as an influence on practices and policy-making.</abstract>
    <targetAudience authority="marctarget">specialized</targetAudience>
    <classification authority="local">056</classification>
    <classification authority="local">116</classification>
    <relatedItem type="host">
      <titleInfo>
        <title>Gaceta Sanitaria</title>
      </titleInfo>
      <part>
        <detail type="volume">
          <number>32</number>
        </detail>
        <detail type="volume">
          <number>3</number>
        </detail>
        <extent unit="pages">
          <list>203-205</list>
        </extent>
      </part>
      <originInfo>
        <dateIssued>2018</dateIssued>
      </originInfo>
      <identifier type="issn">0213-9111</identifier>
    </relatedItem>
    <identifier type="uri">https://www.documentation.ird.fr/hor/fdi:010072292</identifier>
    <identifier type="doi">10.1016/j.gaceta.2018.02.003</identifier>
    <identifier type="issn">0213-9111</identifier>
    <location>
      <shelfLocator>[F B010072292]</shelfLocator>
      <url usage="primary display" access="object in context">https://www.documentation.ird.fr/hor/fdi:010072292</url>
      <url access="row object">https://horizon.documentation.ird.fr/exl-doc/pleins_textes/divers19-02/010072292.pdf</url>
    </location>
    <recordInfo>
      <recordContentSource>IRD - Base Horizon / Pleins textes</recordContentSource>
      <recordCreationDate encoding="w3cdtf">2018-05-15</recordCreationDate>
      <recordChangeDate encoding="w3cdtf">2023-07-11</recordChangeDate>
      <recordIdentifier>fdi:010072292</recordIdentifier>
      <languageOfCataloging>
        <languageTerm authority="iso639-2b">fre</languageTerm>
      </languageOfCataloging>
    </recordInfo>
  </mods>
</modsCollection>
