Neo4j Data Browser UI: "template" for new nodes?

[Roman]

Hi,

When using the Neo4j Data Browser UI to enter some nodes it would be very convenient if I there was a form that already has all the relevant property names (and default values):

• Define mandatory and optional properties and default values for a node_type.
  
• When adding a new node select the respective node type (or template) (ideally a default could be defined)
  
• Afterwards Neo4j Data Browser UI would present the respective form with property names and default values.
  

Is this one can already do with Neo4j Data Browser UI ... or maybe with some add-on / hack?

[Javier de la Rosa]

On Sun, May 6, 2012 at 9:38 AM, Roman <roman.b...@googlemail.com> wrote:
> Define mandatory and optional properties and default values for a node_type.
> When adding a new node select the respective node type (or template)
> (ideally a default could be defined)
> Afterwards Neo4j Data Browser UI would present the respective form with
> property names and default values.

+1.

At the risk of sounding a bit off topic, that is exactly what the
platform we are developing provides, relaxed schemas for Neo4j,
storing them in an external relational database through Django. Sylva
is the name [1], in development yet. For testing you can use the
username that1 and the same for the password.



[1] http://beta.sylvadb.com

--
Javier de la Rosa
http://versae.es

[Roman]

Javier,

I've had a look at [1] Sylvia. Yes, sth like those schemas would help.

[Michael Hunger]

You could also store the schemas in the graph, which would allow you to link the instances of the schema definition to the actual schema nodes which might add some interesting query capabilities.

Michael

[Peter Neubauer]

Javier,
very cool approach! I like the flexibility of that. Would be neat to
have the type info stored in the graph itself, so the whole sytems
becomes self-sufficient?

Cheers,

/peter neubauer

G:  neubauer.peter
S:  peter.neubauer
P:  +46 704 106975
L:   http://www.linkedin.com/in/neubauer
T:   @peterneubauer

If you can write, you can code - @coderdojomalmo
If you can sketch, you can use a graph database - @neo4j

[Javier de la Rosa]

On Mon, May 7, 2012 at 4:42 AM, Peter Neubauer
<peter.n...@neotechnology.com> wrote:
> very cool approach! I like the flexibility of that. Would be neat to
> have the type info stored in the graph itself, so the whole sytems
> becomes self-sufficient?

Thank you, Peter. Each node and relationship is marked with the id of
the schema type. We are using the same instance of Neo4j for handling
all the different graphs for every user, we hope to be able to sell
custom instances sometime in the future ;-) The inclusion of the
schema data in the graph sounds definitely good, but it adds overhead
when you query the graph or do some algorithms on it, so you have to
exclude the schema types nodes. For the time being, you can export the
schema in JSON and the data in Gephi separately.