CANDDI Bo Wandschneider CAPDU/DLI April 13, 2005 Queen’s University

CANDDI Rome wasn’t built in a day These types of collaborations are slow to develop – especially with…  no funding  no formal governance structure We have made progress  Lots more to do …recap

CANDDI – what has happened Several discussion around DDI, Metadata. Nesstar were happening in the community Chuck proposed rolling this into a discussion forum in early early 2004 Yahoo Group created

CANDDI – what has happened Face to face meetings held in:  Montreal – Train the trainers (March)  Kingston - DLI (April)  Wisconsin - IASSIST (May) RDC’s partner to look at DDI and Nesstar Looking at integrating metadata during creation of survey vs. retro-fiting

CANDDI - Wisconsin On Friday, May 28, 2004 the members of CANDDI who attended IASSIST met to discuss next steps in implementing a Canadian DDI solution. Nineteen of the current list of CANDDI members were in attendance. A healthy discussion led to the recommendation to create five working groups.

CANDDI –working group 1 Logistics / Coordinating-Steering Group:  identify parallel activities occurring in the implementation of DDI in Canada; from a project management standpoint  identify ways of coordinating parallel DDI projects  responsible for coordinating the activities of the other four working groups  recommend to the CANDDI membership a more formal organizational model for CANDDI and its relationships with other organizations, for example, the DLI EAC.

CANDDI – working group 2 The Canadian DDI Tag Working Group:  responsible for selecting anappropriate set of DDI tags for Canadian data  produce a document describing these tags and annotating their use  recommend this document to the CANDDI membership for comment and revision  responsible for the care of this document.

CANDDI – working group 3 Control Vocabulary / Thesaurus Coordination Working Group:  responsible for identifying and recommending control vocabularies  including appropriate labels for variable groupings  vet their findings with the CANDDI membership  responsible for the care of the control vocabularies

CANDDI- working group 4 Quality Control:  responsible for articulating best practices and processes involved in the production of accurate and consistent DDI-compliant documentation  responsible for the care of the documentation of these practices and processes.

CANDDI – working group 5 Education / Training:  responsible for training programs for creators of data documentation, users of DDI-compliant documentation, and intermediaries supporting end- users  promoting their training program for use with existing training conducted by DLI and other appropriate organizations.

CANDDI - what happened next Discussions happened on-line and off-line Some expressions of interest were made Still some concerns being raised about fully understanding what DDI was People couldn’t – see it, touch it, play with it… How does it work with our data Maybe we need something more concrete before we move forward…

CANDDI – getting dirty People were already playing with markup Maybe we start with a subset of working group 2  The Canadian DDI Tag Working Group  Get something on paper  Something people can see, touch and play with  Has value that we can build on

CANDDI – getting dirty DINO put a group together in December Meeting in Ottawa Shared knowledge Discussed coordination

CANNDI – getting dirty  Tag details: ID - - institution unique identifier – UG example: cchs2003 ID - - Stats Can Catalogue number followed by year. Example: 82M

CANDDI – getting dirty  File priority: DLI – Labour Force Survey & General Social Surveys UG – focus on files in collection

CANDDI – getting dirty  Sharing Files Should we track? If so, how and where in the codebook? Who’s doing what?

CANDDI – what’s next Publish the suggested set of tags Get some feedback Education? Put in the Steering group?  Should this be formal?  Budget? Start establishing the working groups Set timelines?

CANDDI DISCUSSION