Hi everyone,
many of you are now working on quality assurance, i.e. another
round of looking over almost-finished files to make sure that
nothing is missing and the language is presentable. The guidelines
for this task are attached below for future reference. This
includes tasks that not everyone has been made aware of yet:
please check whether all provided links are working; and please
mark all your changes in red font so that we can see what you have
changed afterwards. Here is the full list:
Quality assurance
- check whether the coders filled in everything they are
supposed to fill in. Are (1) sources provided, (2) all relevant
statements actually coded (e.g., coder 3 provided a source but
forgot to fill in pledge_fulfilled). Mark statements where
something is missing in an extra column - this will go back to
the coders.
- read the statements again and, where applicable, check whether
a statement is flagged as credit claiming or status quo claim in
the notes. (credit claiming: this is not a pledge but rather
boasting about something great the party has done in the past;
status quo claim: "we will keep the top marginal income tax rate
at the current level")
- read the notes from all coders and edit the language where
required (spelling mistakes, non-professional language). This is
not so much about the contents but rather about how the notes
look to an outsider.
- check whether all provided links are working
- mark all your changes in red font; we will look at them later.
Thank you!
Best wishes,
Leo