Another great post! And thanks for the Properties Wrangler plug. I expect @argentum’s feature request “Properties: Recognize tags in text property when formatted as "#tags"” is also relevant to mention which may approach a kind of compromise to the functionality you describe here?
Always appreciate your thoughtful insights on this wonderful tool.
See my previous message about how tags could be used:
About the automatic link generation i.e. “clickable and easily searchable”. You can use Obsidian URI to perform searches by clicking links. Putting these links manually into properties can mess up property value based queries but you could maybe use css to display links so that property values would remain untouched.
I’m 100% sure that in future there will be a feature in Obsidian to easily generate links from searches. You could then put them to your properties as text properties or use css to indirectly have links in your properties. I’m not sure if search links for properties could be generated implicitly in general as a feature because we don’t know exactly what should happen when you click a property value (you could want to edit it, copy it etc). With tags you know what to expect when you click it. We could apply same logic to properties and introduce new property types that will create search links implicitly. These could be called super properties.
This meta requests are hard to track.
Could you kindly open a specific FR about quick searching from properties UI?
you don’t need to use dataview. you can use the global search with [people: prominent] Search - Obsidian Help
Regarding the nested properties, I am not sure what you mean or if you mean the same thing that this highly popular FR is asking Properties: Support multi-level YAML (nested attributes)
Another tag advantage is that I can use them inline, meaning they can reference a specific part / sentence in a note. In search that context is shown.
Hi. Does this currently work for searching boolean/number/date property values? I haven’t got it working.
Not, yet. there are open FRs for number and Boolean. You can open one for dates.
In your screenshot, you have links for the up and down properties but not for the domains and fields properties. I’m just wondering why this is the case? Not for any judgmental reason, just genuinely interested.
great question, it’s because of this:
While Octavia Butler’s work can be classified under Art and Writing, I don’t want a note called “Art” to have every possible person who I’ve classified with Art to show up there.
It’s a preference to keep links meaningful. I’d rather have my notes linked to “Art” be about art. This is especially important early on in a new note’s lifecycle, where the entire tenor of a note is influenced by the notes already linking to it.
Instead, being able to run a looser tag-like search (where clicking on it would populate results in the sidebar) would be preferred. The functionality is mostly already there to pull it off:
Somebody already mentioned my FR above (Properties: Recognize tags in text property when formatted as "#tags"). Not sure what is the difference between this FR and mine?
Hi. What do you think about my idea of “super properties” that I presented in this thread (I haven’t yet received any comments)
Seems a bit convoluted, for me personally, since we already have a core feature that is linked (if not meant) to search. I like that tags are explicit with the syntax. CSS and backend shenanigans go a bit against the “plain text” philosophy imo (and I’m not even sure this is at all possible with CSS… but I’m no expert there).
Very much this!
From 2020-22, I had a weekly scheduled 1:1 meeting with my manager. Throughout the week, if I saw an item I wanted to discuss at that meeting, I tagged it with his name. Just before the meeting, I compiled the list into an agenda and was able to get through the meeting quickly and efficiently.
Thanks for sharing this! Tags are definitely useful regardless of properties. Your example shows that tags are not going anywhere. People know how to use them effectively.
To every reader: see my other comment if you want a general picture of how tags could be used.
I’m smiling with you as you pulled up that inline note. Always a good feeling.
I use tags pretty heavily. To begin with, this was honestly carryover from Evernote, but I find that they help me in a similar manner as MOCs (used in tandem with MOCs) to manage bottom-up organization structure without getting lost.
I tag my notes with all the major subject areas they fall under – essentially what would be, if I were using Dewey Decimal numbers, the equivalent of tagging a note as 600 and 640 and 647. Because they’re not in a hard structure, I can tag them for multiple categories if there’s overlap. And I can certainly use the note outside the obvious designation(s). But it means that if I’ve made a lot of small notes that have otherwise gotten somewhat “lost in the depths” of the vault, I can still find them – and I often will pull up a whole section that way in order to start a MOC and reorganize things.
I strongly agree, Nick. It will be great to have feature parity since I think properties are the future.
But for now, I continue to add data in two places: (1) frontmatter and (2) tags, so to get benefits from both metadata approaches. I would prefer, though eventually, to use Properties.
I’ll draw some attention to this post for more feedback.
Especially using tag wrangler to make “Tag Pages” by adding tags as aliases to a note, so they then appear as unlinked mentions. Pretty cool!
Well said. I agree and wait for devs to make their next steps.
Ah yes…
One of the many reasons why I won’t be upgrading to properties any time soon. There is a fluidity to my current system and properties would throw all that into turmoil/