I have totally no experience with graph dbs. Created only today some container to test with, created some nodes and queries. So forgive me for some incorrect assumptions ;)
I am interested in having something like a slider element that you can slide across a time period to visualise data 'active' during the selected timestamp.
I assume the nodes will need to have some interval property on basis of which they will be shown or not. In this blog[1] I see some 'from' properties having a timestamp.
Is 'temporal' functionality fully supported or are these more or less hacks to create this behaviour?
Is there some specific way this 'temporal' functionality needs to be used or do you just create your own timestamp fields and query those?
Are there checks on created relationships so that they can only exist during this interval and not outside this 'active interval'
I also constantly see this KeyLines and that you need apply for a license and on this forum I saw finally some alternative (I think) Gephi[2]. I thought about combining this with three.js[3]
What would be currently an easy, open source choice for getting this slider on the client. As an alternative I could also have a drop down with dates or so.
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
Yes something like that indeed. But I don't think this bloom will be the correct tool for visualising some data on a website.
I also like to combine this with some 3d library or so.
"it is possible to translate them into the same timezone."
I guess if I store in each node a start and end date. I can use the these functions to determine if the node was available during the period of the 'slicer' position.
And if this is not sufficient I would be able to generate some user defined function that takes a current timestamp, a start timestamp and an end timestamp or interval and returns a boolean true if current is in the period, correct?
This slicer is 'mandatory' for what I currently want to do. I really like users to be able to see changes through time. Having some drop down to select a time is not so nice.
I got the idea that temporal properties in graphdbs are not so commonly used. That is why I am investigating a bit.
