Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleApril 13, 2015

Simple Codebook Meeting
2015-04-13

Steve added Package and suggested package and the DDI-C definition The meeting focussed on reviewing the next set of metadata elements from DDI-C - those covered by Steve.

Steve had created an additional three columns to his copy of the spreadsheet . Source – example for digitized statistical abstract  the original print publication. If administrative data the original administrative program. A simple version of provenanceGeographic unit? for his work - adding:

  1. Package (for elements already matched in DDI4)
  2. Suggested Package (for elements that have no match)
  3. the DDI-C definition.

These additional columns have now been added to the Google Spreadsheet - linked here.

The discussion then focussed on the elements. Notes on specific elements are included in the spreadsheet, and summarised below

Elements

Source

  • example for digitized statistical abstract  the original print publication. If administrative data the original administrative program. A simple version of provenance

Geographic unit

  • “Lowest level of geographic aggregation covered by the data.”
  • Would GeographicLevels (plural) be better to indicate that multiple levels can be used.
  • Is GeographicLevel a better term than GeographicUnit?

Control operations – description

  • Description of what was done. Data collection process
,What do we recommend here
  • ,

General comments and issues

It was noted that much of the methodology section of DDI-C was not yet covered in DDI4. Part of this will be addressed by the Methodology working group.

There is however a set of elements that are not really methodology (or at least the research design), but rather are descriptive of the process and outcome of the execution of the methodology. These elements might most appropriately fall under the heading of "Fieldwork". Examples from DDI-C include:

  • CollectionSituation
  • MinimizeLossActions
  • ControlOperations

and, notably, RESPONSE RATE.

The group had concerns that it was unclear how we might provide recommendations here? e.g. ResponseRate, what is meant – “opposite of rate of refusal?” other types?  Is this It was also recognised that this is not really part of methodology, but has an impact on methodology – impact on analysis, post processing. Was there an intervention based on low response rate? Fieldwork issues. Bring this to AG sooner rather than later.on methodology – as well as on analysis, post processing. For example, was there an intervention based on low response rate? Fieldwork issues.

On similar lines, there was a recognition that Methodology is the ugly part of DDI Codebook. Dan suggested that this section may be in need of a significant revamp, given the developments in survey methodology that have occurred since the original development of DDI-C, in particular the Total Survey Error framework.

It was noted that these issues with Methodology and Fieldwork need to be raised with the AG sooner rather than later, as they have resource and workload implications for the Moving Forward program. Steve will write something up on this .

Methodology is the ugly part of Codebook.

Steve will add his columns to the spreadsheet.and distribute to the group, prior to sending to the AG.