-
Notifications
You must be signed in to change notification settings - Fork 0
/
20400-factor-labels-flags.rmd
35 lines (17 loc) · 2.64 KB
/
20400-factor-labels-flags.rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
# 📚 Factor labels: using hashtags{#xfactor-hashtags}
[Hierarchical](#xhierarchical-coding) coding is one way to bring some order to a whole crowd of factors. However, sometimes you don't want to think in terms of a strict hierarchy, or maybe you have an additional set of themes which cut across that hierarchy.
````{r,echo=F}
knitr::include_url("https://player.vimeo.com/video/671894620")
````
Hashtags are useful in either of these cases.
Hashtags are just sequences of characters within a factor label to which you have given a special meaning, and which are unique and easy to search for. These can include letters, emojis or phrases. You can do coding without any such hashtags if you want, but it can help when searching and filtering.
So a hashtag is nothing more than any sequence of characters which is repeated in several factor labels. Any sequence of characters will do. For example you could consider the letter "a" to be a hashtag and display the map showing all the factors which contain the letter "a". But this wouldn't be interesting. The trick when using hashtags is to decide on short, meaningful codes which will not be repeated anywhere else. For example you wouldn't want to use a pair of hashtags like "women" and "men" to distinguish factors which are only relevant for one or the other gender because the "wo**men**" factors would also turn up when you search for "**men**". That is why we have to be careful when creating hashtags, for example by preceding a sequence of characters with a hashtag `"#"`.
A quote like “family situation is better now because of improved food availability” can be coded like this:
> <u>More food</u> --> <u>Improved wellbeing</u>
Now, maybe you are asked also to keep track of any aspects of the project which have to do with nutrition. Nutrition is not really part of your system of factors, but you would like to be able to construct some maps just to look at this aspect. So you can write this:
> <u>More food #nutrition</u> --> <u>Improved wellbeing</u>
Similarly, if <u>Improved Wellbeing</u> is one of the desired outcomes of the project, we might want to reflect that by adding a hashtag "(Outcome)" like this.
> <u>More food --> Improved wellbeing (Outcome)</u>
Then we can easily search for this and other desired outcomes.
A hashtag like “men” is not suitable because it is likely to appear elsewhere (e.g. as part of “women” or “management”). To get round this, add additional characters like a hash: “#men”; this makes the hashtag unique.
If you use curved or square brackets around your hashtags, you can use one of the app filters to hide the hashtags for specific maps if desired.