Welcome to this week in Neo4j where we round up what’s been happening in the world of graph databases in the last 7 days.

This week we look at how to create a Neo4j powered Alexa bot, analysing the Neo4j community on twitter, and a write up from the life sciences and healthcare workshop.


This week’s featured community member is Daniel Himmelstein, Postdoctoral Fellow at University of Pennsylvania.

Daniel Himmelstein - This Week's Featured Community Member

Daniel Himmelstein – This Week’s Featured Community Member

Daniel is the creator of Hetionet – an integrative network of biology, disease, and pharmacology. ‘hetnet’ is actually a word coined by Daniel to describe networks with many types of relationships

There’s a hosted Neo4j instance including a walk through guide, which you can play with at neo4j.het.io and Daniel spoke about Hetionet at GraphConnect San Francisco 2016.

Daniel has appeared interviewed on the Graphistania podcast and recently launched cognoma in collaboration with the DataPhilly and Code for Philly meetups. This project puts machine learning in the hands of cancer biologists.

On behalf of the graph and biology communities, thanks Daniel for all your work!

Neo4j life sciences and healthcare workshop in Berlin


Often invisible to the people outside of the field, life-science researchers have been embracing graph databases instead of the traditional triple- and relational-stores.

This week Petra Selmer and Michael Hunger invited life-science and healthcare researchers and practitioners to Berlin to share their experiences in a full day workshop.

Neo4j life sciences and healthcare workshop

Neo4j life sciences and healthcare workshop

And a full day it was: 11 planned and 3 ad-hoc presentations and 2 longer workshops, covering everything from genome, proteome, pathway and systems biology model databases and interactions to actual drug development efforts and plans for improving healthcare, all with the help of graphs.

We were stunned by the breadth of applications and by the enthusiasm and happiness of the presenters.

Thank you so much to everyone for presenting, discussing and attending, we will definitely run similar events elsewhere and possibly coordinated with the industry conferences. We will publish a longer blog post about the event and also proper proceedings. Daniela Butano from InterMine.org shared her impressions here.

Analysing Neo4j tweets, IEEE Graph Challenge, Neo4j Alexa Chatbot


Online Meetup: Pheno4J – a gene to phenotype graph databases


In this week’s online meetup Nikolas Pontikos showed us Pheno4J – a gene to phenotype graph database created to make it easier to analyze human DNA and genetic mutations.



You can also find the code in the pheno4j repository on GitHub.

From The Knowledge Base


This week from the Neo4j Knowledge Base we have an article showing how to use Amazon CloudWatch to monitor Neo4j logs.

And if you’re planning to deploy Neo4j on AWS, we’ve recently created a guide showing how to install Neo4j using a custom AMI with AWS command line tools.

Next Week


What’s happening next week in the world of graph databases?

Tweet of the Week


My favourite tweet this week was by David Fudge:

Don’t forget to RT if you liked it too.

That’s all for this week. Have a great weekend!

Cheers, Mark

 

Keywords:  


About the Author

Mark Needham, Developer Relations Engineer

Mark Needham Image

Mark Needham is a graph advocate and developer relations engineer at Neo4j.

As a developer relations engineer, Mark helps users embrace graph data and Neo4j, building sophisticated solutions to challenging data problems. Mark previously worked in engineering on the clustering team, helping to build the Causal Clustering feature released in Neo4j 3.1. Mark writes about his experiences of being a graphista on a popular blog at markhneedham.com. He tweets at @markhneedham.


Leave a Reply

Your email address will not be published. Required fields are marked *

Subscribe

Upcoming Event

 


Have a Graph Question?

Stack Overflow
Slack
Contact Us

Share your Graph Story?

Email us: content@neo4j.com