brainannex 5.0rc2

Full-Stack Data/Knowledge Management with Neo4j

Brain Annex

Version 5 of is a complete overhaul of Brain Annex's internal structure.
This major new release is in a release candidate stage.

The bottom layer (the NeoAccess library) is stable, and is being released independently.

The version number can be found in the brainannex/__init__.py file.

Website: https://BrainAnnex.org

Change Log

Brain Annex's Technology Stack (Overview)

NOTE: the bottom layer, or layers, of the stack may be used independently of the layers above them, if desired.

From lower to higher levels:

• Neo4j graph database (v. 4.4)

• NeoAccess library (python interface offering many services)

• NeoSchema library (optional Schema layer)

• Python/Flask (for web API, and web app pages)

• Vue2.js

EXAMPLE of use case : Multimedia Knowledge Representation and Management

Motivation and overview

What are Neo4j/Graph Databases, and why do they matter?

If you're new, here's a gentle brief intro.

Brain Annex's Technology Stack (Details)

Brain Annex may be used as a standalone web app, or used to power other web apps.
The libraries that are the bottom layers may also be used independently.

How to set up and use Brain Annex

Brain Annex, if used in its entirety, supports both local and remote setup of the web app and of the Neo4j database.

The database and web app may reside on the same or different machines.

You may also opt to simply use some of its library: everything is very modular!

SETUP

INSTRUCTIONS

EXAMPLES of Schemas available for import

(For instructions on how to import the Schemas, see the setup page, above)

EXAMPLE 1 - the available default Multimedia Content Management System

The ROOT node for the Categories is shown in blue at the top.

---

EXAMPLE 2 - same as example 1, but with sample extra Classes (representative of user-added schema)

The diagram below is split in 2 parts, for readability.

"chem" is an example of a custom Class.

The following second half of the diagram shows the remainder of the Schema, detailing Classes that are instances of the "Records" Class. Most of the items in this diagram are examples of typical user-added schema:

Optional: add Neo4j Indexes and Constraints

Not strictly needed for test runs, but at some point Neo4j Indexes and Constraints need to be added, for speed and reliability. From the Neo4j browser interface, issue the following Cypher commands:

CREATE CONSTRAINT unique_BA_ID ON (n:BA) ASSERT n.uri IS UNIQUE
CREATE CONSTRAINT unique_CLASS_ID ON (n:CLASS) ASSERT n.uri IS UNIQUE
CREATE CONSTRAINT unique_CLASS_NAME ON (n:CLASS) ASSERT n.name IS UNIQUE
CREATE CONSTRAINT unique_PROPERTY_ID ON (n:PROPERTY) ASSERT n.uri IS UNIQUE

Major components

• NeoAccess : a library to connect to Neo4j with python. It provides many services. Link

• NeoSchema : a higher-level schema-based library on top of NeoAccess. Link
  Article explaining this layer

• CK Editor : open-source JavaScript library to implement an online HTML Editor.
  Website. (Note: Brain Annex uses version 4 of the CK Editor)

• API : the endpoints appear in this file

• Web pages : the pages generated by Brain Annex are listed in this routing file

• Navigation bar : Brain Annex can be used either as a standalone web app, or integrated with another site.
  The navigation is implemented in this package

Project website: https://BrainAnnex.org

The lead author of Brain Annex can be reached on LinkedIn