Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Define packages as tools vs data interfaces #1

Open
chrismheiser opened this issue Oct 25, 2018 · 0 comments
Open

Define packages as tools vs data interfaces #1

chrismheiser opened this issue Oct 25, 2018 · 0 comments
Assignees
@chrismheiser
Labels
enhancement New feature or request

Comments

@chrismheiser
Copy link
Collaborator

Find out how to programmatically label which packages are tools vs which packages are data interfaces. A distinction to search for might be some GET and POST http calls within a package.

A data interface package is one that has functions for manipulating and working with data. An example of this is geoChronR.

A tool package is one that interfaces with other sources can pull data from those sources in a workflow. Examples of this is neotoma and rNOAA.
@chrismheiser chrismheiser added the enhancement New feature or request label Oct 25, 2018
@chrismheiser chrismheiser self-assigned this Oct 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chrismheiser chrismheiser

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chrismheiser