peterneubauer

EPublishing: A graphical approach to digital publications

Hej dude

---

peterneubauer

This gist is a small subset of objects in the the Oracle database, and their dependencies on the object, SYS.DBA_OBJECTS.

When database objects are created, they create a tree structure. It’s possible to have many root nodes to a single child node, such as a stored procedure that reads six or more tables.

When creating objects such as functions or procedures, all the parent objects must first be created and valid. If a single object become invalidated, all child objects also become invalidated.

Queries to the data dictionary view, DBA_OBJECTS, will show dependencies, however, the dependencies are only shown only one level up or down. Another problem with such queries, is that it’s often possible to see the same object listed many times in the output.

peterneubauer

DBA_OBJECTS Tree – Modelled As A Graph in NEO4J, Visualized With Gephi

This gist is a small subset of objects in the the Oracle database, and their dependencies on the object, SYS.DBA_OBJECTS.

When database objects are created, they create a tree structure. It’s possible to have many root nodes to a single child node, such as a stored procedure that reads six or more tables.

When creating objects such as functions or procedures, all the parent objects must first be created and valid. If a single object become invalidated, all child objects also become invalidated.

peterneubauer

= Enterprise Content Management with Mattias

== Introduction

There are several challenges in Enterprise Content Management (ECM) that current technologies cannot tackle efficiently. With Neo4j, a whole new world of possibilities opens up. There are few things more "graphy" than ECM, and so the logical next step is the use of graph databases.

What follows is a subset of the possibilities with Neo4J in ECM. We tackle recommendations, time-based versioning, ACL, metadata management and user action registration. 

== The dataset 

peterneubauer

Analytics on throughput and Oil well optimizations

The setup

CREATE (t11:Throttle{name:'throttle11'})
CREATE (t12:Throttle{name:'throttle12'})
CREATE (well1:Wellhead{name:'well1'})
CREATE (well2:Wellhead{name:'well2'})

peterneubauer

Piping Water

Inspiration

London’s antique water distribution network is infamous: it loses a quarter of the water supplied to London (spilt into the ground). Consequence: desalination, massive additional CO2 emissions, road congestion caused by too many emergency excavations and very high water prices for consumers. London’s case is severe but not atypical: most cities suffer from the same underlying infrastructure problem. Pipes and valves buried below busy urban streets are inherently difficult and expensive to maintain. Inaccessibility, lack of information, failure to efficiently process data and the high cost of each human intervention in legacy systems all compound to undermine efficient resource distribution.

peterneubauer

Union and Intersection

This Gist tries to anwser This question on the Neoj4 mailing list:

I have networks, which have many "egos" that appear in those networks. These egos, in turn, occur in many different networks - basic many-to-many relationship, and in the context of a graph db, a bipartite network. In practice, my data looks something like this (pardon whatever silly format I’m about to write it as):

Network 1: [Ego 1, Ego 2, Ego, 3, Ego 4]
Network 2: [Ego 2, Ego 4, Ego, 5, Ego 6]
Network 3: [Ego 4, Ego 5, Ego, 7, Ego 8, Ego 9, Ego 10]

peterneubauer

= Relationships

[source,cypher]
----
CREATE (umu:UNIVERSITY {name:"Ume Universitet"})
CREATE (mat:DEPARTMENT {name:"Matematik"})
CREATE (fv:COURSE {name:"flervariabel analys"})
CREATE (roland:PERSON {name:"Roland"})
CREATE (anna:PERSON {name:"Anna"})
CREATE (wille:PERSON {name:"William"})

peterneubauer

CREATE (a{name:'Admin'})
CREATE (fr1{name:'Folder1'})
CREATE (fr2{name:'Folder2'})
CREATE (fr3{name:'Folder3'})
CREATE (fa{name:'File A'})
CREATE (fb{name:'File B'})
CREATE (fc{name:'File C'})

peterneubauer

A sales funnel

CREATE (s:Stage{name:'Suspect'})
CREATE (mql:Stage{name:'Marketing Qualified Lead'})
CREATE (ssc:Stage{name:'Self-Serve Customer'})
CREATE (ec:Stage{name:'Existing Customer'})
CREATE (ecno:Stage{name:'Existing Customer-No Opportunity'})
CREATE (sql:Stage{name:'Sales Qualified Lead'})