trove-obsidian-bases

Obsidian Bases

A .base file is YAML describing views over vault files and their properties. Creating a view does not require rewriting the source notes.

Workflow

1. Read the existing base and representative notes. Establish the scope, property names, types, missing values, and available view plugins.
2. Preserve unrelated views, formulas, display settings, and unknown extension fields. Select notes using global filters, then refine individual views.
3. Define computed values in formulas. Reference them as formula.name in view columns and display settings. Note properties use note.name or a bare name; file metadata uses file.name, file.ext, and similar fields.
4. Use table, cards, or list views supported by the installed app. A map view needs the Maps community plugin; do not install it as a side effect. Use a table fallback if appropriate and explain any unavailable requested view.
5. Parse YAML, check filter structure and formula references, and inspect representative results in Obsidian when available. A YAML parser cannot evaluate the formula language. State when runtime evaluation was unavailable.

Read formulas-and-views.md for additional functions, summaries, grouping, and embedding context.

Working example

filters:
  and:
    - 'file.ext == "md"'
    - 'file.inFolder("Projects")'
    - 'file.hasTag("task")'
formulas:
  days_left: 'if(due, (date(due) - today()).days.round(0), "")'
properties:
  formula.days_left:
    displayName: Days left
views:
  - type: table
    name: Active tasks
    filters:
      and:
        - 'status != "done"'
    groupBy:
      property: status
      direction: ASC
    order:
      - file.name
      - status
      - due
      - formula.days_left
  - type: table
    name: Completed
    filters: 'status == "done"'
    order:
      - file.name
      - status