Maybe use a cache for larger data sets about modeldata HOT 12 CLOSED

yea i think the order of figuring out what path to use should look something like:

data_ames(path = NULL)

• Use path if not NULL
• Use modeldata.cache if not NA
• Use global cache path into <cache-path>/model-data/ames.rds

from modeldata.

We are doing all this in https://github.com/tidymodels/modeldatatoo 😄

from modeldata.

https://github.com/emilhvitfeldt/textdata is an expanded version of what you are proposing. You are free to take bits and pieces as you need.

from modeldata.

Yea that looks great! I also didn't know rappdirs was an actual package. This will be helpful too

https://github.com/EmilHvitfeldt/textdata/blob/2b5e9f7bd8b6b722970d2c5b54a8989f542d252f/R/load_dataset.R#L10

from modeldata.

yes rappdirs is gonna save you a lot of headaches

from modeldata.

Alternatively, gargle stores things in <os-home>/.R/gargle/gargle-auth, with the additional opportunity to override this with a global option options("gargle_auth_cache" = <path>)

from modeldata.

Should have:

• A function to clean the cache
• A function to check if a data set is outdated
• Maybe create subfolders by package version?
• Provide a way to access the package version specific data if you have downloaded it in the past, even if you are on a higher version of the package (for reproducibility)

from modeldata.

should also have a way to overwrite the file path

from modeldata.

Perfect timing for some new data too. @trang1618 😃

from modeldata.

Would pins be able to solve this problem as well?

from modeldata.

datastorr looks perfect for this application.

from modeldata.

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.

from modeldata.