1. Managing questions, instruments and discovery
Jon Johnson
5 December 2016
License: CC BY 4.0

2. Overview Getting your questions in
What question is the data based on and where did that question come from?
What questions are related to this one

3. Find yourself a DDI 3.x editor

4. Enter your questions

5. Assemble items, statements, filters

6. Linking Questions to data

7. A derived variable

8. Is made up of some variables

9. Each of which has a source question

10. Which came from a paper questionnaire
Which we can document with a URL to a PDF using the External Instrument Location element on Instrument

11. Often these aren’t new questions
Provenance of the questions is increasingly needed for publication
You will want to know if it was the same or varies from the original
If you are comparing questions from different studies
You need to know how they are different
And why they are different

12. AUDIT-PC was sourced from this battery
The Alcohol Use Disorders Identification Test Primary Care (AUDIT-PC) provides an adapted Primary Care version of the full AUDIT with questions 1, 2, 4, 5 and 10 of the AUDIT asked first. (2008, DH)

13. Documenting the source
Obviously this will be in the Technical Report - somewhere!
It would be useful if it was possible to see whether the questions asked were the same, differed slightly (or a lot) from the original
In the absence of the producer of the scale having documented this in DDI with a persistent URL …… we have to do it yourself .. or get your friendly Archive to do it.

14. <d:InstrumentScheme>
<r:URN>urn:ddi:uk.closer:closer_audit_pc-ins :1.0.0</r:URN>
<d:InstrumentSchemeName>
<r:String xml:lang="en-GB">closer_audit_pc_is01</r:String>
</d:InstrumentSchemeName>
<d:Instrument>
<r:URN>urn:ddi:uk.closer:closer_audit_pc-in :1.0.0</r:URN>
<d:InstrumentName>
<r:String xml:lang="en-GB">
Alcohol Use Disorders Identification Test - Primary Care (AUDIT-PC)
</r:String>
</d:InstrumentName>
<Description>
Provides an adapted Primary Care version of the full AUDIT with questions
1, 2, 4, 5 and 10 of the AUDIT asked first
</Description>
<ExternalInstrumentLocation>
</ExternalInstrumentLocation>
<d:ControlConstructReference>
<r:URN>urn:ddi:uk.closer:closer_audit_pc-se :1.0.0</r:URN>
<r:TypeOfObject>Sequence</r:TypeOfObject>
</d:ControlConstructReference>
</d:Instrument>
</d:InstrumentScheme>

15. What is the relationship between the two
Using the BasedOnObject property we can point to our ‘canonical’ instrument from the implemented instrument
Question Item used in Q32 is
<d:QuestionItem>
<r:URN> urn:ddi:uk.cls.bcs70:bcs9_sc-qi :1.0.0 </r:URN>
<d:LiteralText>
<d:Text>How often have you have a drink containing alcohol?</d:Text>
</d:LiteralText>
<BasedOnObject>
<BasedOnReference TypeofObject=”QuestionItem”
<r:URN>urn:ddi:uk.closer_audit_pc-1:1</r:URN>
<BasedOnReference
</BasedOnObject>
....
</d:QuestionItem>

16. Harmonised Questions

17. Pair-wise Mapping: Using QuestionMap

18. The problem with Question Grids
You can’t ‘point’ to a question in a question grid
It has been broken up into the question, code and the response domain
If you want to provide provenance and harmonisation (avoid them)
They have other strengths
They an efficient way to ‘point’ from a variable to a ‘cell within a grid’ using bindings
If you need to show the way the questions were answered with some indication of the format