Top Five coding

first run through coding high volubility segments, spring 2023

As of December 2022, all VIHI files have been coded through all 15 randomly-sampled segments. Now, we have added 15 new (+5 extra) segments that were chosen for being particularly dense with speech, and it's time to start coding them.

However, we anticipate these will take much longer to code BECAUSE they contain more speech. Instead of trying and failing to code everything, we want to aim for an even distribution corpus-wide that we can conceivably finish by the end of May 2023.

• First, we're focusing only on VI files and their age matches (color coded blue and purple, respectively on the Asana board).

• Second, we are only going to code the 5 most dense high volubility segments. (not the first five chronologically)

Instructions for finding the Top Five high volubility segments in your file:

• Navigate to your your parallel-annotation folder at Fas-Phyc-PEB-Lab/Duke/VIHI/SubjectFiles/LENA/annotations-in-progress/YY_XXX_ZZZ_Your-Name/YY/YY_XXX/YY_XXX_ZZZ

• Open selected_regions.csv and VIHI_coding_issues_YY_XXX_ZZZ.docx.

• In selected_regions.csv, you will see a column called "rank." Find the top 5 regions in this column by looking for the lowest numbers (1-5), and find their corresponding "code_num" in column G. Make sure they're high-volubility and not high-volubility-extra.

• Add a section to the coding issues document below the superchecking note called "Top Five hi vol regions"

• List the code_num of the 5 segments you selected above. This will help you find them in the .eaf (ELAN) file, as this will correspond with their value on the code_num tier.

  • ***Remember that these segments may chronologically be mixed in with the random segments, so the segment number listed by ELAN next to each segment natively won't be the same as their actual code_num value. All code_num values for high volubility and extra segments will be 16-35, since random segments were 1-15).

• Add the description and timestamps of these regions to your coding issues document, and proceed with coding these five segments as usual (as described in random sampling coding instructions).

• Once you have completed these five, export file as a .txt file and check it for errors using the minchat error spotter. Move your file across the Asana board from "top five coding in progress" to "txt, minchat, update spreadsheet, push to github" and assign it to Lilli.