Alexandria logo Alexandria

Use case: Live dashboards with Link DB

Alexandria does not have a saved-query engine today. The real building block is a Link DB Table: a live table you insert from the editor's slash menu (/) and point at a tag.

Use it for overview notes, project dashboards, reading lists, or any place where you want a note to include one or more tag tables.

Open the dashboard note where the table should appear. In the editor, open the slash menu (/), choose Link DB Table, and select the tag to show.

The app inserts the live table into the note and keeps it connected to that tag. Under the hood, this is stored as a short <link-db id="tag-id"> embed, but you normally do not need to type that syntax yourself.

2. Prepare the tag it points at

A Link DB Table needs a tag. In a note's tags bar under the title, type the tag name and pick an existing tag or create a new one from the dropdown.

If the table should show structured fields, open Manage Properties on the tag, then edit its Tag Properties. Add each property with a name and type, such as status as select, priority as select, or due_date as date.

After applying the tag to notes, set their values inline in each note's properties panel.

You can include more than one Link DB Table in the same note:

## Project dashboard

### Tasks

[Link DB Table: Task]

### Decisions

[Link DB Table: Decision]

### Meeting notes

[Link DB Table: Meeting notes]

Use headings to explain what each table represents.

What you can do in the table

A Link DB Table shows notes tagged with the selected tag. In the app, it lets you:

Changes to the tagged notes or their properties are reflected in the dashboard view.

Current limitations

Not a query engine. Link DB currently:

  • Requires a tag.
  • Shows all notes for that tag.
  • Has no saved queries.
  • Has no filtering, sorting, grouping, or column hiding.

If you need a narrower table today, create a narrower tag and apply it only to the notes that should appear in that view.