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

How to most efficiently correct variable titles and definitions? #5

Open
kirbykat opened this issue Sep 12, 2017 · 5 comments
Open

Comments

@kirbykat
Copy link

kirbykat commented Sep 12, 2017

Many variables in the SCCS have had their titles and code definitions shortened in the digitization process (i.e., the original digital files, available from World Cultures, provide only these shortened titles/definitions).

A lot of information is lost in the process!

E.g., v116, which in the digital SCCS (and now in D-PLACE) is called "Sex Frequency in Marriage" was originallly published as "Attitude towards desirability of frequent sex in marriage". Here's a screenshot of original codes, compared to codes in D-PLACE.

code_example

  • No abstinence
  • Abstinence at times
  • Moderation
  • Abstinence admired

Is the best solution to use a text extractor to get original definitions? (This is what I did for the EA, but will take a while for 1781 variables...) For now, it is up to the user...

@xrotwang
Copy link
Contributor

I guess having this typed in by a student assistant may be quicker than fiddling with OCR and having to cross-check the results.

@kirbykat
Copy link
Author

I'm going to work on improving the variable titles/definitions. I'm planning to do it in the csv file because it will be a fairly major overhaul. Any concerns with this, or anyone else working on the variables?

@xrotwang
Copy link
Contributor

If by csv file you mean this https://github.com/D-PLACE/dplace-data/blob/master/datasets/SCCS/variables.csv then no concerns. Not even if someone else would be working on it, because, hey, that's what version control is good for :)

@xrotwang
Copy link
Contributor

@kirbykat has this issue been addressed and solved by now?

@xrotwang xrotwang transferred this issue from D-PLACE/dplace-data Nov 21, 2023
@xrotwang
Copy link
Contributor

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