This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I'm using the calgary transforms with the Experian cencus dataset for the first time and am trying to figure out how to bring in the descriptions of the codes.
Is this some setting in the calgary input tool? Or will I have to join to all the additional files that come with the census data set to get the descriptions?
You can get to the descriptions for the codes when you go to edit index metainfo, so it seems as though the tool knows how to get the descriptions, but it doesn't appear to output those descriptions, just the codes, which are kinda useless if you don't know what they mean.
It's been a while since I looked at it, but it's primary basis is using the Allocate Metainfo tool in connection with a Dynamic Rename tool. The only thing is that you can't just match on the code because the Descriptions can be the same for various codes and are actually unique on Description/SubCategory.
I'm pretty sure this macro takes this into consideration, but you can always open it up to see the actual workflow behind it.
The value descriptions you see in the Experian Household and Individual Calgary files actually come from an XML installed with the datasets. The HH file XML is named "ConsumerView__QueryFieldInfo.xml", and the Individual file XML is named "Individual__QueryFieldInfo.xml". There is no way to output the value descriptions directly from the Calgary tools, but you could definitely write a process to do so with these files.
Below is an example of how to do it... I'm not sure how useful this feature would be for anything other than final presentation of the data. For performance reasons, you'd want to join the descriptions as far down in the stream as possible.
Hi, for the file ConsumerView_QueryFieldInfo.xml has 3 fields, but only "name" field is poplulated, the "EnumeratedValues" and "QueryFieldInfo" are empty. I am wondering how can I know the meaning of the coded value for Experian Household Data?
@idaho8007 Instead of reading in the QueryFieldInfo file as xml - read it in as a csv with no delimiter (\0) and no field names in the first row. From there you have quite a few options for parsing out the data.