A Property representing a node
Here's an example, you have a project (which is represented by a node in Ganister). This project is run for a particular product (also represented by a node in Ganister). When you create the relationship between these two nodes, you could potentially use a basic tab where you would attach the product to the project. But every time you have a project it only refers to one product, therefore it might be a better user experience to have a property in your project form where you could select the product. This is what we call a node-property. It looks like a property for any user but it is actually stored as a relationship in the database.
Keeping the graph concept intact
In most SQL based systems, such property would be represented as an ID in a text property. Ganister keeps the graph concept intact. If it is a relationship, it should be stored as a relationship. We are at the beginning of consuming graph data with graph databases. If we start taking care of our semantic data right now, who knows what we will be able to do with such great data graphs. This is the best way to prepare yourself for your next IT move into predictive operations, artificial intelligence and more.
The Video !
The following video shows you how to configure a node property, by first taking care of the datamodel before adding the user interface elements.