Often it is useful to keep a codebook to document the contents of a dataset. (By
dataset I mean
a rectangular structure such as a dataframe.)
The codebook has as many rows as the dataset has columns (variables, fields).
The columns (fields)
of the codebook may include:
•
I find that Harrell's describe ( Hmisc) provides some of that desired
functionality. When I am creating a paper codebook I will print the
results of describe function fro a dataframe to create an overview
snapshot and will post a copy of str(dfname) on the wall.
As his help page says:
Alzola and Harrell discuss some of these issues in An introduction to
S and the Hmisc and Design Libraries.
-ista
On Wed, Oct 28, 2009 at 1:27 PM, Jacob Wegelin jacobwege...@fastmail.fm wrote:
Often it is useful to keep a codebook to document the contents of a
dataset. (By dataset I mean
a
As does Muenchen in RforSASSPSSusers.pdf and in the book that grew out
of that effort:
http://rforsasandspssusers.googlepages.com/RforSASSPSSusers.pdf
http://www.amazon.com/SAS-SPSS-Users-Statistics-Computing/dp/0387094172/ref=pd_bbs_sr_1?ie=UTF8s=booksqid=1217456813sr=8-1
4 matches
Mail list logo
