ImpactMapper offers support for importing existing coded data (we call t also taggings) on which you can run an analysis and generate charts.
These files will be imported into an existing analysis project. Our application will ask you to specify the project by selecting one of the available options in the import screen.
Before discussing the coded (taggings) data structure, please review our tag data imports guide (TODO: link here). Tag data needs to be included along with the taggings data and it is usually easier to prepare the rest of the CSV structure if this step is done correctly!
Taggings
Taggings are represented as a word or a sentence which is connected to one or multiple tags/tag groups. A CSV file will include on every row the information about the tagging tag name, tag group, tag category and the text which is annotated and stored in our system. If a tagging carries a numerical value, the Quantity and Quantity Label information will be included as well.
An example of a such CSV file can be found below. Please consider using it as a template.
Report Content,Quantity,Quantity Label,Tag Category,Tag Group,Tag Name
Results indicate a result of 10% new jobs.,10,percent,Social,Default Outcomes,Decreased poverty
Peaceful protests starting 2017.,,,Social,Default Outcomes,Decreased violence
Peaceful protests starting 2017.,,,Economical,Default Outcomes,Decreased corruption
As part of the new law initiative.,,,Economical,My Outcomes,Decreased poverty
It is important to:
not include multiple tags, tag groups, report content or any other data in a single row, keep things one-to-one!!!
duplicate the report content if it belongs to multiple tags/tag groups
provide numbers in the Quantity column
As you can see in our example, the sentence Results indicate a result of 10% new jobs. has a numerical quantity in percentage of 10. The sentence Peaceful protests starting 2017. is tagged with two tags (the Decreased violence and the
Decreased corruption).
Error reports
ImpactMapper uses an automated process for importing the CSV files and the error handling is reported after every import.
The taggings import is split into two steps. The first step is to process the tags related data. The taggings data will be processed as the second step.
The errors generated in the second step should be handled in the similar way the tag data errors are processed.
If you need help with the data cleaning or understanding the error report summary, please get in touch with us.