A fantastic, engaging call today! We welcome @SZdenek to the team, who came with many generative questions that spurred some great conversation.
Take-homes from the call:
- Define all codes, no matter how obvious they seem, so we can be sure that we are using the same words in the same way.
- Break up longer/highly specific compound codes into 2 different ones, as long as each individual code carries semantic meaning and isn’t too vague.
We decided that assigning codes in two different languages to the same block of text (native language and English translation) instead of doing the slash system is very preferable, so that co-occurrences in English and English translations across the languages can display (and so we don’t just have isolated islands of languages). This will optimally be supported by a front-end function that can assign both to the same text at the same time. Ideally, when typing in codes in English, the box will display code suggestions from across the POPREBEL projects (so, by any other POPREBEL ethnographer, instead of only individual’s code or previous system where all codes from all projects were suggested). Depending on how the dual-code function works, suggestions in the native language should ideally include all codes that have been assigned in the project in that language. @matthias
There are 2 major things to focus on when coding using English translations/English:
- Read others’ codebooks and make note of when they are using a different code in the same way as one of yours – then make a note suggesting that we merge the codes.
- Read others’ codebooks and make a note of when they are using the same code in a different way – make a note that we should fork the codes.
We had a long discussion about hierarchies. Conclusions:
- Make sure that all codes carry meaning on their own and do not rely on a hierarchical representation (e.g. the presence of the parent code) to carry meaning. Both parent and child codes should carry clear semantic meaning on their own.
- Use hierarchies to organise codes in the codebook. Don’t worry about inputting them into the backend right away, but continue to use them to structure and make the codebook clear. Feel free to use a separate tab in the codebook to make note of hierarchies.
Suggestion for next call: Thursday April 30, 3pm Brussels time. Can everyone make this?