PDL Quiz
PDL Knowledge Assessment
Test your understanding of PDL (Panel Data Language) with this comprehensive quiz. Designed for those in the research and data fields, it assesses your knowledge through a series of questions ranging from syntax usage to PDL updates.
Here’s what you can expect:
- Multiple choice questions
- Immediate scoring
- Insightful feedback on your knowledge level
Welcome to PDL Quiz
You have 60 seconds for answering to a question. If the time passed, then you'll be autosubmitted to the next question.
Pay attention to the selected response, because if you click it, you will be autosubmitted to the next question, without the possibility to change the answer.
Good luck!
6.
LEGEND:
sample internal, birthyear is already fully populated.
Syntax : [birthyear if not pdl.birthyear] {pdl-update birthyear}
sample internal, birthyear is already fully populated.
Syntax : [birthyear if not pdl.birthyear] {pdl-update birthyear}
Will be birthyear asked once the respondent gets to the above line in the script?
Yes
No
Don't know
7.
Syntax : [birthyear if 0] {pdl-update birthyear}
The above syntax will be executed :
When respondent gets to the above line in the script
When respondent access the Gryphon link
Both of the above
Don't know
8.
LEGEND:
sample internal, educ is not fully populated.
Syntax : [educ if 0] {pdl-update educ}
sample internal, educ is not fully populated.
Syntax : [educ if 0] {pdl-update educ}
Will be "educ" asked when respondent gets to the above line in the script?
Yes
No
Don't know
9.
Syntax : [educ] {pdl-update educ}
The above PDL will be always asked?
Yes
No
Only if it doesn't have answer in Datum
1.
[age if 0] {pdl-update age}
[birthyear] {pdl-update birthyear}
LEGEND:
age is a computed pdl after panelist's birthyear
pdl.age==16 already set in Datum.
he now enters: birthyear=1988 (31 years).
In the end the respondent will have in the Gryphon database & Datum:
Age = 31, pdl.age = 16
Age = 16, pdl.age = 31
Age = 16, pdl.age = 16
Age = 31, pdl.age = 31
None of these
2.
[age if 0] {pdl-update age}
[birthyear] {pdl-update birthyear}
LEGEND:
age is a computed pdl after birthyear
non-panelist on the link, he enters: birthyear=1988 (31 years)
age is a computed pdl after birthyear
non-panelist on the link, he enters: birthyear=1988 (31 years)
In the end the respondent will have in the Gryphon database & Datum:
Age = 31, pdl.age = null
Age = null, pdl.age = 31
Age = null, pdl.age = null
Age = 31, pdl.age = 31
None of these
3.
[birthyear if not pdl.birthyear] {pdl-update birthyear}
[age if 0] {open-int} age
{
if pdl.age: age.set(pdl.age)
}
{
if pdl.age: age.set(pdl.age)
}
LEGEND:
age is a computed pdl after birthyear
panelist, pdl.birthyear==1988, pdl.age==31 already set in Datum
age is a computed pdl after birthyear
panelist, pdl.birthyear==1988, pdl.age==31 already set in Datum
In the end the respondent will have in the Gryphon database & Datum:
Age = 31, pdl.age = null
Age = null, pdl.age = 31
Age = null, pdl.age = null
Age = 31, pdl.age = 31
None of these
4.
[birthyear if not pdl.birthyear] {pdl-update birthyear}
[age if 0] {open-int} age
{
if pdl.age: age.set(pdl.age)
}
{
if pdl.age: age.set(pdl.age)
}
LEGEND:
age is a computed pdl after birthyear
non-panelist
age is a computed pdl after birthyear
non-panelist
While the respondent is on the link, right after he gives birthyear=1988, he will have the following values:
Age = 31, pdl.age = null
Age = null, pdl.age = 31
Age = null, pdl.age = null
Age = 31, pdl.age = 31
None of these
5.
[birthyear if not pdl.birthyear] {pdl-update birthyear}
[age if 0] {open-int} age
{
if pdl.age: age.set(pdl.age)
}
{
if pdl.age: age.set(pdl.age)
}
LEGEND:
age is a computed pdl after birthyear
non-panelist, he sets birthyear=1988 (31years)
age is a computed pdl after birthyear
non-panelist, he sets birthyear=1988 (31years)
After he finishes the link, the respondent will have in Gryphon database & Datum:
Age = 31, pdl.age = null
Age = null, pdl.age = 31
Age = null, pdl.age = null
Age = 31, pdl.age = 31
None of these
10.
LEGEND:
sample internal and external, age is a computed PDL based on birthyear and it's required.
sample internal and external, age is a computed PDL based on birthyear and it's required.
What setup must be added in order for "age" to always be populated?
[birthyear if not pdl.birthyear] {pdl-update birthyear}
[age if 0] {pdl-update age}
[age if 0] {pdl-update age}
[birthyear if not pdl.birthyear] {pdl-update birthyear}
[age if 0] {pdl-update age}
{
if pdl.age : age.set(pdl.age)
}
[age if 0] {pdl-update age}
{
if pdl.age : age.set(pdl.age)
}
[birthyear if 0] {pdl-update birthyear}
[age if 0] {open-int}
{
if pdl.age : age.set(pdl.age)
}
[age if 0] {open-int}
{
if pdl.age : age.set(pdl.age)
}
[birthyear if not pdl.birthyear] {pdl-update birthyear}
[age if 0] {open-int}
{
if pdl.age : age.set(pdl.age)
}
[age if 0] {open-int}
{
if pdl.age : age.set(pdl.age)
}
None of these
11.
Datum definition:
[q11_PDL] {single} Zu welcher Berufsgruppe gehören Sie?
<1> Selbständige
<2> Freiberufler
<3> Leitende Angestellte
<12> Sonstiges [q11_Text] {open}
<777> keine Angabe
[q11_PDL] {single} Zu welcher Berufsgruppe gehören Sie?
<1> Selbständige
<2> Freiberufler
<3> Leitende Angestellte
<12> Sonstiges [q11_Text] {open}
<777> keine Angabe
How you're updating the above PDL?
[q11_PDL if 0] {pdl-update q11_PDL}
[q11_PDL] {pdl-update q11_PDL}
[q11_PDL, text_q11] {pdl-update q11_PDL}
[q11_PDL(q11_Text)] {pdl-update q11_PDL}
[q11_PDL, text_q11] {pdl-update q11_PDL, q11_Text}
Can't be updated
None of these
12.
What is your workaround when the researcher is asking you to make "PDL-update", but also to hide few items from it?
Adding in Gryphon the "pdl-update" syntax and hide the items in Datum platform
It can't be done and we will use hard question instead of PDL
It can't be done and we will inform the researcher that we're using the full definition of PDL, without hiding the items
None of these
13.
What is your workaround in adding "spd_category" for a PDL that doesn't have this tag in Datum and the researcher insists to have it in the study?
Adding "spd_category" tag in Datum for that PDL
It can't be done and we will inform the researcher about this
You're adding the "spd_category" tag inline with "pdl-update" syntax
You're using custom script(JS/jQuery) to add "spd_category" in standard "pdl-update" syntax
I don't know, it's the first time when I'm hearing about "spd_category" tag inside a PDL question
None of these
{"name":"PDL Quiz", "url":"https://www.quiz-maker.com/QPREVIEW","txt":"Test your understanding of PDL (Panel Data Language) with this comprehensive quiz. Designed for those in the research and data fields, it assesses your knowledge through a series of questions ranging from syntax usage to PDL updates.Here’s what you can expect:Multiple choice questionsImmediate scoringInsightful feedback on your knowledge level","img":"https:/images/course8.png"}
More Surveys
Data Intelligence Team Weekly Fair
9412
Background of Attendees
8419
Let's know more about you
4264
Excel Training
5229
Purchasing Document Menu Search Filter
3225
Shared tools
6320
Know about IoT
10521
CS FOLDER PROJECT
1589
Chart visualization 101
12621
Registaration Form for Certificate
12619
Aseptic Technique and Streaking Survey
4226
Safety Analyst Training
17833
Make your own Survey
- it's free to start.
- it's free to start.