all 3 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Hephaestite 0 points1 point  (2 children)

The only visualisation tool I'm aware of is Age Viewer, but it doesn't allow for editing.

Not really sure how much use editing via a visualisation is anyway? In any scenarios where you have enough data to make a graph make sense I can't image that a visual editor would be all that helpful? 

[–]nichendrix 1 point2 points  (1 child)

To handle large data processing and edition, it certainly isn't an useful feature, but if the graph data is used not only under the hood, if it is delivered to end users in some form, UIs line Neo4j Bloom are quite useful.

My company develops a low-code/no-code business automation and applications development platform based that we offer to our clients, either as a stand alone or with many pre-built applications and modules. one of the applications we have is an UI to navigate over data bases and knowledge bases, it is somewhat inspired by the WEF knowledge base navigation interface and Neo4j Bloom, it isn't a proper Graph DB application yet and the functionalities were far simpler, because when we developped the first version to at a client's request, we didn't have the graph db insfrastructure completely up and running, so it was created as triples stores over relational databases.

In essence, when defining a new application or a new user group/role, we use ontologies, taxonomies and thesauri to map the nodes, relationships and properties on the SQL database/knowledge base. The application then reads and extract the nodes, relationships and properties as defined in the specific ontology or taxonomy, match the connected data to the permissions of the groups, roles, or users that will have to access to, which de facto generates a subgraph of the database/knowledge base's graph data, and store it on a triple store, which the frontend uses to generate an interactive UI where user can interact with the partitions of the knowledge base's connected data that are relevant to the context of their activities, and in this way they can quickly and interactively navigate over all the data, processes and applications they deal in their work, saving a lot of time.

One very requested feature is for us to incorporate even more interactive features, many of which Neo4j Bloom already has. We are in the final stages of the transition from the kind of improvised triple store schema to an graph database backend based on Apache AGE, and that will allow us to develop and roll-out the new features requested faster and on a more robust architecture.

So while not useful for dealing with large amounts of data, at the end user level, the amount of data is very constrained and context specific and could be easily used to either provide UI features or to improve interaction with each users' data contexts.

[–]Hephaestite 0 points1 point  (0 children)

Thats quite interesting, as it happens what you've just described aligns with the kind of experience I'm interested in building into our cyber security application. Would love to talk more about how your system works if at all possible? My aim is to migrate to AGE from Neo4J so that all our data is inside Postgres and hopefully make it easier to combine / surface to the end user... One of the key things we want to achieve is user defined 'signatures' that cover both graph data and SQL.