<div dir="ltr"><div>Hi all,</div><div><br></div><div>Please find attached the BPD that we put together (and still use) to help our students when they are doing markup in DDI Codebook.</div><div>It was based on the one you folks put together originally.</div><div>Some of the extras we put in were:</div><div>- explaining what the tag meant in English (no tech terms)</div><div>- if there was something special about the tag, then we put in a <i>Note</i> to explain it</div><div>- we put in lots of examples - and you will see that they are very Canadian-centric. We found that the more examples the students had, the fewer mistakes they made</div><div><br></div><div>I should mention that we are still using Nesstar (for now) to do our markup.</div><div><br></div><div>Cheers,</div><div><br></div><div>Jane<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 28, 2021 at 2:47 PM Wendy Thomas <<a href="mailto:wlt@umn.edu">wlt@umn.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>The DDI Technical Committee is working with a group of Codebook users on a new Best Practices document for DDI-Codebook. This document will focus the structure and technical aspects of Codebook that affect interoperability within and between communities of Codebook users. To do this work we are asking for your input on what should be covered and best practices you may have instituted within your organizations. Some areas we have identified include:</div><div><br></div><div>--Identification</div><div>--Text content (structure and multilingual issues)</div><div>--Controlled Vocabulary usage</div><div><br></div><div>So, what do we need from you?</div><div>1) Have you any existing guidance documents? </div><div>2) Are there any "sore points" where problems have arisen in the area of interoperability or specific use? </div><div>3) Are there areas where you think there should be additional guidance?</div><div><br></div><div>Note that while this document is focusing on structural and technical aspects, the Codebook group will also be preparing high-level documentation for Codebook so that if your content doesn't make it into the Best Practices document it will be used to inform the content of other high-level documentation for Codebook.</div><div><br></div><div>Please send your feedback to this list for others to see or directly to Wendy Thomas <<a href="mailto:wlt@umn.edu" target="_blank">wlt@umn.edu</a>>, chair of the Technical Committee. We appreciate your assistance in creating a document that will be useful to the community of DDI Codebook users.</div><div><br></div><div>Wendy Thomas, Chair, DDI Technical Committee</div><div><br></div>-- <br><div dir="ltr"><div>Wendy L. Thomas Phone: +1 612.624.4389</div><div>Data Access Core Director Fax: +1 612.626.8375</div><div>Minnesota Population Center Email: <a href="mailto:wlt@umn.edu" target="_blank">wlt@umn.edu</a></div><div>University of Minnesota</div><div>50 Willey Hall</div><div>225 19th Avenue South</div><div>Minneapolis, MN 55455</div></div></div></div>
_______________________________________________<br>
DDI-SRG mailing list<br>
<a href="mailto:DDI-SRG@icpsr.umich.edu" target="_blank">DDI-SRG@icpsr.umich.edu</a><br>
<a href="http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg" rel="noreferrer" target="_blank">http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Jane Fry, MA, MLIS<br>Data Services Librarian<br>MacOdrum Library<br>Carleton University, Ottawa, Ontario<br><a href="http://www.library.carleton.ca/find/data" target="_blank">http://www.library.carleton.ca/find/data</a><br>613.520.2600 x1121<br><br>.......................................................................................................................<br>This email communication, including all attachments, may contain private, proprietary, privileged and/or confidential information and subject to copyright. It is intended only for the person to whom it is addressed. Any unauthorized use, copying or distribution of the contents of this email is strictly prohibited. Please delete this email and notify the sender immediately, if you are not the intended recipient, and have received it in error.</div></div></div></div></div></div>