Picking the right Coding Mode is one of the biggest challenges, but don't worry: You can combine different modes and coding systems within the same document!
You can switch between coding modes and code definitions per observation pass.
 | Standard (Ad-hoc) - This is the most direct coding mode, perfect for mutual exclusive codes as well as regularly overlapping Codes and a wild combination of Codes with and without duration. The number of Codes inside a single Code definition file is limited to the number of ASCI keys on a keyboard, but you can manually switch between Code definition files, especially if you observe in multiple passes. |
This basic logging method was designed to:
oLog separate events per Code
oCreate overlapping Events on the fly
oAssign multiple exclusion lists for mutual exclusive coding*
oEasily combine durational and none durational codes
oDefine a single code definition file per observational pass.
*) Mutual exclusive coding, allows you to only log the start of each behavior. A new behavior automatically ends the previously logged Event. For details, read Define Mutual Exclusive Codes.
| Lexical (Post-hoc) - The most laid-back way of coding your video: Log all kinds of behavioral Events using just the SPACEBAR and describe the observed behavior with one or multiple descriptive Codes from different Classes, while the video pauses! There is NO limit to the number of codes to be used. This mode is also advisable to code multiple subjects, if you are using video recordings. |
This very powerful logging method was designed to:
oEasily code your video with just the use of your SPACEBAR
oContinuously, seamlessly and sequentially code your video
oAutomatically pause you video at the end of each Event
oTranscribe Events while the video pauses (replay possible)
oEnter multiple Codes per Event
oBuild hierarchical chains of Codes with Lexical Chains
oCreate context based Classes (column headers) while coding, based on the Codes chosen
oImplement extremely complex coding systems with the help of 'Prefixes'
oCreate combined Codes on the fly, with the option Combine Codes
Using this method as designed, you do log only one sequential Event at a time - all with the SPACEBAR - but coding overlapping events is possible as well:
oRewind the video a bit (for sporadic overlaps) to the start of the overlapping behavior and start from there.
oRewind the video completely and work your way through your video multiple times, concentrating on a certain type of behavior per pass.
oUse, for some behaviors, the corresponding Code keys, instead of the SPACEBAR, to create overlapping Events in addition to the sequential Events logged with the SPACEBAR. This is especially useful for coding none durational Codes that occur during the regular, sequential, Events, that are logged with the SPACEBAR.
oIn case of consequent overlaps, that you want to code in one pass, start and end all Events with the corresponding first level Codes, instead of using the SPACEBAR to log your Events - make sure none of the [keys] for the first level Codes is re-used in any of the sub-leveled code definitions!
TIP: assign only capitals or numbers to the first level Codes, so it is easier to keep them apart.
Note: Especially if you log overlapping Events, using this coding mode, it is very important to remember, that each Event needs to be closed by the same [key] (=Code), as it was started with!!!
This means, that you cannot start an Event with the SPACEBAR and then close it, using the code you' want to apply. You first need to press the SPACEBAR again, to close the Event and while the video pauses, you can enter the applicable codes. The same thing applies, if you use the different Codes to start a new Event: Each Event needs to be started and closed with the same [key].
| Refine Existing Events - This coding mode does NOT create new Events, like the other coding modes do, but enables you to enter Codes into a currently selected Event, without altering the time information. |
You can :
oAdd additional Codes into existing Events, either using existing Classes or creating new Classes.
oOverwrite existing Codes to make corrections
oEnter Codes into empty, interval based, automatically created Events
The Refine Existing Events coding mode supports Lexical chains and Prefixes, so complex coding systems can be used.
Note: If changes in a top level Code result in lower-level Codes using other Class-columns as the initial Codes, the old codes are NOT automatically removed. To automatically remove old Codes from the current Event, use the AutoFill functionality in combination with the Refine existing Events coding process.
The Coding Mode Refine Existing Events is required for anyone doing interval based Time Sampling observations.
•For interval-based coding, create fixed interval Events, as is described in Create Fixed Intervals.
| Complex - This coding mode allows you to log multi-level Codes per subject, during live observations. For this routine, each subject always has a active Event during the observation. This means that you need a Code for every possible situation/condition, for each first level code, throughout the video! A subordinated NILL code can cover the parts that are not of interest to you. |
Note: The Complex coding mode, does not automatically pause the video!
So in most video based cases, the Lexical (Post-hoc) coding mode is the better choice.
This Complex coding mode was designed to:
oLog multiple Events simultaneously (multi-channel) during a live observation.
oCreate a continuous stream of Events, for each first level Code.
oCreate Events with duration only.
oUse multi-level coding systems during life observations.
oEnter multiple Codes per Event, using lexical chains.
oCreate context based Classes (column headers) -in real time while coding- based on the Code just chosen.
oImplement complex coding systems, with the help of 'Prefixes' .
oCreate combined Codes on the fly, in combination with the option Combine Codes.
•
| TIP: | Anyone choosing either the Lexical (post-hoc) or Complex coding mode, should also take a peek at the possibilities described in Create context based Classes and in the Coding facial expressions example. |
Remember: Any of the examples can be adapted to a completely different field, because the difference lays not so much in what you observe, but in the way you observe!