| Node/Link | Property Name | Don't Use / Should Implement | Remark |
|---|---|---|---|
| Node | x | Don't Use | Reserved for system use |
| Node | y | Don't Use | Reserved for system use |
| Node | z | Don't Use | Reserved for system use |
| Node | vx | Don't Use | Reserved for system use |
| Node | vy | Don't Use | Reserved for system use |
| Node | vz | Don't Use | Reserved for system use |
| Node | fx | Don't Use | Reserved for system use |
| Node | fy | Don't Use | Reserved for system use |
| Node | fz | Don't Use | Reserved for system use |
| Node | __threeObj | Don't Use | Reserved for system use |
| Node | color | Should Implement | Optional: set font color |
| Node | namespace | Should Implement | Optional: for subgraph separation |
| Link | source | Don't Use | Reserved for system use |
| Link | target | Don't Use | Reserved for system use |
| Link | __curve | Don't Use | Reserved for system use |
| Link | __lineObj | Don't Use | Reserved for system use |
| Link | __photonsObj | Don't Use | Reserved for system use |
In the EonGraph project, it is a must to use a user-generated ID in Neo4j for robust and portable node identification.
all node must have a id that is unique, this id must not be named "id"
Why?
Short Answer: It’s better not to name your user-generated ID simply id. Instead, use a more descriptive property name (like userId, uuid, productId, etc.).
Why Not Just id? Neo4j already has an internal node identifier that can be accessed using the id() function. Naming your property id can cause confusion, especially for new users or when reading Cypher queries. Explicit and descriptive naming helps maintain readability and prevents accidental mix-ups between your property and Neo4j’s built-in identifier.
all neo4j links must not have any props that already exist on the connected 2 nodes(to avoid duplication of datas).
use props instead