Skip to content

Commit

Permalink
Update 2015-03-16-bio4j-a-roadmap.markdown
Browse files Browse the repository at this point in the history
  • Loading branch information
pablopareja committed Mar 16, 2015
1 parent 2e1368b commit 0cffefc
Showing 1 changed file with 13 additions and 1 deletion.
14 changes: 13 additions & 1 deletion source/_posts/2015-03-16-bio4j-a-roadmap.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -43,4 +43,16 @@ tag:

## Documentation

- **ETA?** examples for every graph, model docs integrated with the source code
- **ETA?** examples for every graph, model docs integrated with the source code

## Dataviz

In principle they would all be data visualizations that don't imply server requests. _(That doesn't mean that we won't be developing webapps in the future but we can first get a lot from what we already have without complicating things much more)_ We could include:

- A few _dashboards_ built with [dc.js](http://dc-js.github.io/dc.js/) This kind of dataviz is quite nice to play with and people generally just love it _(even though they might not understand what's going on too much and they just click randomly at the charts to see what happens... :) )_
- We should definitely have some sort of minimally interactive visualization of Bio4j data model, IMHO this is crucial not only for people that are willing to use Bio4j but also to get the big picture of what kind of data is included in the database.
- A set of biologically-wise interesting/useful visualizations _( @rtobes @marina-manrique @epareja @eparejatobes please some help here! ;) )_

## Neo4j distribution

This comment has been minimized.

Copy link
@eparejatobes

eparejatobes Mar 16, 2015

Member

but what about the data? testing it? will we make releases for it? In principle I'm quite sympathetic to having support for Neo4j, but there are a lot of rough edges in terms of what we will support and what not

This comment has been minimized.

Copy link
@pablopareja

pablopareja Mar 16, 2015

Author Member

We (or just me) could test it and so on without much work, I think that even having a yearly (or every other year) release would still be highly beneficial 😃 (actually even a paper could be written about it 😜)


I think this would be very important in order to regain some momentum for the project. The workload to get this running should not be much and, in turn, the benefits in terms of both visibility and potential engagements would be quite big.

0 comments on commit 0cffefc

Please sign in to comment.