Brian E. Granger
Brian E. Granger
The current design of the collapsible sections in the data explorer is a challenge to navigate and takes up a large amount of vertical space. The "Hide" and "Show" buttons...
### Problem I have a proposal to create a new document ID service for server/lab/notebook. Because many of the usage cases related to things like RTC and commenting in lab/notebook,...
The existing Voyager UI is designed to be a full page app. In JupyterLab, that doesn't make as much sense. This purpose of this issue is to explore different ways...
This is an issue to begin discussing and thinking about what data sources we would want to support. There are maybe three related questions: * What data formats? * What...
A user should be able to save/export a Voyager visualization to a notebook. Some possible formats of saving that might be: * A raw `display_data` cell (not yet implemented in...
The other data output/save examples are focused on the saving a single chart. A user should also be able to save the state of the entire redux store as a...
A user should be able to share their Voyager based visualization using the Voyager website (http://vega.github.io/voyager/) or Blocks (https://bl.ocks.org/domoritz/455e1c7872c4b38a58b90df0c3d7b1b9)
A user should be able to save a visualization they have created with Voyager as a file. This would likely be as a `.vl.json` file and might include the raw...
(This came up in the private Steering Council group and we wanted to open this here for public discussion and eventual voting) Previously, we have been creating individual Gmail addresses...
There are a number of Jupyter contributors and stakeholders who are writing grants for the CZI EOSS program (https://chanzuckerberg.com/eoss/). Here are links to some of the discussions and issues on...