-
Notifications
You must be signed in to change notification settings - Fork 6
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
Adding Utilities at hydroshare-jupyterhub #153
Comments
It would be best if HydroShare can work as a source to https://mybinder.org/ to turn the notebooks live |
I talked with @dtarb and @Castronova about it and yes it would be pretty cool to make a public composite resource in HydroShare to work with Binder. It should not be a hug amount of work. Binder deploys the content of a public GitHub repo which may include Jupyter Notebooks and makes them live and interactive. Maybe my issue though is different than what @ChristinaB is asking for |
This seems to mix separate things.
|
@dtarb @Castronova
We have a request from an organization (CSDMS https://github.com/csdms) and a toolkit publication (Observatory https://github.com/Freshwater-Initiative/Observatory done in part with HydroShare funding from 2016) to add Utilities.
From notes in a 4/18/2017 Team meeting (currently page 20) I asked for Team Input on "Is it a HydroShare responsibility or the CUAHSI JupyterHub server? How do we build utilities?"
Proposal Option 1: Develop a document to describe CUAHSI suggested steps/standards, test with OGH (independently developed tools that uses HydroShare REST client)
Proposal Option 2: Muddle through just making it work for examples above and develop a document describing the process for future utilities
Notes and thoughts on the utility adding process-
Possible steps to Contribute to hydroshare-jupyterhub/Utilities (TBD)
If dev continues, users can do a pip install to those evolving repos
Is this too much work for the utility developer?
yes
no
Library options currently for using tools in a Notebook:
The text was updated successfully, but these errors were encountered: