Obsidian Properties: Best Practices and Why?

I was trialling the following:

---
aliases: 
author: 
date: 
citation:
series: 
url: 
related:
folks: 
locations: 
tags: 
---

But then I realized that related, folks, and locations should just be [[linked]] in the content of my note. So then I was left with

---
aliases: 
author: 
date: 
citation:
series: 
url: 
tags: 
---

I then removed citation because why should I duplicate what Zotero does so well: one app, one job. I also removed series because I realized I was just “collecting” that information for no real reason and it’s really the individual books in a series that I focus on, whereas creating a note for a series of works didn’t add value. Thus,

---
aliases: for synonyms and titles
author: only [[linked]] if I think I'll be interested in learning more about a particular author, or if I myself am the author
date: to follow trends over time in my research and my personal journaling
url: for quick access when needed
tags: for the status of a note
---

I would say “tags” is my biggest open question. I use YAML tags for status, but I use inline tags for other metadata, like #inspiring. I feel like I am under-utilizing tags but this is more a question of process.

In conclusion, very pleased with Properties! Hoping for some added functionality that will support quick refactoring sessions in the future (see my feature request on bulk removal and renaming if interested.

5 Likes