qcoder
qcoder copied to clipboard
ropenscilabs
Basic analysis tools
While aiming for MVP we should think of some basic analysis tools that we might want to include. As discussed at the unconf we don't want or need to have every bell and whistle but some items would be useful.
Ideas from me, please add more in comments.
- [x] Dashboard with current status
- [ ] code-document matrix
- [x] report template that shows all the text for a given code
- [x] report template that shows some summary data like frequencies of codes.
Some of this is done but the first two are not. Need to clarify what status means.
Just for information, I am now working on a kind of qcoder module for creating cognitive maps based on the coding of qualitative data. I will adapt my package CogMapR (https://gitlab.com/FrdVnW/CogMapR) so that qcoder output (coded data) could be the input for cognitive mapping tools. This is a precise analysis tools (linked to a specific manner to code the text). Now it is on a branch on my fork. We will see in the future how to build a module that can easy 'add/enabled'... if relevant.
Good news @elinw . We are working with colleagues on a project using the 'qcoder' intensively (my forked version as explained above). After that, sure we will have new ideas for the 'qcoder'. I will be in Toulouse, useR!2019 for a talk on the 'cogmapr' package and the coding of qualitative documents with cognitive mapping techniques. I will certainly mention the work of 'qcoder'. Will you be there also ? or some of the authors ?
Oh wow that is so exciting! We weren't there (I wish I could have been!) but that is really great. Do you have slides or anything you could share?
Found the slides! I wonder if interfacing to cogmapr should be like interfacing to tidytext ... we should have a function the provides the data in the formate needed. I could see making a set of those.