4/10/2023 0 Comments Maxqda separate code segmentsThere might be a long term resolve to combine and compare in the form of journal articles, conference papers and so perhaps this will not impinge on day to day decisions during analysis. Final reporting by each partner may be largely independent and site specific, as in within case analysis. Partly arising from the above but possibly independent of it are the dimensions and logistics of collaboration. Basic measures such as working inside the software with data files whose text is never edited or are read-only might be necessary. Such a process might require certain early safeguards to be sure that the repeated merges work each time. Team projects often seek to follow an incremental process of merging work repeatedly. In some software packages specific parts of projects can be imported into another project. Separate projects can be ‘merged’ or one project (or several, in turn) can be imported into another. Many planning issues have to be addressed because of this one circumstance. Different team members cannot usually feed into one ‘project’ from different work stations at the same time, although Transana, a video analysis package, is the exception to this rule in that it provides a specific multi-user version designed for team situations. The project becomes a container or linking device for all further work. Most CAQDAS packages are single user software programs in which (although the terminology differs), the user creates a ‘project’ file and assigns or imports all the data files relevant to the research into that ‘project’. Elements of the project can be isolated and interrogated while comparisons across the different elements can also be achieved once they are drawn together. Will it be relevant for just one team, several, or all teams to use a CAQDAS package to assist in the analysis? Are both within case and cross case analyses intended? Project design, though not merely revolving around what the CAQDAS package can do, can be reflected in structures and displays within the software project. Research project designĪssuming that different teams of researchers are all contributing in some way to the research project, are they each pursuing similar research processes at individual sites? There could be disciplinary or methodological differences to each team’s contributions. Key strategic issues in collaborative qualitative research are the research project design, the issue of multiple users of CAQDAS packages within a team project and the logistics of collaboration. Therefore while these protocols are useful for everyone in a team or even an individual, it is the co-ordinator who might operationalise some of the ideas coming from all the protocol sections at this resource, into a set of conventions to be followed by team members. In team research there should ideally be a CAQDAS co-ordinator who is responsible for systematising everyone’s use of a qualitative software package. Our aim is to clarify processes and provide constructive ideas about the management of collaborative work in the context of team working. See our software reviews for specific information about collaborative processes using individual software packages. The needs of particular projects will be quite different as will the way your chosen CAQDAS package is used. Whatever the situation qualitative software may play an important role. For example, you may be involved in a local participatory project, a multi-disciplinary intervention evaluation or a cross-national study comprising many complex components. Here we raise broad considerations as starting points in planning to use CAQDAS packages within team projects. The dynamics of research teams can vary quite significantly, as can the role of software within them. Collaborative qualitative research: the extra dimensions of project managementĬonducting research in team situations can pose a number of challenges.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |