-
Notifications
You must be signed in to change notification settings - Fork 2
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
Cleanup #63
Cleanup #63
Conversation
…y to download restricted references without proper authentication/permissions.
@@ -138,7 +138,7 @@ get_refs_info <- function (reference_type = "dataPackage", | |||
#' | |||
#' If a data package fails to download (or load) into R, the function will return NAs instead of summary data about the data package as well as a message about the package status ("Loads", "Error") in the dataframe that the function returns. The function will ignore files that fall outside the data package specifications (one or more .csv files and a single .xml file ending in *_metadata.xml). | |||
#' | |||
#' When `check_metadata` is set to the default `FALSE`, the function will attempt to and load any .csv, regardless of the contents. Data packages with restricted access can produce false positives if you do not have the appropriate permissions to download the data as the function will still download the files, but they will be populated with unhelpful hmtl rather than the intended data. Functions that fail to load into R likely violate the data package specifications in some fundamental way (e.g. .CSV file instead of .csv or no .csv files at all). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the future, might be worth throwing an error when it downloads a csv with an html error instead of the actual data.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Totally, if that behavior persists on the DataStore side. It was rather unexpected and Judd said we should probably improve how DataStore handles the situation. I'm holding off until that gets figured out in the hopes that it does so relatively soon.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. See comment on meta_analyses.R.
Get rid of old/bad functions and their files, add importFrom to some functions that needed it, remove unused packages from Imports, add variables to the globalVariable list, and fix up some documentation. Result: 0 warnings 0 errors 0 notes!