-
Notifications
You must be signed in to change notification settings - Fork 4
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
Comments
@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. |
So right now the So do you think it makes more sense to make a separate repository for data download / upload? Currently, data download is in |
Should we just make a separate python interface for dealing with the figshare API residing either in cancer-data or cognoml? |
I do think there should be a separate figshare-facing repo that both core-service and cognoml can use. |
Okay I created https://github.com/cognoma/figshare and gave @jessept and @vasudevanv write access. |
Awesome. I started working on a figshare module with upload new, download and update existing article features. Can push something over the weekend. |
Currently, there are three main issues we need to think about / address:
cognoml/data.py
andcognoml/figshare.py
have duplicate functionality.We may want to make a subclass for
FigshareDataSource
in data.py. See cognoml refactor part 1 #3 (comment)We need to find a way to expose figshare download functionality to other cognoma repositories. For example, this could help with Acquires and loads gene and mutation data core-service#42
The text was updated successfully, but these errors were encountered: