---
# System prepended metadata

title: Welcome to newcomers
tags: [' process', authors-only]

---

---
title: Welcome to newcomers
tags: authors-only, process
---

# Welcome to the c19vax-wiki team!

:::info
Are you joining as a page **curator** or as a page **manager**? You must know this before you proceed so you know which section below is applicable. Check your invitation email if you are unsure, or **[contact us](mailto:contact@scibeh.org)** if you need more information.
:::

[TOC]

## Information about the project
* [About the handbook and Wiki](https://c19vax.scibeh.org/policy#About-the-COVID-19-Vaccine-Communication-Handbook-and-Wiki)
* [Current list of pages and team assignments](https://hackmd.io/@scibehC19vax/tasklist)
* [Instructions to authors](https://hackmd.io/@scibehC19vax/instructions):  guidelines and tips for updating the Wiki pages
* [How the handbook and wiki came about page](https://c19vax.scibeh.org/how): formal documentation of roles and processes

## Joining as a page curator

**Page curators** locate new resources, links, references, and items relevant to their Wiki page, and bring it to the team's attention.

Curators should email the new information to `c19vaxwiki@gmail.com`. Please **include the topic and page you are proposing the information for in the email title or body**, to faciliate assignments to the correct page manager.

Curators can also make proposed changes to the text in a page (e.g., 'change XXX paragraph to YYY paragraph'). They should email this to `c19vaxwiki@gmail.com` as well. 

As a curator, you can be dedicated to a single page (in which case, you will be credited on that page).

You can also be a general curator, in which case you just email any new Wiki-related information you identify to `c19vaxwiki@gmail.com`, **including at least the topic** if you do not know which page it would apply to.

<!---We also have a **supercurator** role, which is responsible for assigning curated information to the page managers. **Supercurators** need to maintain good knowledge of the [different Wiki pages](https://hackmd.io/@scibehC19vax/tasklist) and a sense of what information will be relevant for each page. 

<!---Supercurators will use the [GitHub inbox](https://github.com/scibeh/c19vaxwiki/issues) to assign issues to page managers. They should also identify if an issue needs urgent attention. These issues will be tagged `URGENT`, and assigned to the page manager directly. Assigning a page manager sends them an automatic email from GitHub. --->

## Joining as a page manager

**Page managers** maintain the content on their page. This means including updates at regular intervals. For substantial additions, these should be cleared by an expert reviewer to ensure the content is valid.

Page managers do not need to be experts in the domain, but should be confident of making judgement calls as to what needs expert clearance (i.e., what is a substantial change) and what can be immediately updated.

If an expert in the page domain is a page managers, the expert reviewer and page manager role would be combined in that case.

**Note: We are currently doing a test run with volunteers to help with page updating, and will update here with a process for this if it works well.**

==Update: volunteer support is now available! See [here](https://hackmd.io/@scibehC19vax/tasklist) for the pages who have assigned volunteers to help with updates.==

### Page manager workflow

Page managers will have their own **personal page board on GitHub** ([example here](https://github.com/scibeh/c19vaxwiki/projects/4)). You need a GitHub account to access this.

:::info
**See your page assignments and find the link to your board [here](https://hackmd.io/@scibehC19vax/tasklist).**
:::

The board has three 'buckets'. The first is for **new items**: these are sent by the curators, and will automatically appear when available. 

You should consider whether the item is suitable for addition to your page. If it is not, you can drag and drop it in the **ignore** bucket. 

If it is suitable for inclusion, update your page accordingly. We recommend you could do this in a batch, ==**once a week**==. 

**Please let the team know if there is important new information added to your page, so we can share it on Twitter.**

Once you have updated the item, you can drag and drop it in the **done** bucket. That way we all know what items have been added to the Wiki.

_The video below summarises the above and shows what it looks like in the GitHub page boards:_

{%youtube WfYovKxZ5jc %}

<!---Please document substantial changes on your page by **naming the page version with an updated version number**.

> ==Insert video for this? If so, I need some time to do it (probably not before Friday!)==
> 
> ==I'd be inclined to remove this section until the video is ready and then add it. I don't think we need this for a while as page managers are unlikely to make major changes. Do we also need to tell them to tell us, so we can tweet etc? SL==-->

<!--## Joining as an expert reviewer

**Expert reviewers** check and verify proposed new content/changes to page content within their domain of expertise. 

==We define expertise as: XXXX==

==I'd be inclined not to bother with putting this here at all. Being a reviewer is pretty straightforward, and wouldn't it suffice to explain their duties in an invite email? I don't want to overcomplicate this page. SL==-->


## Creating a new Wiki page

If you recognise that a topic needs its own new page and want to produce this, please [notify the SciBeh organising team](mailto:contact@scibeh.org). They are:
* Dawn Holford
* Stephan Lewandowsky
* Ulrike Hahn
* Stefan Herzog
* Ol Beun

(Best to use the contact@scibeh.org email to reach the team. But feel free to contact any one of us individually if you prefer.)

The team will aim to get your page set up quickly, but you can start writing beforehand and paste it into your page once the link is ready.