Back to the Item List


The OECD Survey of Adult Skills (PIAAC) assesses the proficiency of adults in key information-processing skills essential for participating in the information-rich economies and societies of the 21st century. These are: literacy, numeracy, and problem solving in technology-rich environments. For more information about the survey have a look at the official OECD website.

During the PIAAC assessement, user interactions were logged automatically. This means that most of the users’ actions within the assessment tool were recorded and stored with time stamps in separate files called log files. The availability of these log files offers new opportunities to researchers, for instance to reproduce test-taking behavior of individuals and to better understand test-taking behavior.
This documentation provides an overview of the interactions being possible in the items and the corresponding logged events.
A selection of possible event types can be displayed where they occur within the items (pop up box) via the Item List and with a technical explanation via the Events sections.

Additional Information about the PIAAC log files

Please note that log files from the cognitive part are not expected to be processed directly. An automatic extraction of variables is made in the [PERSID]-[TESTID]-Var.xml and is released as the Public Use Files (PUFs).
The general structure of each traced event generated by the TAO CBA platform (for details on TAO see chapter 9 of the Technical Report) looks like:
< taoEvent > Name ="origin" Type ="Event Type" Time ="ms"> </ taoEvent >
The attribute "Name" is stating the physical environment from which the event is issued.
There are three possible values: “taoPIAAC”, “stimulus” and “service”. The attribute "Type" helps to classify the traced events in categories; the possible values are covered in the following table, in the “Event Type” column.
The attribute "Time" provides a time stamp expressed in milliseconds; the time stamp is reset to zero (“0”) at the beginning of each unit.
The following tabs present all available event types and include a short description divided by domain.

Event types for Literacy and Numeracy

The PIAAC screen includes a left panel with the directions and sometimes a response area and a right panel presenting the stimulus. Related event types including a short description are presented in the following.

Event types for Problem Solving in Technology Rich Environments

The PIAAC screen includes a left panel with the directions and sometimes a response area and a right panel presenting the stimulus. Related event types including a short desription are presented in the following.

For the events generated in the context of PS, the payload consists of one or several attribute-value pairs.
In case of several pairs, the following separator is used: |*$

Event Type Description
Event category: environment [events directly bound to the environment applications of PS-TRE]
ENVIRONMENT Currently activated environment.
Payload
Attribute(s) Possible values
environment WB [WebBrowser]
MC [MailClient]
SS [Spreadsheet]
WP [WordProcessor]
Example:
<taoEvent Name="stimulus" Type="ENVIRONMENT" Time="32140">environment=SS</taoEvent>
Event trigger:
TOOLBAR
View Example
MENU Main menu item has been pressed.
Payload
Attribute(s) Possible values
id string [menu identifier]
Example:
<taoEvent Name="stimulus" Type="MENU" Time="39371">id=ss-data-menu</taoEvent>
Triggered event(s):
MENUITEM
Comment:
This event implies a user interaction.
Examples can be viewed in all PS items.
MENUITEM Main menu sub item has been pressed.
Payload
Attribute(s) Possible values
key string [menuitem identifier, environment functions]
e.g.: new, close, sort, etc.
<taoEvent Name="stimulus" Type="MENUITEM" Time="48165">key=sort</taoEvent>
Triggered event(s):
BOOKMARK_ADD
BOOKMARK_VIEW
HISTORY_ADD
NEW_FOLDER
COPY
PASTE
REPLY
REPLYALL
FORWARD
MAIL_SENT
MAIL_MOVED
MAIL_DELETED
SS_SORT
MC_SORT
SS_SEARCH
MC_SEARCH
Event trigger:
MENU
Comment:
This event implies a user interaction.
The payload refers to the “key” attribute as the menu item elements don’t have an identifier attribute (id) in the BLACK files.
Please see below for examples for each triggered event.
TOOLBAR Toolbar icon, desktop buttons to change environment and to split screen (bottom bar) or ‘Send’ icon of (new, reply, reply all, forward) email has been pressed.
Payload
Attribute(s) Possible values
id
Example:
<taoEvent Name="stimulus" Type="TOOLBAR" Time="48165">id=toolbar_back_btn</taoEvent>
Triggered event(s):
ENVIRONMENT
HISTORY_FORWARD
HISTORY_BACK
HISTORY_ADD
BOOKMARK_ADD
REPLY
REPLYALL
FORWARD
MAIL_SENT
MAIL_MOVED
MAIL_DELETED
COPY PASTE
SS_SORT
SS_SEARCH
MC_SEARCH
Comment:
This event implies a user interaction.
The SPLITSCREEN event is captured within the TOOLBAR event.
Please see below for examples for each triggered event.
TAB A tab has been pressed.
Payload
Attribute(s) Possible values
id string [tab identifiers]
Example:
<taoEvent Name="stimulus" Type="TAB" Time="55651"> id=tabbutton2</taoEvent>
Comment:
This event implies a user interaction.
View Example
Event category: Interaction [GUI actions of the respondent]
BUTTON A button has been pressed.
Payload
Attribute(s) Possible values
id string [identifier of button that has been clicked]
Example:
<taoEvent Name="stimulus" Type="BUTTON" Time="63231">id=sortValidation</taoEvent>
Triggered event(s):
DOACTION
View Example
TEXTLINK A text link has been pressed.
Payload
Attribute(s) Possible values
id string [identifier of text link]
href string [target page or pop up identifier]
target _self, _popup [mode to display content]
Example:
<taoEvent Name="stimulus" Type="TEXTLINK" Time="18140"> id=u07_default_txt3|*$href= unit7page1|*$target=_self </taoEvent>
or
<taoEvent Name="stimulus" Type="TEXTLINK" Time="6788169"> id=u07_pg1_txt7|*$href= u07_pg1_popup1|*$target=_popup </taoEvent>
Triggered event(s):
HISTORY_ADD
View Example
TEXTBOX_ONFOCUS Modification of text box (start input). The value of this event provides the content of the textbox before the text input of the respondent.
Payload
Attribute(s) Possible values
id string [textbox identifier]
value string [text input]
Example:
<taoEvent Name="stimulus" Type="TEXTBOX_ONFOCUS" Time="546227"> id=textbox1|*$value=text</taoEvent>
View Example
TEXTBOX_KILLFOCUS Modification of text box (end input). The value of this event provides the possible respondent input text.
Payload
Attribute(s) Possible values
id string [textbox identifier]
value string [text input]
Example:
<taoEvent Name="stimulus" Type="TEXTBOX_KILLFOCUS" Time="549502"> id=textbox1|*$value=text</taoEvent>
View Example
KEYPRESS A key has been pressed.
Payload
Attribute(s) Possible values
ASCII integer [ascii value of pressed key]
code integer []
Example:
<taoEvent Name="stimulus" Type="KEYPRESS" Time="71435"> ASCII=97|*$code=65</taoEvent>
View Example
RADIO_BTN A radio button has been selected.
Payload
Attribute(s) Possible values
id string [identifier of radiobutton that has been selected]
Example:
<taoEvent Name="stimulus" Type="RADIO_BTN" Time="13359"> id=u12rg1_prop1</taoEvent>
View Example
CHECKBOX A checkbox has been selected.
Payload
Attribute(s) Possible values
id string [identifier of checkbox that has been selected]
Example:
<taoEvent Name="stimulus" Type="CHECKBOX_SELECT" Time="23985"> id=check2</taoEvent>
View Example
CELL_CHANGE Status of checkbox in a spreadsheet cell has been changed.
Payload
Attribute(s) Possible values
id WB [WebBrowser]
string [identifier of spreadsheet cell that has been changed]
Example:
<taoEvent Name="stimulus" Type="CELL_CHANGE" Time="155078"> id=content_spreadsheet_ColaD_row65</taoEvent>
Comment:
This event implies a user interaction.
View Example
LISTBOX A listbox item has been selected.
Payload
Attribute(s) Possible values
index integer [index of list item that has been selected]
Example:
<taoEvent Name="stimulus" Type="LISTBOX_SELECTED" Time="207018"> index=0</taoEvent>
To view example click on "Websearch" in "Bookmarks" pop-up
COMBOBOX A combobox item has been selected.
Payload
Attribute(s) Possible values
id string [identifier of combobox]
index integer [index of combobox item that has been selected]
Example:
<taoEvent Name="stimulus" Type="COMBOBOX" Time="22181"> id=u021_default_menu2|*$index=2</taoEvent>
View Example
MAIL_DRAG Mail that has been dragged.
Payload
Attribute(s) Possible values
id string [mail identifier]
Example:
<taoEvent Name="stimulus" Type="MAIL_DRAG" Time="852693"> id=u02_item101</taoEvent>
Triggered event(s):
MAIL_DROP
MAIL_DROP Target folder in which mail has been dropped.
Payload
Attribute(s) Possible values
target string [identifier of folder the mail has been moved to]
Example:
<taoEvent Name="stimulus" Type="MAIL_DROP" Time="20186"> target=u01a_CanComeFolder</taoEvent>
Event trigger:
MAIL_DRAG
Triggered event(s):
MAIL_MOVED
FOLDER_FOLDED Folder has been folded.
Payload
Attribute(s) Possible values
id string [identifier of folder that has been folded]
Example:
<taoEvent Name="stimulus" Type="FOLDER_FOLDED" Time="6830">id=u12_forms</taoEvent>
View Example
FOLDER_UNFOLDED Folder has been unfolded.
Payload
Attribute(s) Possible values
id string [identifier of folder that has been unfolded]
Example:
<taoEvent Name="stimulus" Type="FOLDER_UNFOLDED" Time="4202"> id=u12_division</taoEvent>
View Example
SHORTCUT A shortcut has been used (combination of KEYPRESS EVENTS to trigger the EVENT “COPY” or “PASTE”).
Payload
Attribute(s) Possible values
modifiers string [modifier key pressed]
key string [key pressed]
Example:
<taoEvent Name="stimulus" Type="SHORTCUT" Time="45591"> modifiers=ctrl|*$key=v</taoEvent>
Triggered event(s):
COPY
PASTE
Event trigger:
KEYPRESS
Comment:
This event implies a user interaction.
Event category: Action [System actions triggered by respondent’s interaction events]
DOACTION System event activated by respondent’s interaction event.
Payload
Attribute(s) Possible values
action string [action script commands]
e.g.: as://hide(sortwindow),
as://moveTo(mailview,movetree)
Example:
<taoEvent Name="stimulus" Type="DOACTION" Time="63231"> action=as://hide(sortwindow)</taoEvent>
Event trigger:
TOOLBAR
TAB
BUTTON
COPY
PASTE
View Example
HISTORY_NEXT Page visited when respondent has clicked on NEXT icon in the toolbar.
Payload
Attribute(s) Possible values
pageid string [page identifier]
title string [page title]
url string [page url]
Example:
<taoEvent Name="stimulus" Type="HISTORY_NEXT" Time="158481"> pageid=unit02page1 |*$title=View Calendar |*$url= http://enderson.com/reservations/vc</taoEvent>
Triggered event(s):
HISTORY_ADD
Event trigger:
TOOLBAR
View Example
HISTORY_BACK Page visited when respondent has clicked on NEXT icon in the toolbar.
Payload
Attribute(s) Possible values
pageid string [page identifier]
title string [page title]
url string [page url]
Example:
<taoEvent Name="stimulus" Type="HISTORY_BACK" Time="155020"> pageid=unit02page5 |*$title=Complete Unfilled Request Notice |*$url =http://enderson.com/reservations/nur </taoEvent>
Triggered event(s):
HISTORY_ADD
Event trigger:
TOOLBAR
View Example
HISTORY_ADD A page has been added to the history.
Payload
Attribute(s) Possible values
pageid string [page identifier]
title string [page title]
url string [page url]
Example:
<taoEvent Name="stimulus" Type="HISTORY_ADD" Time="302135"> pageid=unit02page1 |*$title=View Calendar|*$url =http://enderson.com/reservations/vc </taoEvent>
Event trigger:
HISTORY_NEXT
HISTORY_BACK
BOOKMARK_VIEWED
TEXTLINK
View Example
BOOKMARK_ADD Bookmark that has been added.
Payload
Attribute(s) Possible values
pageid string [page identifier]
title string [page title]
url string [page url]
Example:
<taoEvent Name="stimulus" Type="BOOKMARK_ADD" Time="647336"> pageid=unit02page2 |*$title=View Meeting Room Details|*$url =http://enderson.com/reservations/mrd </taoEvent>
Triggered event(s):
DOACTION
Event trigger:
MENUITEM
TOOLBAR
BUTTON
View Example
BOOKMARK_VIEWED Bookmark that has been viewed.
Payload
Attribute(s) Possible values
pageid string [page identifier]
title string [page title]
url string [page url]
Example:
<taoEvent Name="stimulus" Type="BOOKMARK_VIEWED" Time="207018"> pageid=unit02page1|*$title=View Calendar|*$url =http://enderson.com/reservations/vc </taoEvent>
Triggered event(s):
HISTORY_ADD
Event trigger:
LISTBOX_SELECTED
View Example
MAIL_MOVED System action executing a moving mail event.
Payload
Attribute(s) Possible values
id string [mail identifier]
target string [identifier of folder the mail has been moved to]
Example:
<taoEvent Name="stimulus" Type="MAIL_MOVED" Time="164084"> id=u01a_item103|*$target=MTGROOMFOLDER</taoEvent>
Triggered event(s):
DOACTION
Event trigger:
MENUITEM
MAIL_DROP
View Example
MAIL_VIEWED Message has been viewed.
Payload
Attribute(s) Possible values
id string [mail identifier]
Example:
<taoEvent Name="Stimulus" Type="MAIL_VIEWED" Time="237327"> id=u01a_item301</taoEvent>
Comment:
This event implies a user interaction.
View Example
MAIL_SENT Message has been sent.
Payload
Attribute(s) Possible values
function string [mailing mode]
to string [mail receiver]
subject string [mail subject]
message string [mail message]
Example:
<taoEvent Name="stimulus" Type="MAIL_SENT" Time="87550"> function=reply|*$to=Bill Yin|*$cc=|*$subject =RE: CD question |*$message=Yes%2E%20we%20have%2
0two%2E%20Essentials
%20and%20Tartello%0D
%0D%2D%2D%2D%2D%2D%2
D%2D%2D%2D%2D%2D%2D%
2D%2D%2D%2D%2D%2D%2D
%2D%0D%0DI%20am%20lo
oking%20for%20a%20CD
%20by%20a%20classica
l%20musician%20named
%20Martinessa%2E%20%
20Do%20you%20have%20
any%20of%20her%20CDs
%3F%0D%0DThank%20you%2E</taoEvent>

Event trigger:
TOOLBAR
View Example
MAIL_DELETED Mail has been deleted.
Payload
Attribute(s) Possible values
id string [mail identifier]
Example:
<taoEvent Name="stimulus" Type="MAIL_DELETED" Time="921307"> id=myMails</taoEvent>
Event trigger:
MENUITEM
View Example
FOLDER_VIEWED Mail folder that has been viewed.
Payload
Attribute(s) Possible values
id string [folder identifier]
Example:
<taoEvent Name="Stimulus" Type="FOLDER_VIEWED" Time="270543"> id=SentFolder</taoEvent>
Comment:
This event implies a user interaction.
View Example
NEW_FOLDER New folder has been created.
Payload
Attribute(s) Possible values
id string [folder identifier]
Example:
<taoEvent Name="stimulus" Type="NEW_FOLDER" Time="90661"> target=u01a_myMails|*$name=New Folder</taoEvent>
Triggered event(s):
DOACTION
Event trigger:
MENUITEM
TOOLBAR
BUTTON
View Example
COPY Text has been copied.
Payload
Attribute(s) Possible values
content string [copied text]
Example:
<taoEvent Name="stimulus" Type="COPY" Time="312997"> content=text</taoEvent>
Triggered event(s):
TEXTBOX_ONFOCUS
TEXTBOX_KILLFOCUS
Event trigger:
MENUITEM
SHORTCUT
View Example
PASTE A copied text has been pasted into a textbox. The following TEXTBOX_KILLFOCUS event will indicate the textbox in which the text is pasted.
Payload
Attribute(s) Possible values
content string [copied text]
Example:
<taoEvent Name="stimulus" Type="PASTE" Time="94170">content=The next Facilities Department meeting will be on March 16th from 11:00 - 1:00. I'd like to reserve a room for that date if one is available. Sorry for the late notice.</taoEvent>
Triggered event(s):
TEXTBOX_ONFOCUS
TEXTBOX_KILLFOCUS
Event trigger:
MENUITEM
SHORTCUT
View Example
SS_SORT Spreadsheet column(s) has/have been sorted.
Payload
Attribute(s) Possible values
id string [identifier of button that has been clicked]
id string [spreadsheet identifier]
sortby1 string [identifier of column that is sorted]
order1 string [mode of sorting]
sortby2 string [identifier of column that is sorted]
order2 string [mode of sorting]
sortby3 string [identifier of column that is sorted]
order3 string [mode of sorting]
Example:
<taoEvent Name="stimulus" Type="SS_SORT" Time="111152"> id=spreadview|*$sortby1=spreadSheet_colB |*$order1=ASCENDING|*$sortby2=spreadSheet_colA |*$order2=ASCENDING|*$sortby3=spreadSheet_colD |*$order3=DESCENDING</taoEvent>
Triggered event(s):
DOACTION
Event trigger:
MENUITEM
TOOLBAR
BUTTON
View Example
MC_SORT Mail list has been sorted.
Payload
Attribute(s) Possible values
sortby string [identifier of column that is sorted]
order string [mode of sorting]
Example:
<taoEvent Name="stimulus" Type="MC_SORT" Time="70615"> sortby=from|*$order=ASC</taoEvent>
Triggered event(s):
DOACTION
Event trigger:
MENUITEM
BUTTON
View Example
SS_SEARCH Keyword has been searched in a spreadsheet.
Payload
Attribute(s) Possible values
keyword string [keyword used for search]
nboresults string [number of results]
Example:
<taoEvent Name="stimulus" Type="SS_SEARCH" Time="36887"> keyword=Martinessa|*$nbofresults=2</taoEvent>
Triggered event(s):
DOACTION
Event trigger:
BUTTON
View Example
MC_SEARCH Keyword has been searched in a mail client.
Payload
Attribute(s) Possible values
keyword string [keyword used for search]
nboresults string [number of results]
Triggered event(s):
DOACTION
Event trigger:
BUTTON
View Example
BUTTON A button has been pressed.
Payload
Attribute(s) Possible values
id string [identifier of button that has been clicked]
Example:
<taoEvent Name="stimulus" Type="BUTTON" Time="63231">id=sortValidation</taoEvent>
Triggered event(s):
DOACTION
View Example (occurs in many items)
Event category: Unit specific actions

Back to top

Unit 2
SUBMIT_RESERVATION_SUCCESS The “Submit” button on page “Make Room reservation” has been clicked with correct selection of the comboboxes was.
The payload is subsuming all choices of this page’s comboboxes.
Payload
Attribute(s) Possible values
room_index integer [index of combobox item that has been selected]
start_time_index integer [index of combobox item that has been selected]
end_time_index integer [index of combobox item that has been selected]
department_index integer [index of combobox item that has been selected]

Example:
<taoEvent Name="stimulus" Type="SUBMIT_RESERVATION_SUCCESS" Time="97222"> room_index=2|*$start_time_index=4 |*$end_time_index=5 |*$department_index=1</taoEvent>
Event trigger:
BUTTON
View Example
SUBMIT_RESERVATION_FAILURE The “Submit” button on page “Make Room reservation” has been clicked with a combination of comboboxes’ values causing a conflict.
Payload
Attribute(s) Possible values
reason conflict [reason of failure]
field missing[missing value(s) of combobox(es)]

Example:
<taoEvent Name="stimulus" Type=SUBMIT_RESERVATION_FAILURE" Time="887451"> reason=conflict</taoEvent>
Event trigger:
BUTTON
View Example
DELETE_RESERVATION Clicking on a new reservation on the “View calendar” page will lead to a page with “Delete” button. The event is captured when this “Delete” button is clicked.
Payload
Attribute(s) Possible values
room_index integer [index of combobox item that has been selected]
start_time_index integer [index of combobox item that has been selected]
end_time_index integer [index of combobox item that has been selected]
department_index integer [index of combobox item that has been selected]

Example:
<taoEvent Name="stimulus" Type="DELETE_RESERVATION" Time="97222"> room_index=2|*$start_time_index=4 |*$end_time_index=5 |*$department_index=1</taoEvent>
Event trigger:
BUTTON
Unit 6b
INFORMATION A value has been selected outside the stimulus.
Payload
Attribute(s) Possible values
index integer [index of drop down list item that has been selected]

Example:
<taoEvent Name="service" Type="INFORMATION" Time="8126"> index=3</taoEvent>
Event trigger:
menuPopupChange
View Example
GLOBAL_VAR A value has been selected (in this case a website) and will be needed in another part of the unit.
Payload
Attribute(s) Possible values
website string [id of website]

Example:
<taoEvent Name="service" Type="GLOBAL_VAR" Time="12512"> website=3</taoEvent>
Event trigger:
INFORMATION
View Example
TRANSLATION The translation of specific texts is provided for verification (automatic comparison) to allow the scoring.
Payload
Attribute(s) Possible values
address string [translation of the selected website item in the drop down list]

Example:
<taoEvent Name="service" Type="TRANSLATION" Time="8127"> address=feelbetter</taoEvent>
Event trigger:
GLOBAL_VAR
View Example
Unit 16
TRANSLATION The translation of specific texts is provided for verification (automatic comparison) to allow the scoring.
Payload
Attribute(s) Possible values
address string [translation of the address to be sent]
name1 string [translation of name of email receiver]
mail1 string [translation of email address]
name2 string [translation of name of email receiver]
mail2 string [translation of email address]
name3 string [translation of name of email receiver]
mail3 string [translation of email address]

Example:
<taoEvent Name="service" Type="TRANSLATION" Time="762">address=334 Elmwood Avenue, Northfield, MO 64184 |*$name1=Emily Hua|*$mail1=emi@piaac.org |*$name2=Kevin Ames|*$mail2=kev@school.net |*$name3=Maria Taylor|*$mail3=mt@myhome.org</taoEvent>
Event trigger:
START
Event category: Frame actions [actions triggered by respondent’s interaction events outside the stimulus]
menuPopupChange A value has been selected outside the stimulus.
Payload
Attribute(s) Possible values
id string [identifier of drop down list]
newIndex integer [index of drop down list item that has been selected]

Example:
<taoEvent Name="taoPIAAC" Type="menuPopupChange" Time="8126"> id=u06b_menupopup1|$*newIndex=3</taoEvent>
Event trigger:
START
Event category:events available outside the stimulus

Back to top

Event Type Description
RADIO_BTN A radio button has been pressed.
Payload
Attribute(s) Possible values
id string [radio button identifier]
Example:
<taoEvent Name="taoPIAAC" Type="RADIO_BTN" Time="32150">id=radio_1</taoEvent>
Comment:
This event implies a user interaction.
CHECKBOX A check box has been pressed.
Payload
Attribute(s) Possible values
id string [check box identifier]
Example:
<taoEvent Name="taoPIAAC" Type="CHECKBOX" Time="39371">id=check_4</taoEvent>
Comment:
This event implies a user interaction.
TEXTBOX_ONFOCUS A text box (input field) received the focus.
Payload
Attribute(s) Possible values
id string [text box identifier]
value string [encoded text located in textbox]
Example:
<taoEvent Name="taoPIAAC" Type="TEXTBOX_ONFOCUS" Time="3371"> id=txt_2|$*value=text</taoEvent>
Comment:
This event implies a user interaction.
View Example
TEXTBOX_KILLFOCUS A text box (input field) lost the focus.
Payload
Attribute(s) Possible values
id string [text box identifier]
value string [encoded text located in textbox]
Example:
<taoEvent Name="taoPIAAC" Type="TEXTBOX_KILLFOCUS" Time="3371"> id=txt_2|$*value=123</taoEvent>
Comment:
This event implies a user interaction.
View Example
BUTTON A button has been pressed.
Payload
Attribute(s) Possible values
id string [button identifier]
Example:
<taoEvent Name="taoPIAAC" Type="BUTTON" Time="741"> id=btn_validation</taoEvent>
Comment:
This event implies a user interaction.
Examples can be viewed in all PS items
DOACTION A programmatic function has been triggered.
Payload
Attribute(s) Possible values
action string [name of the called function]
Example:
<taoEvent Name="taoPIAAC" Type="DOACTION" Time="6012"> action=stopTimer</taoEvent>
Comment:
This event implies a user interaction or a software invocation.
Examples can be viewed in all PS items
COMBOBOX A combo box (drop down listbox) has been opened or closed.
Payload
Attribute(s) Possible values
id string [combo box identifier]
action string {OPEN or CLOSE}
Example:
<taoEvent Name="taoPIAAC" Type="COMBOBOX" Time="6901"> id=cbb_2|$*action=OPEN</taoEvent>
Comment:
This event implies a user interaction.
View Example
COMBOBOX An element contained in a combo box has been selected.
Payload
Attribute(s) Possible values
id string [text box identifier]
index integer [selected row number; first=0]
Example:
<taoEvent Name="taoPIAAC" Type="COMBOBOX" Time="7045"> id=cbb_2|$*index=3</taoEvent>
Comment:
This event implies a user interaction.
View Example
NEXT_BUTTON A NEXT button has been pressed.
Payload
Attribute(s) Possible values
id string [button identifier]
Example:
<taoEvent Name="taoPIAAC" Type="NEXT_BUTTON" Time="20041"> id=next_button</taoEvent>
Comment:
This event implies a user interaction.
Examples can be viewed in all PS items
START or RESTART A START action is issued at opening of a unit. RESTART comes after a crash recovery.
Payload
Attribute(s) Possible values
TEST_TIME integer [time elapsed since beginning of the test in milliseconds]
Example:
<taoEvent Name="taoPIAAC" Type="START" Time="41"> TEST_TIME=23378</taoEvent>
Comment:
automatic event
END An END action is issued at the closing of a unit.
Payload
Attribute(s) Possible values
END N.A.
Example:
<taoEvent Name="taoPIAAC" Type="END" Time="25554">END</taoEvent>
Comment:
automatic event
PREVIOUS_INQUIRY A PREVIOUS for inquiry (ITEM) button has been pressed.
Payload
Attribute(s) Possible values
REQUEST N.A.
Example:
<taoEvent Name="taoPIAAC" Type="PREVIOUS_INQUIRY" Time="25554"> REQUEST</taoEvent>
Comment:
This event implies a user interaction.
Examples can be viewed in all PS items
NEXT_INQUIRY A NEXT for inquiry (ITEM) button has been pressed.
Payload
Attribute(s) Possible values
REQUEST N.A.
Example:
<taoEvent Name="taoPIAAC" Type="NEXT_INQUIRY" Time="25554">REQUEST</taoEvent>
Comment:
This event implies a user interaction.
Examples can be viewed in all PS items
PREVIOUS_ITEM A PREVIOUS for item (UNIT) button has been pressed.
Payload
Attribute(s) Possible values
REQUEST N.A.
Example:
<taoEvent Name="taoPIAAC" Type="PREVIOUS_ITEM" Time="25554">REQUEST</taoEvent>
Comment:
This event implies a user interaction.
Examples can be viewed in all PS items
NEXT_ITEM A NEXT for item (UNIT) button has been pressed.
Payload
Attribute(s) Possible values
REQUEST N.A.
Example:
<taoEvent Name="taoPIAAC" Type="NEXT_ITEM" Time="8824">REQUEST</taoEvent>
Comment:
This event implies a user interaction.
Examples can be viewed in all PS items
GET_HELP A HELP button has been pressed.
Payload
Attribute(s) Possible values
REQUEST N.A.
Example:
<taoEvent Name="taoPIAAC" Type="GET_HELP" Time="2570">REQUEST</taoEvent>
Comment:
This event implies a user interaction.
Examples can be viewed in all PS items
BREAKOFF A BREAKOFF action has been requested.
Payload
Attribute(s) Possible values
REQUEST N.A.
Example:
<taoEvent Name="taoPIAAC" Type="BREAKOFF" Time="554">REQUEST</taoEvent>
Comment:
This event implies a user interaction.

Booklet Order of the cognitive assessment by domain

For an explanation of the assessment design please refer to the official OECD website and the corresponding publications.

Within the domains Literacy and Numeracy, there are three booklets (testlets) in stage 1 and four booklets in stage 2. For Problem Solving there are 2 booklets in total.
For more information about items and item maps in different domains, see the OECD´s Reader´s Companion.

Literacy: Stage 1 Testlet 1 Literacy: Stage 1 Testlet 2 Literacy: Stage 1 Testlet 3
CBA Sequence Item Name CBA Sequence Item Name CBA Sequence Item Name
CBA-L11: 1
Unit 1 Question 1/1
311 Dutch Women CBA-L12: 1
Unit 1 Question 1/1
315 Mexican Cities CBA-L13: 1
Unit 1 Question 1/1
315 Mexican Cities
CBA-L11: 2
Unit 2 Question 1/2
321 Internet Poll CBA-L12: 2
Unit 2 Question 1/4
308 Baltic Stock Market CBA-L13: 2
Unit 2 Question 1/2
304 Contact Employer
CBA-L11: 3
Unit 2 Question 2/2
321 Internet Poll CBA-L12: 3
Unit 2 Question 2/4
308 Baltic Stock Market CBA-L13: 3
Unit 2 Question 2/2
304 Contact Employer
CBA-L11: 4
Unit 3 Question 1/4
308 Baltic Stock Market CBA-L12: 4
Unit 2 Question 3/4
308 Baltic Stock Market CBA-L13: 4
Unit 3 Question 1/2
308 Baltic Stock Market
CBA-L11: 5
Unit 3 Question 2/4
308 Baltic Stock Market CBA-L12: 5
Unit 2 Question 4/4
308 Baltic Stock Market CBA-L13: 5
Unit 3 Question 2/2
308 Baltic Stock Market
CBA-L11: 6
Unit 3 Question 3/4
308 Baltic Stock Market CBA-L12: 6
Unit 3 Question 1/2
305 TMN AntiTheft CBA-L13: 6
Unit 4 Question 1/4
327 Summer Streets
CBA-L11: 7
Unit 3 Question 4/4
308 Baltic Stock Market CBA-L12: 7
Unit 3 Question 2/2
305 TMN AntiTheft CBA-L13: 7
Unit 4 Question 2/4
327 Summer Streets
CBA-L11: 8
Unit4 Question 1/2
305 TMN AntiTheft CBA-L12: 8
Unit 4 Question 1/2
304 Contact Employer CBA-L13: 8
Unit 4 Question 3/4
327 Summer Streets
CBA-L11: 9
Unit 4 Question 2/2
305 TMN AntiTheft CBA-L12: 9
Unit 4 Question 2/2
304 Contact Employer CBA-L13: 9
Unit 4 Question 4/4
327 Summer Streets

Literacy: Stage 2 Testlet 1 Literacy: Stage 2 Testlet 2 Literacy: Stage 2 Testlet 3 Literacy: Stage 2 Testlet 4
CBA Sequence Item Name CBA Sequence Item Name CBA Sequence Item Name CBA Sequence Item Name
CBA-L21: 1
Unit 5
Question 1/2
307 Medco CBA-L22: 1
Unit 5
Question 1/4
322 Lakeside Fun Run CBA-L23: 1
Unit 5
Question 1/2
310 Memory Training CBA-L24: 1
Unit 5
Question 1/2
306 CANCO
CBA-L21: 2
Unit 5
Question 2/2
307 Medco CBA-L22: 2
Unit 5
Question 2/4
322 Lakeside Fun Run CBA-L23: 2
Unit 5
Question 2/2
310 Memory Training CBA-L24: 2
Unit 5
Question 2/2
306 CANCO
CBA-L21: 3
Unit 6
Question 1/4
309 Generic Medicine CBA-L22: 3
Unit 5
Question 3/4
322 Lakeside Fun Run CBA-L23: 3
Unit 6
Question 1/2
322 Lakeside Fun Run CBA-L24: 3
Unit 6
Question 1/2
318 Civil Engineering
CBA-L21: 4
Unit 6
Question 2/4
309 Generic Medicine CBA-L22: 4
Unit 5
Question 4/4
322 Lakeside Fun Run CBA-L23: 4
Unit 6
Question 2/2
322 Lakeside Fun Run CBA-L24: 4
Unit 6
Question 2/2
318 Civil Engineering
CBA-L21: 5
Unit 6
Question 3/4
309 Generic Medicine CBA-L22: 5
Unit 6
Question 1/2
309 Generic Medicine CBA-L23: 5
Unit 7
Question 1/2
306 Canco CBA-L24: 5
Unit 7
Question 1/3
313 International Calls
CBA-L21: 6
Unit 6
Question 4/4
309 Generic Medicine CBA-L22: 6
Unit 6
Question 2/2
309 Generic Medicine CBA-L23: 6
Unit 7
Question 2/2
306 Canco CBA-L24: 6
Unit 7
Question 2/3
313 International Calls
CBA-L21: 7
Unit 7
Question 1/3
322 Lakeside Fun Run CBA-L22: 7
Unit 7
Question 1/2
310 Memory Training CBA-L23: 7
Unit 8
Question 1/3
313 International Calls CBA-L24: 7
Unit 7
Question 3/3
313 International Calls
CBA-L21: 8
Unit 7
Question 2/3
322 Lakeside Fun Run CBA-L22: 8
Unit 7
Question 2/2
310 Memory Training CBA-L23: 8
Unit 8
Question 2/3
313 International Calls CBA-L24: 8
Unit 8
Question 1/2
329 Work-related Stress
CBA-L21: 9
Unit 7
Question 3/3
322 Lakeside Fun Run CBA-L22: 9
Unit 8
Question 1/3
320 Discussion Forum CBA-L23: 9
Unit 8
Question 3/3
313 International Calls CBA-L24: 9
Unit 8
Question 2/2
329 Work-related Stress
CBA-L21: 10
Unit 8
Question 1/2
313 International Calls CBA-L22: 10
Unit 8
Question 2/3
320 Discussion Forum CBA-L23: 10
Unit 9
Question 1/2
323 Library Search CBA-L24: 10
Unit 9
Question 1/2
323 Library Search
CBA-L21: 11
Unit 8
Question 2/2
313 International Calls CBA-L22: 11
Unit 8
Question 3/3
320 Discussion Forum CBA-L23: 11
Unit 9
Question 2/2
323 Library Search CBA-L24: 11
Unit 9
Question 2/2
323 Library Search
Back to top
Numeracy: Stage 1 Testlet 1 Numeracy: Stage 1 Testlet 2 Numeracy: Stage 1 Testlet 3
CBA Sequence Item Name CBA Sequence Item Name CBA Sequence Item Name
CBA-N11: 1
Unit 1 Question 1/2
615 Candles CBA-N12: 1
Unit 1 Question 1/1
604 Gas Gauge CBA-N13: 1
Unit 1 Question 1/2
623 Wine
CBA-N11: 2
Unit 1 Question 2/2
615 Candles CBA-N12: 2
Unit 2 Question 1/3
605 Photo CBA-N13: 2
Unit 1 Question 2/2
623 Wine
CBA-N11: 3
Unit 2 Question 1/2
624 BMI CBA-N12: 3
Unit 2 Question 2/3
605 Photo CBA-N13: 3
Unit 2 Question 1/1
657 Package
CBA-N11: 4
Unit 2 Question 2/2
624 BMI CBA-N12: 4
Unit 2 Question 3/3
605 Photo CBA-N13: 4
Unit 3 Question 1/1
619 Tiles
CBA-N11: 5
Unit 3 Question 1/1
604 Gas Gauge CBA-N12: 5
Unit 3 Question 1/1
650 Urban Population CBA-N13: 5
Unit 4 Question 1/2
632 Educational Level
CBA-N11: 6
Unit 4 Question 1/3
605 Photo CBA-N12: 6
Unit 4 Question 1/2
623 Wine CBA-N13: 6
Unit 4 Question 2/2
632 Educational Level
CBA-N11: 7
Unit 4 Question 2/3
605 Photo CBA-N12: 7
Unit 4 Question 2/2
623 Wine CBA-N13: 7
Unit 5 Question 1/1
646 Rug Production
CBA-N11: 8
Unit 4 Question 3/3
605 Photo CBA-N12: 8
Unit 5 Question 1/1
657 Package CBA-N13: 8
Unit 6 Question 1/2
620 Inflation
CBA-N11: 9
Unit 5 Question 1/1
650 Urban Population CBA-N12: 9
Unit 6 Question 1/1
619 Tiles CBA-N13: 9
Unit 6 Question 2/2
620 Inflation

Numeracy: Stage 2 Testlet 1 Numeracy: Stage 2 Testlet 2 Numeracy: Stage 2 Testlet 3 Numeracy: Stage 2 Testlet 4
CBA Sequence Item Name CBA Sequence Item Name CBA Sequence Item Name CBA Sequence Item Name
CBA-N21: 1
N11:Unit 6
N12,N13: Unit 7 Question 1/1
613 Logbook CBA-N22: 1
N11:Unit 6
N12,N13: Unit 7 Question 1/1
655 Path CBA-N23: 1
N11:Unit 6
N12,N13: Unit 7 Question 1/1
622 Classified CBA-N24: 1
N11:Unit 6
N12,N13: Unit 7 Question 1/2
660 Weighthistory
CBA-N21: 2
Unit 7(8) Question 1/1
614 Watch CBA-N22: 2
Unit 7(8) Question 1/3
602 PriceTag CBA-N23: 2
Unit 7(8) Question 1/2
665 Coopertest CBA-N24: 2
N11:Unit 6
N12,N13: Unit 7 Question 2/2
660 Weighthistory
CBA-N21: 3
Unit 8(9)
Question 1/2
618 SixPack1 CBA-N22: 3
Unit 7(8)
Question 2/3
602 PriceTag CBA-N23: 3
Unit 7(8)
Question 2/2
665 Coopertest CBA- N24: 3
Unit 7(8)
Question 1/1
641 Amoeba
CBA-N21: 4
Unit 8(9)
Question 2/2
618 SixPack1 CBA-N22: 4
Unit 7(8)
Question 3/3
602 PriceTag CBA-N23: 4
Unit 8(9)
Question 1/1
636 LabReport CBA-N24: 4
Unit 8(9)
Question 1/2
661 Studyfees
CBA-N21: 5
Unit 9(10)
Question 1/1
635 ParkingMap CBA-N22: 5
Unit 8(9)
Question 1/1
608 Tree CBA-N23: 5
Unit 9(10)
Question 1/2
617 Map CBA-N24: 5
Unit 8(9)
Question 2/2
661 Studyfees
CBA-N21: 6
Unit 10(11)
Question 1/1
607 TV CBA-N22: 6
Unit 9(10)
Question 1/1
606 Solution CBA-N23: 6
Unit 9(10)
Question 2/2
617 Map CBA-N24: 6
Unit 9(10)
Question 1/1
612 Dioxin (MOD)
CBA-N21: 7
Unit 11(12)
Question 1/1
655 Path CBA-N22: 7
Unit 10(11)
Question 1/2
611 TempScale CBA-N23: 7
Unit 10(11)
Question 1/2
660 Weighthistory CBA- N24: 7
Unit 10(11)
Question 1/1
651 Fertilizer
CBA-N21: 8
Unit 12(13)
Question 1/3
602 PriceTag CBA-N22: 8
Unit 10(11)
Question 2/2
611 TempScale CBA-N23: 8
Unit 10(11)
Question 2/2
660 Weighthistory CBA -N24: 8
Unit 11 (12)
Question 1/1
664 Orchestratickets
CBA-N21: 9
Unit 12(13)
Question 2/3
602 PriceTag CBA-N22: 9
Unit 11(12)
Question 1/1
622 Classified CBA-N23: 9
Unit 11(12)
Question 1/1
641 Amoeba CBA- N24: 9
Unit 12(13)
Question 1/2
634 Peanuts
CBA-N21: 10
Unit 12(13)
Question 3/3
602 PriceTag CBA-N22: 10
Unit 12(13)
Question 1/2
665 Coopertest CBA-N23: 10
Unit 12(13)
Question 1/2
661 Studyfees CBA- N24: 10
Unit 12(13)
Question 2/2
634 Peanuts
CBA-N21: 11
Unit 13(14)
Question 1/1
608 Tree CBA-N22: 11
Unit 12(13)
Question 2/2
665 Coopertest CBA-N23: 11
Unit 12(13)
Question 2/2
661 Studyfees CBA- N24: 11
Unit 13(14)
Question 1/1
644 NZExports
Back to top
Problem Solving: Part1 Problem Solving: Part2
CBA Sequence Unit Number Task Name CBA Sequence Unit Number Task Name
PS-M1: 1
Unit 1
01a Party Invitations PS-M2: 1
Unit 1
19a Club Membership
PS-M1: 2
Unit 1
01b Party Invitations PS-M2: 2
Unit 1
19b Club Membership
PS-M1: 3
Unit 2
03a CD Tally PS-M2: 3
Unit 2
07 Book Order
PS-M1: 4
Unit 3
06a Sprained Ankle PS-M2: 4
Unit 3
02 Meeting Room
PS-M1: 5
Unit 3
06b Sprained Ankle PS-M2: 5
Unit 4
16 Reply All
PS-M1: 6
Unit 4
21 Tickets PS-M2: 6
Unit 5
11b Locate Email
PS-M1: 7
Unit 5
04a Class Attendance PS-M2: 7
Unit 6
23 Lamp Return
Back to top