Note Database Plugin

Greetings, Helga!

Thank you for pointing out a very nifty looking plugin that has been probably off the radar for most people around here. Hence, no replies.

Well, it was new to me, anyway, and looking at the options people have for a Bases + Calendar View setup (core solution by the team is on the roadmap)

I daresay this is something I could use.

By the way, people who use the Bases core plugin would probably couple with one of these community plugins to add a calendar layout on top of it (I haven’t tried them myself, so treat these as pointers rather than recommendations):

Summary

Now, to address your concerns:

1. Showing properties inside the calendar entries

I had plugin’s source code looked at by an LLM to see whether this can be done, and as far as I can tell, not out of the box. A month-view event only contains the title, the time, an icon and (for multi-day events) the date range.
The property values aren’t in the entry at all, they only appear in the detail pop-up when you click on a note, so a CSS snippet can’t pull them in. Showing a line like produkt or kategorie under the title would need a code change in the plugin.
What you can do today to tell content types apart at a glance:
a) The click pop-up shows all properties of the note (status, priority, dates, etc.), so you at least don’t have to open the note.
b) Filters in views. You can create several Calendar views, each filtered by one value of kategorie (blog post, photo tip, course, etc…). Then each view only shows one kind of entry.
c) Colors. Status/select options have colors, and the calendar can use them for the entry bars.

I ran into trouble with the *Event color* setting though (it didn’t apply any color for me, see the bug report: [BUG] Calendar view: 'Event color' has no effect (`--db-calendar-event-bg` never set), but conditional formatting with the same values works · Issue #9 · pangy9/obsidian-note-database · GitHub ).

A conditional formatting rule (Record → kategorie equals blog → pick a color) would work for you, including on multi-day bars, so that is a usable workaround.
Just to be clear, issue #9 is a bug report about the color setting, not a feature request for displaying properties under the title. If you want that, it’s worth opening a feature request in the plugin’s repo yourself, since you know the exact use case best. I haven’t filed one for it.

2. Slowness

I only have about a tenth of your project notes, so I can’t say how it feels at your scale. But I did have the source looked at, and a few things could plausibly explain the lag.

Summary

This is from reading the code, not from profiling, so take it as a hint rather than a verdict.

  • The calendar view has no incremental update. When a note changes, table and chart views have a “patch only what changed” fast path, but the calendar rebuilds everything: it re-queries all records of the database, builds a row for every one of them (not just the visible month), evaluates computed columns, and redraws the DOM.

  • Backlink/formula columns are costly. Computing backlinks loops over the vault’s whole link map for every row, so a column based on backlinks gets expensive as notes grow.

  • Some work runs vault-wide, even when no database is open. The plugin listens for metadata changes and rescans every markdown file’s properties (debounced), and any note modification can trigger a disk re-read to reconcile data.

    If you want to try things: narrow the database’s source folder/rules so only the notes you really need are included, avoid backlink or formula columns on the calendar database, and if you’re comfortable with it, record a Performance trace in Obsidian’s DevTools (Ctrl+Shift+I) while opening the calendar to see where the time goes.

Hope this helps, and good luck with the setup!


A CSS I tried for scrolling long filenames in Calendar View was placed here (not effective, if you set due/end dates, though):