CoronaNet Research Project Manual

Training Videos

---

• Assessing, Planning, Coding and Cleaning Training, October 1: This is the additional training video which all RAs must watch before starting on the CoronaNet Research Project which goes over how to assess, plan, code and clean policies.(Password 6Yk+^cKK).
• CoronaNet Onboarding Video, 25 January: This is the main training video which all RAs must watch before starting on the CoronaNet Research Project.
• How to do updates: This training video shows RAs how to enter an update and how to end a policy.
• CoronaNet Background Video: This video outlines the process of registering RAs, data collection, advantages of qualtrics, data validation, reliability, cleaning, difference between beta and final dataset (15:00h).
• Data Integration Guide: This video shows what data integration is and how external data is to be integrated into the CoronaNet database.

Weekly Meetings

---

• CoronaNet General RA Meeting: In the general RA meeting that we have every Wednesday at 4:30pm CET and Thursday at 10am CET, the PIs share updates about the progress of the project. Recordings of older meetings can be found at the end of this section. Once a month, we use this time to host a town hall where people can ask questions, make suggestions, or express concerns both directly or anonymously through this survey form.
• Task Force Meetings: RAs should also have a regular weekly meeting with their Task Force manager. The relevant link for that meeting should be provided by the appropriate Task Force manager.

Project Goals

---

This project has always had to deal with uncertainty given that we are collecting data in real time and we thus cannot know ahead of time how long the pandemic will last and how governments will react to it. Having project-wide goals helps us coordinate and make sure that despite the uncertainty, we are doing our best to collect data for all over the world for the same time periods and ensure high quality in our data collection efforts. Having complete and clean data for many countries over the same time period is crucial to say anything about what the drivers and effects of COVID-19 government policies are.

The overall CoronaNet Project Goals are to ensure complete and clean data for all countries.

In order to assess progress toward the CoronaNet Project Goals. It is necessary to conduct data assessments on a regular basis. These assessments are done using the version of the data in the Shiny App along the following criteria:

• Goals and Activity
  • Current Goals
  • Current Activity
  • Most Recent Activity
• Volume of Data
  • Number of policies coded in total
  • Number of policies coded by quarter
• Data Completeness
  • RA Internal Assessment: Approximate date the data is coded until
  • RA Internal Assessment: Policy Completeness
  • Amount of external data to integrate
• Data Quality
  • Policy Cleanness
  • Number of missing end dates
• Data Complexity
  • RA Internal Assessment: Policy Complexity
  • RA Internal Assessment: Subnational Policy Making

Surveys

---

• Test Survey: This is the link to the test survey that each RA must pass with at least 70% accuracy in order to join the project. After passing the test, RAs should feel free to take the test survey as many times as they would like in order to learn more about how to use the main survey.
• Main Qualtrics Survey: The main Qualtrics survey is the main tool by which RAs collect data on government policies for the CoronaNet project. Note that there is no general link for the main Qualtrics survey. Everyone has an individualized survey link that is emailed to you.
• RA Internal Assessment Survey: We know that RAs are the backbone of the project. The aim of this RA Internal Assessment Survey is to gauge how you view your time at CoronaNet and will also help us identify and assess changes in countries and regions. Remember, there are no right or wrong answers, this survey will help us to see your point of view, so we would like it if you are as honest as possible when answering. This survey should take around 15-20 minutes. If you code for multiple regions, please take a separate survey for each region that you code.

Correcting or Updating the Main Survey

---

RAs can correct or update the main survey using:

• The Shiny App: This app allows RAs to visualize policies. It also provides links to update or correct the survey for each unique record. Please see the section of this manual on the Shiny App for more information on how to use it.

Coding Resources

---

• CoronaNet Coding Guide: The coding guide provides links to videos and slides which explain how to categorize and systematically capture policies.
• CoronaNet Data Codebook: This codebook explains what dimensions of a given policy different questions/variables in the main survey seek to capture.
  
• CoronaNet Printed Survey: The printed survey provides an overview of the questions and answers available in the Qualtrics survey in a scrollable/searchable format
• CoronaNet Taxonomy: This taxonomy table provides a way to visualize how different policy types and subtypes relate to each other
• CoronaNet Skeleton: The CoronaNet Skeleton provides an overview of how the data is structured
• #ra-chat: This Slack channel is the main place where RAs should post questions about how to code different policies.
• The **CoronaNet Automated Data Quality Check Sheet provides feedback on what specific policies likely have errors in them
• The FAQ tab in the Shiny App. The FAQ tab summarizes and organizes common questions asked in the #ra-chat channel.

Organizational Tools

---

• CoronaNet Project Research Assistant Dashboard: Here you can find all the tools, guides and resources you might need while you’re working with CoronaNet.
• RA Allocation Sheet: Information on which RAs are allocated to which countries are available in this sheet. Available through Project Management.
• Validation sheet: RAs on the validation team should assign themselves a record to validate using this sheet.

Other

---

Instructions for Country Reports and Research Notes : Instructions on how RAs should write country reports or research notes are available at this link.

What is data collection and entry?

Data collection and entry forms the foundation on which the rest of the project is built. The ultimate goal of the project is to produce an accurate and complete record of all policies governments have taken in response to COVID-19. This entails 1) identifying relevant policies that governments have taken in response to COVID-19 2) documenting them in a standardized format.

What should I do before starting with data collection and entry?

Before entering in data, you should:

1. Watch the required general RA onboarding video before starting to collect the data.
2. Watch the required training on zoom on how to do updates to the data.
3. Read through the Variable Definitions in the codebook and the corresponding examples provided below.
4. Look through the RA FAQs in the Shiny App for commonly asked questions.

The value of this data is only as good as its quality so please be sure to take your time with documenting these policies, and pose your questions to the Slack Channel or the PIs if in doubt!

How do I actually do data collection and entry?

What counts as a ‘policy’?

These policies can be thought as being in one of two categories:

1. A new policy
2. An updated policy

A new policy is a policy in a category that the government has not addressed before, such as the imposition of a quarantine on the country. An updated policy is a policy change in which the details of the policy change, but not whom the policy is targeted at. For example, if Germany announces a quarantine for one province, and then later extends the quarantine for two weeks, that would count as an update. But if Germany announces a quarantine covering the whole country, that would count as a new policy. The same logic goes for travel bans – making travel bans cover more countries/areas counts as new policies. Changing the way existing travel bans are enforced would be an update. For more information, please reference the codebook below. Please watch the required training on zoom on how to do updates to the data for more information and refer to the accompanying slides.

If in doubt, ask on the #ra-chat Slack channel!

In the Qualtrics survey, you must select either new or updated. To update a policy, find the previous record either:

1. The Record Look up sheet or
2. The Shiny Web Application

Moving forward, we would want you to use the web application as it contains the same data as the Record Lookup sheet, but in a format that is easier to visualize. Also, you can do some corrections in the app itself.

To update, click on the ‘update’ link that is on the left-hand side of the table/google sheet. See pictures:

How do I document a ‘policy’?

The below gives a textual overview of how to document a policy. Please refer to the required general training on Zoom for more information.

Use the following checklist:

1. For each country, check the data sources, in the order given below in the “Data Sources” section, for relevant information on government policy toward combating the coronavirus.

2. Enter the relevant information into your country specific dataset. It should always be possible to answer the following request/questions for a particular policy:

   • What type of entry is this? (e.g. new, correction, update)
   • Description of the government policy.
   • What is the policy category? (e.g. travel ban)
   • From what level of government does this policy originate from?
   • What kind of enforcement does this policy have (if any)?
   • Which organizations or entities are in charge of enforcing a policy?
   • When was the policy announced?
   • What information sources did you use to identify this policy?

   
   Some, but not all policies,[^1] will also require you to identify:

   • Which geographical entity is the target of this policy?
   • What or whom is the policy targeted toward?
   • Is this policy inbound, outbound or both?
   • What kind of transportation is this policy targeted toward?

   When it is not possible to collect this information, please note the reason for the difficulty at the end of the survey.

   Please document each source by answering the according survey question. Currently, the dataset allows you to code up to 10 sources. Note also that it is possible that you will need more than one source to collect all the information for each event.

3. Save a .pdf for each data source that you use. As the file name, use the following format: [Date Collected]_[Title of article].pdf where the [Date Collected] should follow the format MM-DD-YYYY.

4. You can upload the file within the Qualtrics survey (be sure to choose the correct country).

How do I find a policy?

The rest of this document tells you how to go about finding policies. Of course you can just use your own knowledge and Google, but we have some great resources we’ve identified below you should use to get started.

1. We have a list of policies that are coded in other sources external to the project. This external data should be seen as an additional source of information that we hope will make it easier and faster for RAs to identify policies to document for their country or subnational region. You can check the list of these policies in the CoronaNet Data Integration Sheet. In the section titled “Data Integration” later in this document the entire Data Integration process will be explained in detail.

---

2. We now have a source of news articles possibly related to the coronavirus by country compiled by the data science company Starsift. Please see this link for a list of news articles (articles that are more likely to contain a policy are marked in the “policy” column, though all of the articles could contain some information. Once you’ve worked through that dataset, you should do some searching on your own. Of course Google/Google News is a good asset, but there are other available sources:

---

3. Check the U.S. Embassy website for your country.

---

4. Check Wikipedia for your country’s response to the corona pandemic

---

5. Check Government websites for your country

---

6. Check Newspaper coverage on the coronavirus in your country

---

7. Other resources

We will update this section accordingly as more information becomes available. For now, some other resources you might consider include:

• Check Facebook and Twitter accounts for political leaders in the country (or for health ministries).
• This is a crowd-sourced list of government actions against the coronavirus by the Open Government Partnership (OGP). Note please be sure to vet the sources here carefully as the OGP themselves do not control for the quality of the entries made here.
• This website is a crowd-sourced compendium of information about the coronavirus. For now these appear to deal largely with the health outcomes associated with coronavirus but may be useful insofar as includes many links to in-country websites.

What to do if I need to delete an entry?

Please post the entry that you need to be deleted in the Policy Delition sheet and provide a reason for why the entry needs to be deleted.

With regards to incomplete records, please note:

• We DO include in the dataset records for which the RA filled everything out except they didn’t hit the final submit button; all other records are not included.
• If, however, you are seeing a record in the record sheet that looks incomplete, please let us know (those are supposed to be filtered out before the record sheet is populated). Note however, if the record is is a correction, it may look incomplete because a correction may only correct one part of the original record.

Why do we validate data?

Data validation is required to ensure our dataset is reliable and accurate. At the moment we have over 500 hundred hard working research assistants that are entering more than 17,000 policies, updates and corrections. With so many minds, there is bound to be a difference of opinion and skill on how policies should be coded. This difference gives rise to conceptual errors and policies that have been entered that differ to our coding guidelines. For example, is a policy about quarantining or lockdown? Should a policy be entered as one, or broken down into smaller policies? Ideally, we should have high intercoder reliability, which means that two independent people will code the same source in the same way, but with a complex survey this is increasingly difficult. To increase intercoder reliability, we have designed a validation process.

How do we validate data?

Validation is split into two main stages; recoding and reconciliation. Recoding is carried out by experienced coders, from a source chosen out of the randomly selected validation dataset. Reconciliation is done by the validation PIs, who take the original policy and the recoded entries and try to find a match, determining if two independent coders, who had the same source, found the same policy and coded it in the same way.

How do I join the validation team?

1. Send an email to Joan (joan.barcelo@nyu.edu) to signal your interest in becoming a validator.

2. We will then send you a link to a quick test survey that helps us check your coding level. We do this to ensure that everyone who joins the team has a comparable level of coding skills. The score threshold for being added to the validation team is 70% accuracy.

Second Round of Validation: “Checking”

Every entry in the validation set will be validated twice. The second round of validation - termed checking for clarity - will help us determine the most appropriate coding for each policy. The procedure for checking is _nearly _identical to the first round of validation described above. Two important things to note:

1. You should not check an observation that you coded in the original dataset.

2. You should not check an observation that you validated in the first round of validation.

It is important that each round (original entry, validation, and checking) be done by three different individuals. This ensures that our original coding, validation, and checking processes are independent of each other and makes the quality of our data more reliable (statistically speaking)! What follows is a description of how to get involved in checking the data.

What is Data Integration?

Data integration is assessing the overlap between data external to CoronaNet and recoding data that is currently missing from CoronaNet into the CoronaNet taxonomy, while giving proper attribution to the original coders. To see the list of external datasets we are integrating data from, see the Data Integration Guidelines.There are in total around 150,000 policies that we have identified in the external data which we can potentially integrate into the CoronaNet dataset. We have done our best to map this external data to the CoronaNet taxonomy but there are some things that we cannot control and we need your help to work through.

The external data should be seen as an additional source of information that we hope will make it easier and faster for RAs to identify policies to document for their country or subnational region. However, like all sources of information we use, we still need to vet this information carefully before incorporating it into the CoronaNet data. While there are around 150,000 observations in the external data, that doesn’t mean we aim to increase the CoronaNet database by 150,000 observations. This is for a variety of reasons.

How to integrate data?

First of all, make sure you read the Data Integration Guidelines and you have access to the CoronaNet Data Integration Sheet:

1. Identify data that other datasets have documented but which are not currently in the CoronaNet dataset. Fill in this information in the overlap_assess column in the CoronaNet data Integration sheet.

2. Recode the data that is not currently in CoronaNet:

   1. To recode this data, RAs should adhere to the following steps:

      1. Identify policies that are not currently in the CoronaNet dataset by searching for rows that have the value ‘No’ in the overlap_assess column

      2. Click on the ‘link’ or ‘pdf_link’ for that observation and read through the information in the raw data source.

      3. Code the information that you find in that link into the CoronaNet Qualtrics survey. You can use the other column information which maps in the CoronaNet Integration Sheet as a guide for how you can code certain fields.

      4. At the end of the CoronaNet Qualtrics Survey, you will be asked two questions:

         1. [collab] “If (one of) the sources that you used to document this policy came from another dataset, please note which dataset’ ➪ Information about the dataset that you are integrating will be found in the ‘data’ column in the CoronaNet Data; if you used a source/link that you yourself found, please choose ‘I found this source myself’ instead.
         2. [collab_id] ‘Please copy and paste the unique id of the record that you used from the other dataset in the text entry below’ ➪ If you use a source from an external dataset, in this field, copy and paste the ‘unique_id’ found in the ‘unique_id’ column for this observation found in the CoronaNet Data Integration sheet.

      5. In the ‘integrated’ column in the CoronaNet Data Integration sheet, please choose one of the following:

         1. ‘Integrated’; this means you have identified a policy that was in another dataset and recoded it into the CoronaNet taxonomy.
         2. ‘Integrated with additional original research’: You may have to do some additional research for any number of reasons. E.g. the information that you receive from the link or pdf_link of the external dataset may be unclear or require additional context/knowledge to code well. In such cases, please note what additional research you had to do in the ‘Notes’ column and click this option.
         3. ‘Integrated with additional work to find a new link’ means that the original link for the policy as noted in the CoronaNet Data Integration sheet is dead but that the RA was able to find a new link that corroborates the information described in the ‘description’ column. In this case please choose ‘I found this source myself’ option in 2.4 and click this option in the data integration sheet. Note that if you were able to find the information from the original link using the Way Back Machine then choose the ‘Integrated or ‘Integrated with additional original research’ option as appropriate.
         4. ‘Integrated with additional original research AND with additional work to find a new link’: means fulfilled both the criterion under: ‘Integrated with additional original research’ and ‘Integrated with additional work to find a new link’. See above for more information.
         5. ‘Duplicated policy’: this means that there were multiple external policies that were duplicates of each other. In this case, please only integrate one of them (and choose one of the ‘integrated’ options above). When you click this option, this means you do not integrate this particular policy because it is a duplicate. If the data is already in CoronaNet, pick one policy to mark as ‘Yes’ in the overlap_assessment and find the corresponding record_id to paste into the matched_record_id column. In general, for duplicated data, the overlap_assessment should be ‘No’.
         6. ‘Not a relevant policy’: this means that after having taken a closer look at the link for the observation is not one that we would code in CoronaNet. The corresponding overlap_assessment should be ‘No’ in this case.
         7. ‘Link dead, no other link found’ means that the original link for the policy as noted in the CoronaNet Data Integration sheet is dead and the RA was unable to i) use the Way Back Machine to find the original data ii) find another link to corroborate this information. In this case, please do not recode this data.

This might seem like an overwhelming process at first so don’t worry if you make a mistake. Check out the Data Integration Errors sheet to see if you might have made an error and get credit for your work when the mistake is fixed!

Please make sure to read the Data Integration Guidelines for further tips and things to watch out for when doing data integration.

What is Slack?

Slack is a collaboration software tool that enables users to share messages, tools, and files with their fellow team members.

It helps increase productivity amongst large, remote teams and saves everybody from getting lost in endless email chains.

Key Functionalities

Channels

Channels are where the work happens!

Each different part of the project has its own dedicated channel, where all the people involved in that part can easily communicate.

All the messages shared in these channels are searchable, so you will never lose out on information.

Threads

If somebody posts a message in a channel that you want to add to, start a thread specific to the original message.

[](images/manual_img/9. Slack threads.png{width=70%}

Direct Messages

Perhaps you need to contact somebody within the project personally, but there is no need for a specific channel, utilise the direct message function instead.

Notifications / Mute Channel

Maybe it’s the weekend or you’re taking a break; pause all notifications here!

You can also customize notification settings or mute specific channels by clicking on the ‘Details’ tab of the channel.

You can also customize notification settings or mute specific channels by clicking on the ‘Details’ tab of the channel.

Pinned Items

Important/useful messages in a channel may be ‘pinned’.

‘Pinned’ items can be viewed here!

CoronaNet Workspace

All the information you need regarding the CoronaNet project can be found in our Slack workspace. In the rare circumstance you can’t find what you’re looking for, there will be somebody on-hand in Slack to help you answer your question.

Queries regarding policy coding, data validation, data cleaning, existing records, using the CoronaNet app, Hogwarts houses, Zoom team meetings, even birthday wishes for your CoronaNet colleagues, can all be found in Slack. It is the beating heart of CoronaNet!

Slack workspaces have subsets of different channels, the more aspects of the project you are involved in, the more channels you will be invited to join.

To help you navigate your way through the different channels, below you will find a brief summary of each one.

# random With such a global team, spread across multiple time-zones, it’s impossible for us all to gather around the water cooler for a short conversation. Utilise this channel as a substitute! Also, a good place to wish people a happy birthday!

# shinyapp-cornedit Direct any question you have about the Shinnyapp here

# orphaned-records Use this channel to talk about any records you are having trouble locating (or otherwise need help with).

# research-ideas An open forum where you can share any research ideas you may have as you are entering data. Have you noticed anything peculiar / interesting / innovative about certain Countries / Regions approach to policy making? This is the channel to share those thoughts in.

# Country / Region Once you are assigned a Country to work on, you will be invited to the corresponding channel. These channels are a platform for you to coordinate with the other RA’s working on the same Country / Region as you and provide an easy way for you to contact your Country/Regional Manager regarding any specific questions you have.

# Gryffindor / # Hufflepuff / # Ravenclaw / # Slytherin Once you are registered as a member of CoronaNet, the sorting hat will assign you a house! Use this channel to meet your fellow house members and consider it an additional support resource for any questions you may have.

Slack ‘Office Hours’

We have Slack ‘Office Hours’ in the #ra-chat Slack channel from 8am CEST to 4pm CEST every day to answer your questions and provide feedback (while we may also be on at other times, we are making a commitment to being there during those times in particular). Please feel free to post to the channel in off-hours as well! We will get to your questions and comments as soon as we can.

We have some great RAs who have been working with us on this project for a long time who will be stepping in to help out with the #ra-chat questions, they are:

• Monday: Marco Waldbauer and Hans-Peter Novak.
• Tuesday: Paloma Laye and Kader Saigili.
• Wednesday: Celine Heng and Silvia Biagioli.
• Thursday: Whitney Burkes.
• Friday: Isaac Bravo and Jurgen Kadriaj.
  

Note that a PI will always be monitoring these exchanges and a PI might step in if there is a tricky question, but you’ll be in very competent hands with the team above!

Shiny App

The Shiny App can be found here. In order to access the app, you will need to get permission. You should get a message from “shinyapps.io” in your email to get access to the app. Please search your email for “shinyapps.io” if you did not receive the invitation. If you still do not receive one a few days after joining the project, please message in the #record-tracker-app channel on Slack.

What do I use the app for?

You can use it to:
* Make corrections to policy entries (NOT updates) * Find links to make corrections or updates to a policy entry * Look at what policies have currently been entered for certain countries * See a timeline visualization of policies * Find FAQs for internal use about the project

How often is the data updated in the app?

The data is updated approximately every 24 hours. In the “Recorded Data” section of the app, it will note the most recent data currently in the app.

.png){width=60%}

How do I use the app?

You can filter the data in the Policy Table in the app in two ways:

1. You can use the filters for country, RA name, policy type, etc.
2. You can click on a policy in the Timeline Visualization.

Filtering using country, RA name, etc:

1. Select the Country and/or City/Province of the records you are trying to locate (one or more Countries can be selected simultaneously). You MUST select at least one country.

[](images/manual_img/17. Shiny select country.png{width=60%}

2. To further refine your search, the specific policy category can also be defined

3. “Policy Records Table” displays a full list of all available records that match the criteria entered above

• The “Correct” and “Update” buttons, shown in the table above, are a direct link to the Qualtrics survey for that individual record. The ‘record_id’ and ‘policy_id’ are also easily identifiable in this table.

4. “Timeline Visualization” shows the timeline in which the policies are active, and can be used to monitor ongoing policies and see if they need to be updated/ended.

• By hovering the cursor over one of the blue tiles for a few seconds, the record description will appear.
• By clicking on one of the blue tiles, that record will become ‘selected’. The record_id’s of the policies selected by the user will appear at the top of the page (top left of the screenshot above).
• If the user then clicks on the ‘Policy Records Table’ tab again, only the records selected by the user will now be visible in the list (as shown below).

• Utilise the ‘Clear records selected’ button to clear this filter and repeat the process from the beginning.

Organisational Flow Chart

Click here for high resolution version

• All questions about how to do something in the project/where to go to help, please contact the prefects.
• Any questions about your region, sources for entering your policy or if you need a break, please contact regional managers.
• Please see the table on the next page for name of contacts.

CoronaNet organizes its coding in regions and countries. Find out what region your country belongs to by checking out the map below or visiting this link for an interactive version of this map!

Organization

• Task Force will be added to the #task-force-managers Slack channel.
• In addition to the weekly meetings that Task Force managers should have with the RAs under their supervision (see more below in the ‘Key Responsibilities’ section), there will be periodic meetings for task force managers to provide feedback and exchange information with each other and the PIs. These meetings will be announced in advanced in the #task-force-managers Slack channel.

Scope of Responsibilities

• Task Force managers are responsible for fulfilling the ‘Key responsibilities’ listed below for their given task areas

Onboarding new RAs

Assess, Plan, Code, Clean!

Doing data collection and entry requires having knowledge about 1) what the policies are in the region that you are responsible for and 2) how to document those policies in our survey instrument. To get a handle on both of these issues, it helps to first assess what the policies are in the region you are coding, make a plan for how to code them in the survey, code the policies into the survey and clean any previous entries or inconsistencies in the data. In the below, we provide more guidance on what this all means:

Assess

In order to assess the current state of the data and to learn more about their country before they start coding, RAs are asked to create a country overview template. This enables everyone to get a good understanding of the policies that have already been entered in their country/region, so that there is no duplication of policies, to see what policies might need to be ended or updated and also what policies have not been entered at all. This should be finished and sent to the Regional Manager within 7-10 days.

• Video how to fill out country overview template (Password f5G6^AY7).
• Shinyapp guide.
• How to use the Shinyapp video.

Plan

Next RAs are asked to create a plan for how they want to enter their first policies. This helps see how policies are connected to each other with updates and gives the Regional Manager a chance to offer some feedback and tips on how to better code policies. Once the plan is submitted to the regional manager, they will set up a zoom or skype meeting for some one-on-one feedback.

• Timeline Template to help plan.
• Video on how to fill out the Timeline Template.

Code

The process of coding policies is different for every country and region, some countries have relatively straight forward policies and others have fine grained and confusing policies. When in doubt on how to code a policy, we recommend that RAs:

• Ask their question in the ra-chat, regional/country channel, or ask their regional or country manager.
• Check out the coding guide.
• For more general support check out our Zoom hangout room where RAs can code together or have a chat (Password 12345).

Clean

In order to achieve the project goal of having clean and complete policies up until October 1, 2020 by our deadline of January 1, 2021 we are focusing on cleaning different policy types each week. RAs are to fill out their regional/country checklist once a week. This checklist breaks the cleaning process into small tasks for each policy type.

• Regional country checklist.
• Video on how to fill out the checklist (Password tCQ0%8wC).
  

All these links, resources and more can be found on our CoronaNet Research Assistant Dashboard.

Summary of Main Tasks

• Research policies thoroughly and enter them using the Qualtrics questionnaire.
• Based on the number of hours you are asked to commit to the project, we expect RAs to do 25 overlap assessments or 5 coded policies each week.
• You have to fill out the RA internal and Well Being surveys every 3 months. * When the time comes, you will get the link to the survey via email and it will also be available on the #general channel on slack.
• Keep policy records up-to-date (enter records chronologically in order to make it easier to update/end policies as they develop).
• Attend weekly RA meetings with the CoronaNet team (Wednesdays 4.30pm CEST, weekly).
• Attend weekly meetings with the Task Force Managers (to be set up by the Managers and communicated in Slack).

RA points of contact?

• Task Force Manager
  • Specific questions regarding process in the task force.
  • General point of contact/support.
  • Questions regarding the task-specific spreadsheets.
• #ra-chat
  • Questions regarding how policies should be coded in Qualtrics.

RA Onboarding Process