EDDI24

Ref: 16th European DDI Users Conference, Chur

There were two sessions at EDDI 24:

• a dedicated workshop Monday morning

• a Bird of a Feather session Wednesday afternoon

Out of those two sessions, several points were made on how to foster the use of DDI for questionnaires. Here is a summary of those points:

• we need guidance / tooling to help choose between DDI products for questionnaires

  • such material exists:

    • DDI Codebook, DDI Lifecycle, and DDI Cross Domain Integration: Use Cases and Objectives

    • https://ddialliance.org/products/overview-of-current-products

  • maybe actions need to be taken to communicate about those documents to end users?

  • we may though need guidance on how to best use Codebook in order to be interoperable with Lifecycle? And the other way around? Does it make sense?

  • tools can help here too

    • specifically, tools that allow people to use DDI without knowing they’re using it!

      • CLOSER’s DDI questionnaire editor - Archivist

      • or Insee’s Pogues

    • those tools can help designers using other tools than Word

• more focused / on point documents would be useful

  • we have for example demands for how to best use logical statements in questionnaires

  • more generally, discussions during the conference have legitimated the need for documentations between introductory material and specifications/models…

  • …and the need to provide examples

    • see CLOSER guide: Document a Questionnaire

    • and Insee too: DDI questionnaire modeling

• there is also a need for guidance over the use of concepts and their links to questionnaire elements

  • are there training material or guidelines for that?

    • Foundational DDI Metadata: Introduction to Concepts in DDI

• it would be interesting to compare DDI for questionnaires across organisations

  • once again, having profiles could help

  • provide some sort of minimum metadata requirements when documenting questionnaires

• we should have a way to publish questionnaires in order to largely share between users / implementers

  • link to examples need above