Storing public data sets in installation directory is problematic
- Dominant language
- Python
- Stars
- 50
- Forks
- 17
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 3
Description
Downloading the public data sets and store them in the besca installation directory may be a problem if the downloading user does not have permissions to wirte into the installation directory, for example, if the besca installation is shared or if it is within a docker container.
see functions https://github.com/bedapub/besca/blob/4c7f7f1a92de2bc6c61b177e8fe6d0d16bb23d1d/besca/datasets/_datasets.py
workaround: provide option so that the user can specify an alternative path to the besca installation directory.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in besca/datasets/_datasets.py and inspect the functions that download and store the public data sets. Add a user-selectable alternative storage path, then verify that downloads work when the Besca installation directory is not writable, including in a shared installation or Docker container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100