<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//TaxonX//DTD Taxonomic Treatment Publishing DTD v0 20100105//EN" "../../nlm/tax-treatment-NS0.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tp="http://www.plazi.org/taxpub" article-type="research-article">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">17</journal-id>
      <journal-id journal-id-type="index">urn:lsid:arphahub.com:pub:8E638694-B4E0-570A-856A-746FF325BF6B</journal-id>
      <journal-title-group>
        <journal-title xml:lang="en">Research Ideas and Outcomes</journal-title>
        <abbrev-journal-title xml:lang="en">RIO</abbrev-journal-title>
      </journal-title-group>
      <issn pub-type="epub">2367-7163</issn>
      <publisher>
        <publisher-name>Pensoft Publishers</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.3897/rio.3.e15133</article-id>
      <article-id pub-id-type="publisher-id">15133</article-id>
      <article-id pub-id-type="manuscript">6953</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Data Management Plan</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Data Management Plan: HarassMap</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Wael</surname>
            <given-names>Reem</given-names>
          </name>
          <email xlink:type="simple">reem.wael@harassmap.org</email>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">Harassmap, Cairo, Egypt</addr-line>
        <institution>Harassmap</institution>
        <addr-line content-type="city">Cairo</addr-line>
        <country>Egypt</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Reem Wael (<email xlink:type="simple">reem.wael@harassmap.org</email>).</p>
        </fn>
        <fn fn-type="edited-by">
          <p>Academic editor: </p>
        </fn>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2017</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>18</day>
        <month>07</month>
        <year>2017</year>
      </pub-date>
      <volume>3</volume>
      <elocation-id>e15133</elocation-id>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/E53FADEF-3FAB-5A47-B97C-6AA672CACCB3">E53FADEF-3FAB-5A47-B97C-6AA672CACCB3</uri>
      <uri content-type="zenodo_dep_id" xlink:href="https://zenodo.org/record/1139838">1139838</uri>
      <history>
        <date date-type="received">
          <day>18</day>
          <month>07</month>
          <year>2017</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>Reem Wael</copyright-statement>
        <license license-type="creative-commons-attribution" xlink:href="http://creativecommons.org/licenses/by/4.0" xlink:type="simple">
          <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution License 4.0 (CC-BY), which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.</license-p>
        </license>
      </permissions>
      <abstract>
        <label>Abstract</label>
        <p>HarassMap is an Egyptian organisation that works to create an environment where sexual harassment is not tolerated, and where individuals and institutions take action against it. For the purpose of this project, the project team cleaned up, organised, and made openly available for the public to access and use through a web portal, three main types of data:</p>
        <p>
          <list list-type="bullet"><list-item><p>Crowdsourced reports of sexual harassment incidents (reports on HarassMap’s online reporting and mapping system) - CSV and XLS</p></list-item><list-item><p>Field data from HarassMap’s research on sexual harassment using traditional qualitative and quantitative research methods - DOCX, PDF, SAV, MP3</p></list-item><list-item><p>Social media conversations (comment threads and messages related to sexual harassment on harassMap’s Facebook page) - XLS</p></list-item></list>
        </p>
        <p>The social media data was collected retrospectively from our Facebook page during the project period and covers the period 2010-2016. The crowdsourced data and the research data was cleaned and organised to make sure it is usable for the public but still kept in its raw format. During the collection and organisation period, we also made sure to clear out all personal identifiers from the data to ensure anonymity and confidentiality, and prepared descriptions of each dataset that will help the public understand how the data was collected and how it can and cannot be used.</p>
        <p>The data is stored online on a web portal that we built together with a web developer during the project period. On the web portal, the data is available for the public to view, search and download for research or other purposes. The data is also backed up on a hard drive and the cloud. The web portal and HarassMap open data will be advertised on our website, and the direct link shared with our contacts and others who approach us with interest in our data.</p>
      </abstract>
      <kwd-group>
        <label>Keywords</label>
        <kwd>data management plan</kwd>
        <kwd>sexual harassment</kwd>
        <kwd>Egypt</kwd>
        <kwd>crowd sourcing</kwd>
        <kwd>dmp</kwd>
        <kwd>research data management</kwd>
      </kwd-group>
      <funding-group>
        <award-group>
          <funding-source>
            <named-content content-type="funder_name">International Development Research Centre</named-content>
            <named-content content-type="funder_identifier">501100000193</named-content>
            <named-content content-type="funder_doi">http://doi.org/10.13039/501100000193</named-content>
          </funding-source>
        </award-group>
      </funding-group>
      <counts>
        <fig-count count="0"/>
        <table-count count="0"/>
        <ref-count count="0"/>
      </counts>
    </article-meta>
  </front>
  <body>
    <sec sec-type="">
      <title>Data Collection</title>
      <sec sec-type="What types of data will you collect, create, link to, acquire and/or record?">
        <title>What types of data will you collect, create, link to, acquire and/or record?</title>
        <p>We collect different types of data. We will record numeric, audio, PDF, and text, images.  The data includes crowdsourced reports that we receive online, reports, comments and messages that we receive on social media, and field data from research projects (interview transcripts, for example).</p>
      </sec>
      <sec sec-type="What file formats will your data be collected in? Will these formats allow for data re-use, sharing and long-term access to the data?">
        <title>What file formats will your data be collected in? Will these formats allow for data re-use, sharing and long-term access to the data?</title>
        <p>The data will be in different formats, such as XLS, docx, PDF/A, sav, and MP3. These formats are easy to re-use as long as researchers are able to work with the software. In addition, the data will be available and accessible to the user.</p>
      </sec>
      <sec sec-type="What conventions and procedures will you use to structure, name and version-control your files to help you and others better understand how your data are organized?">
        <title>What conventions and procedures will you use to structure, name and version-control your files to help you and others better understand how your data are organized?</title>
        <p>At the beginning, we will add the final version for any type of the data, and there will be three other copies of the data, with one copy stored off site (external hard disk), with an access to certain staff members. In addition, the data will be grouped based on the nature of data as follows:</p>
        <list list-type="bullet">
          <list-item>
            <p>The data that will be collected from the field, the file’s name will include “Field data”, with indication for type whether this data is questionnaire or guideline, audio, report, stories, or interview transcription.</p>
          </list-item>
          <list-item>
            <p>The data that will be collected from our online reporting system, the file’s name will include “Map reports”.</p>
          </list-item>
          <list-item>
            <p>The data that will be collected from our social media platform, the file’s name will include “socialmedia_ FB” for data from Facebook, and “socialmedia_ TW” for data from twitter.  Data from Facebook and Twitter will be structured according to date.</p>
          </list-item>
        </list>
        <p>There will also be text descriptions with information about how each dataset is organised.</p>
      </sec>
    </sec>
    <sec sec-type="">
      <title>Documentation and Metadata</title>
      <sec sec-type="What documentation will be needed for the data to be read and interpreted correctly in the future?">
        <title>What documentation will be needed for the data to be read and interpreted correctly in the future?</title>
        <p>There are different types of data, some needs documentation to make the data usable by other researchers and other do not need documentation because it is understood from the title.  For the data that required documentation such as field data about sexual harassment, the documentation must include: research methodology used, sample size, variable definitions, assumptions made, format and file type of the data, a description of the data capture and collection methods, explanation of data coding and analysis performed (including syntax files- if available).</p>
        <p>The crowdsourced data will also require explanation of how the data was collected and how it can and cannot be used.</p>
      </sec>
      <sec sec-type="How will you make sure that documentation is created or captured consistently throughout your project?">
        <title>How will you make sure that documentation is created or captured consistently throughout your project?</title>
        <p>HarassMap will start collecting data retrospectively. For the last five years we have been recieving data but not collecting. For the purpose of this project we will start from collecting the incoming data and at time we will document data collected in the past, moving chronologically. The purpose is to document as much data as we can in the next 6 months – the duration of the project. To make sure that the documentation is created or captured consistently, HarassMap will use part of the funds allocated through this project to recruit 2-3 interns to work on collecting/cleaning data in the data collection phase. They will work closely with HarassMap unit staff from which the data will be collected.</p>
      </sec>
      <sec sec-type="If you are using a metadata standard and/or tools to document and describe your data, please list here.">
        <title>If you are using a metadata standard and/or tools to document and describe your data, please list here.</title>
        <p>Currently we are not using any.</p>
      </sec>
    </sec>
    <sec sec-type="">
      <title>Storage and Backup</title>
      <sec sec-type="What are the anticipated storage requirements for your project, in terms of storage space (in megabytes, gigabytes, terabytes, etc.) and the length of time you will be storing it?">
        <title>What are the anticipated storage requirements for your project, in terms of storage space (in megabytes, gigabytes, terabytes, etc.) and the length of time you will be storing it?</title>
        <p>We will store the data on a server with the purpose of long-term storage (years).  The exact details on cost and space will be determined once we hire a develop on a consultancy basis for this project. </p>
      </sec>
      <sec sec-type="How and where will your data be stored and backed up during your research project?">
        <title>How and where will your data be stored and backed up during your research project?</title>
        <p>The data will be saved on the server, external hard disks and internet cloud . HarassMap does not have a technology expert on-board. Therefore we will use funds available from this grant to hire a consultant who can help us set this system up and maintain it for the duration of the project. After the end of the project, we will allocate the maintenance fee from another grant as soon as possible. </p>
      </sec>
      <sec sec-type="How will the research team and other collaborators access, modify, and contribute data throughout the project?">
        <title>How will the research team and other collaborators access, modify, and contribute data throughout the project?</title>
        <p>Each team and collaborators can access it through internet and web application. Each team will have permission to edit the relevant parts .</p>
      </sec>
    </sec>
    <sec sec-type="">
      <title>Preservation</title>
      <sec sec-type="Where will you deposit your data for long-term preservation and access at the end of your research project?">
        <title>Where will you deposit your data for long-term preservation and access at the end of your research project?</title>
        <p>It will be saved on the server and available to the public on the open database/platform (which will be kept online and running as long as we have funds for it).</p>
      </sec>
      <sec sec-type="Indicate how you will ensure your data is preservation ready. Consider preservation- friendly file formats, ensuring file integrity, anonymization and de-identification, inclusion of supporting documentation.">
        <title>Indicate how you will ensure your data is preservation ready. Consider preservation- friendly file formats, ensuring file integrity, anonymization and de-identification, inclusion of supporting documentation.</title>
        <p>Each project file will be stored on the server on its format and will be linked to its data in the database using some programming algorithms this will store the data on the server as long as we have the server .</p>
        <p>We will use the application to manage accounts - each team/section manager can manage his team members remove, update, modify, and create.</p>
      </sec>
    </sec>
    <sec sec-type="">
      <title>Sharing and Re-use</title>
      <sec sec-type="What data will you be sharing and in what form? (e.g. raw, processed, analyzed, final).">
        <title>What data will you be sharing and in what form? (e.g. raw, processed, analyzed, final).</title>
        <p>We will primarily share raw data that we collected from a research study that we conducted 2011-2013, crowdsourced map reports, and from social media.</p>
      </sec>
      <sec sec-type="Have you considered what type of end-user license to include with your data?">
        <title>Have you considered what type of end-user license to include with your data?</title>
        <p>HarassMap has a default copy right policy: <ext-link ext-link-type="uri" xlink:href="http://harassmap.org/en/copyright/ Creative Commons">http://harassmap.org/en/copyright/ Creative Commons</ext-link></p>
        <p>
          <ext-link ext-link-type="uri" xlink:href="http://opendefinition.org/od/2.1/en/">http://opendefinition.org/od/2.1/en/</ext-link>
        </p>
      </sec>
      <sec sec-type="What steps will be taken to help the research community know that your data exists?">
        <title>What steps will be taken to help the research community know that your data exists?</title>
        <p>HarassMap will announce this on our website, but we will also keep a permanent icon on the website indicating to users that they can have access to our data. Without announcing it, HarassMap already gets a lot of requests form researchers about sexual harassment.</p>
        <p>We will also utilize our contacts with academics in Egypt, UK, and the US to ensure that they  know about our open data.</p>
      </sec>
    </sec>
    <sec sec-type="">
      <title>Responsibilities and Resources</title>
      <sec sec-type="Identify who will be responsible for managing this project's data during and after the project and the major data management tasks for which they will be responsible.">
        <title>Identify who will be responsible for managing this project's data during and after the project and the major data management tasks for which they will be responsible.</title>
        <p>Four HarassMap staff members are involved in this project: Director, Marketing and Communications Unit Head, researcher and Admin and HR Manager. Additionally we will use the project budget to offer paid internships to collect some data and to hire a developer as a consultant.</p>
      </sec>
      <sec sec-type="How will responsibilities for managing data activities be handled if substantive changes happen in the personnel overseeing the project's data, including a change of Principal Investigator?">
        <title>How will responsibilities for managing data activities be handled if substantive changes happen in the personnel overseeing the project's data, including a change of Principal Investigator?</title>
        <p>HarassMap has three different staff members to oversee the project and therefore the absence of any of them will not affect the implementation of the project.</p>
      </sec>
      <sec sec-type="What resources will you require to implement your data management plan? What do you estimate the overall cost for data management to be?">
        <title>What resources will you require to implement your data management plan? What do you estimate the overall cost for data management to be?</title>
        <p>Person to collect data from social media: 9000 EGP for interns to document and clean information</p>
        <p>Developer: $2590</p>
        <p>Database upkeep (hosting): Will be determined by the end of June 2017.</p>
      </sec>
    </sec>
    <sec sec-type="">
      <title>Ethics and Legal Compliance</title>
      <sec sec-type="If your research project includes sensitive data, how will you ensure that it is securely managed and accessible only to approved members of the project?">
        <title>If your research project includes sensitive data, how will you ensure that it is securely managed and accessible only to approved members of the project?</title>
        <p>The database backend will be accessible only with a user name and password. The data that is accessible for the public, will be checked to ensure anonymity and confidentiality.</p>
        <p>Our data is not generally sensitive but sometimes we get reports with names or numbers and in these cases we only publish the reports after we remove this information. The ‘sensitive’ information will not be available to the public.</p>
        <p>We also are not able to share any information that would put HarassMap staff at risk such as reports that defame a person or a place that can file a defamation claim against HarassMap.</p>
      </sec>
      <sec sec-type="How will you manage legal, ethical, and intellectual property issues?">
        <title>How will you manage legal, ethical, and intellectual property issues?</title>
        <p>We will prepare an agreement for intellectual property rights that researcher will have to agree to before they have access to the data.</p>
      </sec>
    </sec>
  </body>
</article>
