<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>Progeny Community &#187; Topic: Data Dictionary</title>
<link>http://www.progenygenetics.com/community/</link>
<description>Progeny Community &#187; Topic: Data Dictionary</description>
<language>en</language>
<pubDate>Sat, 31 Jul 2010 03:35:55 +0000</pubDate>

<item>
<title>Roger on "Data Dictionary"</title>
<link>http://www.progenygenetics.com/community/topic/35#post-137</link>
<pubDate>Wed, 06 Jan 2010 13:44:59 +0000</pubDate>
<dc:creator>Roger</dc:creator>
<guid isPermaLink="false">137@http://www.progenygenetics.com/community/</guid>
<description>&#60;p&#62;I guess a  data dictionary feature &#34;up front&#34; would be useful.&#60;/p&#62;
&#60;p&#62;However, If you already use MS Access or some other front end to link to the Progeny database, it is easy to output the st_datadictionary table to a query or report.
&#60;/p&#62;</description>
</item>
<item>
<title>andrea on "Data Dictionary"</title>
<link>http://www.progenygenetics.com/community/topic/35#post-92</link>
<pubDate>Tue, 16 Jun 2009 13:08:44 +0000</pubDate>
<dc:creator>andrea</dc:creator>
<guid isPermaLink="false">92@http://www.progenygenetics.com/community/</guid>
<description>&#60;p&#62;A data dictionary feature would be great.
&#60;/p&#62;</description>
</item>
<item>
<title>Ginny Hughes on "Data Dictionary"</title>
<link>http://www.progenygenetics.com/community/topic/35#post-63</link>
<pubDate>Fri, 30 Jan 2009 18:01:53 +0000</pubDate>
<dc:creator>Ginny Hughes</dc:creator>
<guid isPermaLink="false">63@http://www.progenygenetics.com/community/</guid>
<description>&#60;p&#62;yes, please put my vote in as well for a data dictionary
&#60;/p&#62;</description>
</item>
<item>
<title>khope on "Data Dictionary"</title>
<link>http://www.progenygenetics.com/community/topic/35#post-61</link>
<pubDate>Thu, 29 Jan 2009 11:36:03 +0000</pubDate>
<dc:creator>khope</dc:creator>
<guid isPermaLink="false">61@http://www.progenygenetics.com/community/</guid>
<description>&#60;p&#62;I agree as well. This would certainly be beneficial for collaborative epidemiology projects, keeping track of what fields you maintain, and avoiding redundant data collection.
&#60;/p&#62;</description>
</item>
<item>
<title>TRAMDTRAN on "Data Dictionary"</title>
<link>http://www.progenygenetics.com/community/topic/35#post-57</link>
<pubDate>Tue, 20 Jan 2009 11:00:05 +0000</pubDate>
<dc:creator>TRAMDTRAN</dc:creator>
<guid isPermaLink="false">57@http://www.progenygenetics.com/community/</guid>
<description>&#60;p&#62;Yes, I agree this would be very useful as personnel responsible for maintaining the database may change and it may not always be obvious as to why certain data has been maintained and/or the purpose of some computed fields.
&#60;/p&#62;</description>
</item>
<item>
<title>Lianne Mink on "Data Dictionary"</title>
<link>http://www.progenygenetics.com/community/topic/35#post-54</link>
<pubDate>Fri, 16 Jan 2009 10:00:50 +0000</pubDate>
<dc:creator>Lianne Mink</dc:creator>
<guid isPermaLink="false">54@http://www.progenygenetics.com/community/</guid>
<description>&#60;p&#62;Thanks for the feature request! Are there any other community members that would be interested in this? If so, we would like to get your feedback.
&#60;/p&#62;</description>
</item>
<item>
<title>jamie-lheureux on "Data Dictionary"</title>
<link>http://www.progenygenetics.com/community/topic/35#post-53</link>
<pubDate>Thu, 15 Jan 2009 19:45:52 +0000</pubDate>
<dc:creator>jamie-lheureux</dc:creator>
<guid isPermaLink="false">53@http://www.progenygenetics.com/community/</guid>
<description>&#60;p&#62;It would be nice to be able to export out a data dictionary.  It could just be the name of all of the fields, the field type, and if possible, the options for drop down fields.  If a description could be added when each field is created that explains that field, that description could also be exported in the data dictionary.  Funding sources often ask for a data dictionary to see what type of data is being collected for a study.  We currently track this in excel and have to remember to update it whenever we change or make new fields.
&#60;/p&#62;</description>
</item>

</channel>
</rss>
