Obsidian Properties: Best Practices and Why?

I have (as many others) different areas in my vault.

  • Daily notes
  • Infos about groups I have to teach
  • Infos about group members
  • Tasks for my group members
  • Infos about Obsidian plugins
  • Knowledge of all kind

For these notes I use individually defined templates to have the same strict structure for dataview queries. And I hold these notes in - separate folders.

These fields are the same in every template:

aliases:
tags:
filename:
uid:
erstellt:
geändert:
Wiedervorlage:
Info:
draft: true
prefer-view:

(They correspond round about to my smallest template.)

The complex groups and tasks notes have a lot more (~ +27) properties. I need them all.

The more notes of one kind I have, the more this structure is necessary to query them later with dataview.

Works fine and (after a lot of thinking):

So easy.

2 Likes