Looking at this from the task list: “(6) Implement exporting of selected codings to a CATMA file. Doing so should allow to leave code hierarchies built inside CATMA intact, just adding more codings.”
And from the requirements:
Export to QDA software. Ideally, the codings of one ethnographer could be saved into a file (also including codings from others that this ethnographer did take over into her code hierarchy). The requirement is:
- Ability to filter which content will be in the export. Making a list of groups is granular enough. Non-relevant content (like administrative posts etc.) in these groups can be easily ignored as it will not be coded either, and can also be deleted in the export's target QDA software if needed.
- Ability to filter which codes will be in the export. This would default to "all own codes, including shared codes to which one has subscribed", but options would allow to limit this further. Since it is rarely needed that one wants to exclude own tags, implementing this part can wait or even be discarded.
- Export for download in a format of one open source QDA software.
- Real-time syncing to a web-based open source QDA software. [optional] This can be the same QDA software as the one for which a downloadable file is offered.
Download the zip of CATMA 3.2 from here. Unzip it. Run (
java -jar catma/catma3.jar)
CATMA works across 3 files:
- source file -- [docname].txt. May also support formats other than plain text (?)
- annotation file -- [docname_structure.xml]. This contains the character offset
- user file -- [docname_user.xml]. This seems to contain user preferences, such as what color each tag should be displayed
you can see examples of this in the CATMA tests – try rose_for_emily.
I’m going to start working on a limited version of this. Namely, a function to generate CATMA-compatible XML from a piece of tagged content. Things I’m not going to do for now:
- merging with existing CATMA tags
- using only a selection of tags
- providing more than a minimal UI
Once we get the basic export right then either I’ll come back to those additional requirements, or we can spin them off as separate tasks.