EN | PT

All my notes in Obsidian are created using the Unique Note Creator plugin and a single template containing all the properties I may need to find a note or to add it to a Bases table. You can read more about my setup here.

After some trial and error, I settled on a group of properties that I was happy with, but I still tweak it here and there from time to time. This is the latest iteration that I’m currently using.

title
Format: Text
For the note title without worrying about prohibited characters.

date
Format: Date & Time
Date and time auto-filled using {{date:YYYY-MM-DD HH:mm}} in the template.

duedate
Format: Date
Notes that I have to come back to in the future are listed in a Bases table ordered by the duedate property and with the status property set as unchecked. It can be something that I have to revisit, a document expiration date, or anything that I need to do in the future. This was also added in preparation for the upcoming calendar view in Bases.

number
Format: Number
As the name implies, it’s for numbers. Some examples are kilometers I ran, podcast episode numbers, document numbers, and, more recently, I started using it to track fuel consumption, previously handled by the liters property.

value
Format: Number
Anything related to money. It can be the price of something, what a client or a collaboration paid me, a receipt, etc.

location
Format: Text
For geographic coordinates separated by a comma.

url
Format: Text
Links to my blog posts automatically created by the Micro.publish plugin and Web Clipper links.

file
Format: Text
Sometimes I need to have a link to a file on a Bases table. For example, a podcast episode MP3 file or a client invoice.

card
Format: Text
If a note has an image, the address is also added to this property. In the future, if I create a card view on Bases, I’ll know which property will show images on the card.

type
Format: Text
For specifying the type of the note. For example: Blog, Session, Meeting, Clipping, Itinerary, etc. This, together with the tags property, are the core elements in most of my Bases tables.

collection (formerly “company”)
Format: Text
The name of any group, entity, or collection. If it is a company name (clients or collaborations), this property links to the note containing corporate details like address and tax number. If it is the name of one of my YouTube channels, the note likely contains a future video script. If it is a book title, the note will include details such as the cover and bibliographic information.

unit (formerly “people”)
Format: Text
A sub-categorization of collection. For a team member note, the title would be the individual’s name, collection would be their company, and unit would define their position or department – for example, “Marketing.

tags
Format: List
Used as a sub-categorization of type. For example, for type: Itinerary, I always add cities I’m traveling to as tags. In the case of type: Blog, I’ll include the main topics I mention in the post, e.g., Obsidian, Bases, etc.

status
Format: Checkbox
It is pre-set to false (unchecked), and I use it as an indicator of something I still have to do on that note or with the information in that note. For example, I have a Bases table set to look for notes with type: Clipping and status: false. When I read that article, I simply set the checkbox as completed, and that item is automatically removed from the table.

If you're struggling to manage your information, I can help you implement the Timeline System using Obsidian. Learn more about my Online Consulting options.

List of the Categories

(in case you want to copy them)

title:
date: {{date:YYYY-MM-DD HH:mm}}
duedate:
number:
value:
location:
url:
file:
card:
type:
company:
people:
tags:
status: false