The COS platform's remapping feature allows users to change how certain data is displayed without altering the underlying results.
Let's use the "remap responses" field as an example.
In COS, when a result is displayed in the data, it is automatically assigned a numeric value corresponding to the order in which the response was entered in the script. So if the first coded response is "YES", it will be displayed as a "1" in the data. The second response, "NO", will be displayed as a "2", and so on.
However, some clients may have their own existing system for coding responses. The remapping feature in COS enables users to easily account for this and change the default COS response codes to match the client's requirements.
To do this, you would input the following equation: X=Y=Z, where "X" is the question, "Y" is the original response, and "Z" is the new code you want associated with that response. For example, if the client's code for a "YES" response is 20, you would input 1=1=20 to remap the first response to display as 20 instead of 1.
The remapping functionality extends beyond just responses. Users can also remap status codes (e.g. changing "C" for "Complete" to "Complete") and column headers (e.g. changing "duration" to "call_length") to align with the client's preferences.
When inputting any remaps, it's important to separate each individual remap with a comma and avoid including any spaces. For example: C=Complete,CP=Yes Patch,LM=Left Message,D=Disconnect.
By leveraging the powerful remapping tools in COS, users can ensure the displayed data aligns perfectly with the client's needs, without having to alter the underlying results.