Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

DDI Annual Meeting

Enter summary here.

DDI at AAPOR

DDI exhibited at AAPOR, as well as presented a session, titled...

DDI at IASSIST

DDI exhibited at IASSIST

Welcome New Member: TBA21 Group

The DDI Alliance welcomes the TBA21 Group (represented by TBA21 Germany) an Associate Member of the Alliance.  David Schiller is the representative.

RWX: Scholarly Journals Covering DDI

The DDI Community has produced a rich store of DDI and metadata-related publications. Read-Write-Execute (RWX) will highlight some of these existing publications as well as new work as it is produced. The first column featured some of the foundations of DDI in scientific literature. The second revisited some of the top impact publications related to DDI from the last 20 years. And this one tries to identify those (mostly) scholarly journals, which seem to be interested in covering DDI topics.

If one looks for the search term “data documentation initiative” on Google Scholar, one gets 1260 results. Even if the bibliographic quality of the output is sometimes poor, as the entries are far away from being complete and well standardized, some journals stand out, which contain DDI topics more than incidentally. Here is a list sorted by the number of relevant articles:

If there is an article in the pipeline, it can make sense to take these journals into account.  Suggestions for journals, papers and topics for RWX are appreciated and can be sent to: Knut Wenzig, kwenzig@diw.de.

Moving Forward: Lawrence Sprint Report

The latest DDI development sprint was held in Lawrence, KS, following the IASSIST Conference. Eight participants focused on two primary tracks: evaluating the codebook view and reviewing and revising patterns.  Additional work was done on rules for realization of patterns, a technical and environmental assessment for publishing the DDI, identifying a 'ready' state,  recommendations for documentation, and other technical updates. The full report is available on the sprint's wiki page, along with all supporting documentation. 


  • No labels