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.

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

Move Data Retrieval Code to New Repository #20

Open
WardLT opened this issue Nov 2, 2018 · 2 comments
Open

Move Data Retrieval Code to New Repository #20

WardLT opened this issue Nov 2, 2018 · 2 comments

Comments

@WardLT
Copy link
Contributor

WardLT commented Nov 2, 2018

As we modify the codes that publish data from certain repositories, should we move it to their own repositories? They provide great examples for how to use MDF Connect, and are kind of hidden here.

I'm willing to do this. Does anyone object?

@jgaff
Copy link
Contributor

jgaff commented Nov 2, 2018

As discussed offline:
I think it's a good idea to update the harvesters that can still be useful to us (MDR, for example) and move them to the docs/examples dir in the connect_client repo. Having practical, functional examples of dataset submission is a great idea, and I think having those examples close to the client will aid discovery.

@WardLT
Copy link
Contributor Author

WardLT commented Feb 10, 2019

I'm adding a list of databases that we should build indexers for, which is very incomplete at the moment:

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

No branches or pull requests

2 participants