Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Codebook versus SQLite table - Different number of variables for Goals table #5

Closed
glasneed opened this issue Dec 17, 2022 · 2 comments

Comments

@glasneed
Copy link

The codebook lists 27 variables, the SQLite table shows 15 columns. For example, there is no family_name in the SQLite version but it is referenced in the code book.
goals

@jfjelstul
Copy link
Owner

This is intentional. Each table in the database has a different unit of observation, but in the .csv version, I've pre-merged in relevant variables from other tables for convenience. The codebook is based on the .csv version. Since the SQLite version is a relational database, tables don't include variables that vary according to a different unit of observation. Each table in the SQLite database has a primary key that uniquely identifies each observation. And then some tables also have foreign keys, which map each observation to observations in other tables. You can merge tables together based on these foreign keys. The file data-sqlite/SQL-schema.txt indicates which variables in each table are foreign keys.

@glasneed
Copy link
Author

Thank you for the clarification on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants