Dimension Table Verbosity - Theory verses Prictice

Per Kimball "Attributes should consist of real words rather than crptic abbrevistions." and "We strive to minimize the user of codes in our dimension tables by replacing them with more verbose textual attributes." The question is IN PRRACTICE, do you typically use "Yes", "No" for values in a boolean field like Is_Work_Day, or do you spell out the data as in "Workday" or "No Work"?

Both.

Flags and codes are useful internally for ETL processing and query filtering, but end users should be presented with meaningful labels. Wither yes/no or workday/not workday depends on what the users want.

I have used Y/N or 1/0 for these type columns.

OK, I think what we'll do is use the non-verbose data during the early stages of the ETL process, then present the user with the more verbose data in views. That will make it easier for us (the developers), and give the user what they want.

I am beginning to use "Work Day" and "Non Work Day" as well as using a field called "Work Day Indicator" that is Y/N. I like using the indicator when writing code but the Text looks better in Reports and Cubes.