Obsidian's properties feature is a useful tool for categorizing your notes, data and all of your inputs.
There is however in my opinion, a danger of getting a properties fatigue wherein I have way too many properties and way too many precise ways of categorizing it.
Property | Use-case |
---|---|
Created | |
Modified | |
Status | Currently being depreciated, but basically just ´Open´ and ´Closed` |
Related | In case I need to see links easier than reading and/or checking the backlinks panel. |
URL | In case there's an URL |
aliases | |
tags | |
Type: | See #Item Types |
Location | |
Related | |
Next | |
Last | |
Object-based note taking is a new approach that organizes notes using "objects." This system appeals to many because our brains often think in terms of objects or things — a book is a book, a note is a note, and a movie is a movie. That's how these applications function.
Danielpourasgharian,
Including objects that I push/create, that I reflect on, and that makes my system work: Each object has a corresponding template in the templates folder.
An object, like a link or a tag can belong in many different places -- see the Dataview query for example
Evaluation Error: SyntaxError: Unexpected end of input**at DataviewInlineApi.eval (plugin:dataview:19027:21)
at evalInContext (plugin:dataview:19028:7)
at asyncEvalInContext (plugin:dataview:19038:32)
at DataviewJSRenderer.render (plugin:dataview:19064:19)
at DataviewJSRenderer.onload (plugin:dataview:18606:14)
at DataviewJSRenderer.load (app://obsidian.md/app.js:1:1214099)
at DataviewApi.executeJs (plugin:dataview:19607:18)
at eval (plugin:digitalgarden:10886:17)
at Generator.next (<anonymous>)
at eval (plugin:digitalgarden:90:61)
Created:
Modified:
Related:
URL:
aliases:
tags:
As a I'm currently refactoring my vault and making it into BranBrain V6, a flatter part of my obsidian setup, I've chosen to stop using folders as much as possible, get rid of the PARA-system as much as possible.
My folders are now sorted into