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

specify external data sources in module metadata #205

Closed
achubaty opened this Issue Jul 10, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@achubaty
Contributor

achubaty commented Jul 10, 2015

external data sources should be clearly identified in the metadata.

perhaps adding a column in the input object data.frame specifying url? this allows the module developer to check whether the data are available locally, and if not, to get them.

this also raises the issue of where to store data downloaded in this way. presumably the data should be stored in the module's directory. thoughts?

@achubaty

This comment has been minimized.

Contributor

achubaty commented Oct 21, 2015

see also #214

@achubaty

This comment has been minimized.

Contributor

achubaty commented Oct 21, 2015

add data/ directory to each module. can include raw data or be able to download to this folder.

also included in data/ should be a CHECKSUMS.txt file that has the expected hashes for each data file. downloaded (or included) data can be checked against these hashes to ensure validity.

achubaty added a commit that referenced this issue Oct 21, 2015

add data source info to module metadata (#205)
* added `downloadData` to get module data from url
* added `checksums` function to verify MD5 hashes of data files
* update email addresses throughout
* misc cleanup

@achubaty achubaty closed this Oct 22, 2015

@achubaty achubaty referenced this issue Dec 18, 2015

Closed

Development #240

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment