Your data

Hummi is a joyful interface to your data Your data is your data. You can keep it to yourself in local storage. Or you can sync it to the cloud to have it available wherever you need it. If you want to share a cloud-synced database with a person, or your team, you can grant them read or write access tied to their email address. Access is always restricted to secure login.

The Contextual Data Model

This explanation is about the differences between tailored and contextual models. The article explains what a contextual model is, and what benefits it provides. Definitions Tailored model: Facts are entered into the database as they are discovered. Keep all data. Keep provenance. Domain model is defined by the application designer. Contextual model: Facts are asserted within a context. Entities are targets for records and links. Records and links are made in the context they are collected.

Hummi Grammar Explanation

Hummi Grammar is a subgraph description language designed for incrementally building a diagram (graph). Input is consumed from a textbox to produce either a standalone node, or a compound set of related nodes. See Hummi Grammar Reference for a formal definition in ENBF. Rationale Creating and linking nodes individually is tedious. A little notation greatly reduces time to add nodes and relationship to a graph. Given a node and multiple connections, we can create the nodes and edges much faster with notation:

Fast Link

When Nodes are added to a diagram they are initially linked to any previously selected node(s), and the current selection is changed to the new node. Typing “A” and pressing enter followed by “B” enter followed by “C” enter will create a chain of linked nodes A -> B -> C. Keep in mind you can change the current selection before pressing enter to add a new node, thus ensuring it gets linked from the intended node.

Data Modelling in Hummi

The flexibility of datalog in a fluid UI. Hummi stores everything in a database. Hummi enables user modelling. Build queries with UI Express graphs optional edges (a node may have no edges) constraints on edges (exclude edges to nodes that are not in the node set) bfs or dfs to find more nodes by edge when allowing inclusion of external nodes Update results. Every value must be tied to an entity Every column must have a name (for table view) especially optional many rels Entities A collection of attributes with associated values.