|
1 | 1 |
|
2 | 2 | <!-- README.md is generated from README.Rmd. Please edit that file --> |
3 | 3 |
|
| 4 | +<br> <br> <br> |
| 5 | + |
4 | 6 | # ConversationAlign |
5 | 7 |
|
6 | 8 | Open-source software for computing main effects and indices of alignment |
@@ -45,35 +47,31 @@ ConversationAlign</figcaption> |
45 | 47 | # Before |
46 | 48 |
|
47 | 49 | <span style="display: inline-block; padding: 0.2em 0.4em; margin: 0.1em; background-color: #8B0000; color: white; font-weight: bold; border-radius: 3px; font-family: Arial, sans-serif;"> |
48 | | -How to prep your language transcripts for processing in |
49 | | -ConversationAlign </span> <br> |
50 | | - |
51 | | -ConversationAlign can handle a home brew of your own preferred format. |
52 | | -The order of your columns does not matter. Any other data in your |
53 | | -transcripts (e.g., metadata, timestamps, grouping variables, physio |
54 | | -data) will be retained. Don’t worry about stripping punctuation or |
55 | | -splitting your transscripts across rows. ConversationAlign will do that |
56 | | -for you. |
57 | | - |
58 | | -**Note: ConversationAlign can ONLY process dyadic conversation |
59 | | -transcripts (i.e., two person dialogues)** <br> |
60 | | - |
61 | | -Conditions/Precautions: <br> 1) Your raw transcript MUST contain at |
62 | | -least two columns, delineating interlouctor (e.g., Mary or Joe) and |
63 | | -text. 2) Label your talker/interlocutor column as ‘Interlocutor’, |
64 | | -‘Speaker’, or ‘Participant’ <br> 3) Label your text column as ‘Text’, |
65 | | -‘Utterance’, or ‘Turn’. <br> 4) Save each conversation transcript |
66 | | -somwehere on your computer as a separate file (CSV or txt work |
67 | | -best).<br> 5) Be careful/deliberate about your filenaming convention. |
68 | | -The filename for each conversation will become its event ID (or |
69 | | -document_id) in the dataframe ConversationAlign processes. <br> 6) Move |
70 | | -all your individual conversation transcripts to be analyzed into one |
71 | | -folder (e.g., “my_transcripts”). This folder should ideally by nested in |
72 | | -the same directory you are running your R script in. <br> 7) If you have |
73 | | -metadata (e.g., age, timestamps, grouping variables), you can either |
74 | | -append this to your original transcript or merge the metdata as a |
75 | | -separate file. This is a useful option when you have many individual |
76 | | -difference and demographic details. <br> |
| 50 | +Prep your Language Transcripts for ConversationAlign </span> <br> |
| 51 | + |
| 52 | +- ConversationAlign works ONLY on dyadic language transcripts (i.e., |
| 53 | + 2-person dialogues). |
| 54 | +- Your raw transcript MUST contain at least two columns, delineating |
| 55 | + interlocutor (e.g., Mary or Joe) and text. |
| 56 | +- The order of your columns does not matter. |
| 57 | +- Metadata within will be retained (e.g., timestamps, grouping |
| 58 | + variables, physio values). |
| 59 | +- Don’t worry about stripping punctuation. |
| 60 | +- Don’t worry about splitting your transcripts across rows. As long as |
| 61 | + the corresponding text within each turn is marked by a talkerID, |
| 62 | + ConversationAlign will split and append all labeling data rowwise. |
| 63 | +- Label your talker/interlocutor column as ‘Interlocutor’, ‘Speaker’, or |
| 64 | + ‘Participant’. |
| 65 | +- Label your text column as ‘Text’, ‘Utterance’, or ‘Turn’. |
| 66 | +- Save each conversation transcript somwehere on your computer as a |
| 67 | + separate file (CSV or txt work best). |
| 68 | +- Be careful/deliberate about your filenaming convention. The filename |
| 69 | + for each conversation will become its event ID (or document_id). You |
| 70 | + might need this when processing large corpora. <br> |
| 71 | +- Move all your individual conversation transcripts to be analyzed into |
| 72 | + one folder (e.g., “my_transcripts”). This folder should ideally by |
| 73 | + nested in the same directory you are running your R script in. <br> |
| 74 | + <br> |
77 | 75 |
|
78 | 76 | # Installation |
79 | 77 |
|
|
0 commit comments