PDL Quiz

Generate an image depicting a digital interface with coding symbols, focusing on data flow, updates, and user interaction, reflecting the theme of PDL and research methodology.

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

14 Questions4 MinutesCreated by CodingWizard42

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!

LEGEND:
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

Don't know

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

LEGEND:
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

Don't know

Syntax : [educ] {pdl-update educ}

The above PDL will be always asked?

Yes

Only if it doesn't have answer in Datum

[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 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)

In the end the respondent will have in the Gryphon database & Datum:

[birthyear if not pdl.birthyear] {pdl-update birthyear}

[age if 0] {open-int} 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

In the end the respondent will have in the Gryphon database & Datum:

[birthyear if not pdl.birthyear] {pdl-update birthyear}

[age if 0] {open-int} age

{
if pdl.age: age.set(pdl.age)
}

LEGEND:
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:

[birthyear if not pdl.birthyear] {pdl-update birthyear}

[age if 0] {open-int} age

{
if pdl.age: age.set(pdl.age)
}

LEGEND:
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:

10.

LEGEND:
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}

[birthyear if not pdl.birthyear] {pdl-update birthyear}
[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)
}

[birthyear if not pdl.birthyear] {pdl-update birthyear}
[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

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

PDL Quiz

PDL Knowledge Assessment

More Quizzes