Using the default Event Sampling method, you manually create new Events whenever something noticeable happens. This process is referred to as 'Event logging'.
Those Events can be mutually exclusive or (partly) overlapping. They are used to store one or more Codes, representing the behavior observed, as well as the corresponding time information.
Your code definitions are the key to your success!
Depending on the complexity of the required coding scheme, your personal implementation becomes more and more important. Finding the perfect coding rhythm largely depends on your personal preferred approach and the number of Codes at your disposal.
The process of logging Events can vary a lot, due to the available Coding modes and corresponding options.
Note: There is one very important rule, though: Each Event can only be closed with the same [key] as is was opened with. Unless you have set up exclusion lists for mutual exclusive coding!
In case of the latter, the start of each new Code automatically closes any previous Event that contains a Code from the same exclusion list
Basically there are two ways of logging a Code, independent of the chosen Coding mode:
 | By mouse click using the Coding panel - The easiest way for inexperienced rater and/or complex coding systems, because no shortcuts need to be memorized. |
| By pressing a shortcut [key] on the keyboard - The fastest way for experienced raters and/or simple coding systems, where only a few shortcuts are to be used. |
What fits your aim and coding system best, depends on the size of your coding system and your preferred way of working.
| TIP: | If you are into a lot of transcriptions, pay attention to the section Transcriptions and Comments! |
A great advantage of INTERACT is that you can change the chosen Coding mode as well as your coding scheme at any time during your research project.
Note: You can even combine multiple methods, in separate sessions, by logging part of the data with one method and switch to the other method for the rest.