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

Improving figshare download modularity #15

Open
1 of 3 tasks
dhimmel opened this issue Nov 16, 2016 · 6 comments
Open
1 of 3 tasks

Improving figshare download modularity #15

dhimmel opened this issue Nov 16, 2016 · 6 comments
Assignees

Comments

@dhimmel
Copy link
Member

dhimmel commented Nov 16, 2016

Currently, there are three main issues we need to think about / address:

@jessept
Copy link
Collaborator

jessept commented Dec 2, 2016

@dhimmel I've poked around the data retrieval sharing concept and I'm seeing a lot of code in cancer data that could be cleaned up and tweaked.

The end result: the cancer data repo SHOULD contain all data cleaning/downloading. This would allow both cognoml and core-service to use it as a submodule to enable code re-use. I can tackle this but need to understand more about the intended flow in core-service, make sure we are only pulling data from one source, and keep that source consistent through all of our projects.

@dhimmel
Copy link
Member Author

dhimmel commented Dec 2, 2016

The end result: the cancer data repo SHOULD contain all data cleaning/downloading.

So right now the cancer-data repo really just contains a data processing pipeline. Do you think it's the right choice to also include a package? This combined functionality didn't work out that well for machine-learning.

So do you think it makes more sense to make a separate repository for data download / upload? Currently, data download is in cognoml and data upload doesn't exist (data is manually uploaded to figshare). What would be awesome would be to have figshare upload automated. While it will most likely take more time to setup than it would save, this would be very state-of-the art.

@vasudevanv
Copy link
Member

Should we just make a separate python interface for dealing with the figshare API residing either in cancer-data or cognoml?

@jessept
Copy link
Collaborator

jessept commented Dec 7, 2016

I do think there should be a separate figshare-facing repo that both core-service and cognoml can use.

@dhimmel
Copy link
Member Author

dhimmel commented Dec 8, 2016

Okay I created https://github.com/cognoma/figshare and gave @jessept and @vasudevanv write access.

@vasudevanv
Copy link
Member

vasudevanv commented Dec 8, 2016

Awesome. I started working on a figshare module with upload new, download and update existing article features. Can push something over the weekend.

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

No branches or pull requests

3 participants