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

Rebrand family of report_data() functions #131

Closed
BBieri opened this issue Mar 2, 2021 · 2 comments · Fixed by #138
Closed

Rebrand family of report_data() functions #131

BBieri opened this issue Mar 2, 2021 · 2 comments · Fixed by #138
Assignees

Comments

@BBieri
Copy link
Contributor

BBieri commented Mar 2, 2021

Create a family of report_data() functions that serve the following roles:

  • What is in this package/database/dataset?
    • Will contain the names of the content and the bibliographic information
  • How do the datasets compare within one structure (package, database, dataset)
    • This function will contain information about missing values, number of observations, number of variables, earliest beg date and latest end date.
  • How do the datasets compare to the original dataset?

The names of the functions are tbd. I welcome suggestions :)

@BBieri BBieri self-assigned this Mar 2, 2021
BBieri pushed a commit that referenced this issue Mar 2, 2021
It will be rewritten once the structure of report_data family of functions is clearer (relates to #131)
@BBieri
Copy link
Contributor Author

BBieri commented Mar 3, 2021

  • data_source()
    • Will contain the names of the content and the bibliographic information
  • data_compare()
    • This function will contain information about missing values, number of observations, number of variables, earliest beg date and latest end date.

@BBieri
Copy link
Contributor Author

BBieri commented Mar 9, 2021

The data_source() and data_compare() functions are mostly done. Their development is now held back by decisions on the "qID" issue, e.g. which column should be considered as the ID.

Please let me know your thoughts on the function names, the output (do you want to display other information?), as well as your general feedback on the functions.

Sidenote: I will create a separate issue for the data_evolution function since it is less of a priority for the moment. You can find it here: #134.

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

Successfully merging a pull request may close this issue.

1 participant