Database
The database is the home of every element and relation in a project. It is the structured view of all that data.
The Database is primary. Every entity in a project lives in its Database. Maps and Page views project from the Database — an entity can exist in the Database without being on any Map, but cannot be on a Map without being in the Database.
Sub-views
The database supports four sub-views:
- Table — rows and columns, spreadsheet-style
- List — simplified row view, fewer columns visible
- Board — columns defined by a single-select property (kanban-style)
- Gallery — card grid
Capabilities
- Filter — show only elements or relations matching a condition
- Sort — order rows by any property
- Group — arrange rows by a property value
What the database shows
Every element and every relation in the project. Relations appear as rows alongside elements — they are first-class entities, not just columns. The Database is the union of all entities; Maps are subsets.
Relationship to Maps
- Adding an element to a Map first ensures it’s in the Database (creates it if new).
- Removing an element from a Map does not remove it from the Database.
- The Database always shows entities even if no Map currently surfaces them.
Vocabulary note
“Database” replaces “library” and “index.” Neither term is in use. Never use “library” or “index” when referring to this view.