-
Notifications
You must be signed in to change notification settings - Fork 65
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
new "Direct Data Download and Ingestion" section #501
Comments
@wibeasley hi! do you prefer yaml? |
Yes, I typically prefer yaml if the (a) data has a nested or non-rectangular structure and (b) the file is a human entered/edited. I tend to use json for machine-generated datasets. But there are some tabular/rectangular files that I have started expressing as yaml because they're easier to read & adjust. A small downside is that it requires a little more work (for the ingesting code) to verify the yaml politely transforms to a data.frame. Here's an example of a tabular structure that I felt was a better fit for yaml than csv: https://github.com/OuhscBbmc/REDCapR/blob/main/inst/misc/validation-transformation.yml I don't do it much, but the yaml package can load a file from a https url: yaml::yaml.load_file(
"https://raw.githubusercontent.com/OuhscBbmc/REDCapR/main/inst/misc/validation-transformation.yml"
) Since we already have bullets for csv, xml, html, & json ...I thought yaml could be included for completeness. But as always, I'm happy following your lead. Tell me if you think tangents like this are more distracting than helpful. Are there scenarios where you do/don't format a data file as yaml? |
read*()
functions and TLS/SSL urls. A lot of still says that base R functions (eg,read.csv()
) cannot handle an https urlThe text was updated successfully, but these errors were encountered: