An interesting tidbit is that if you create multiple tags in the tags inline propertie there is a way for dataview to show only one by flattening the tags array and selecting only the ones we want to show.
You have to flatten the tags array and select into another variable ```dataview TABLE Tags, Customer FROM -"Templates" AND #type/project AND #status/review FLATTEN array(filter( file.etags, (t) => startswith(t, "#status/") )) as Tags WHERE length(Tags) > 0 ```
@@IgorTerrosoThis is amazing! Thanks for sharing the code examples. Will definitely have to show this to others in an upcoming sessions. Appreciate it!
How can you have tags on a property that is "Text", and still filter by those? On my side they are not recognized as a tag, and hence I can't filter :( Is it a different plugin you using that enables that??
Hmm.... I think any tags defined as "text" has to then be queried by Dataview with a string matcher like contains(). Personally I'll be avoiding using raw text tags rather than the built in tag functionality. Let me know if that's not what you mean though!
hey @@BenCodeZen ! Thanks for your answer, I'm just seeing it now :) I think I finally came to understand the behavior you explain, as you comment on 18:15(Using status), text properties are not able to contain tags. My issue with putting everything in the "tags" section was that it makes it harder to filter and show nicer dashboards(if I have multiple tags, imagine "#type/project" and "#status/on-going" and "#tech/ai"), becomes messy quick. I understand now these are issues come with the tag system, not my setup, and my solution is to move completely to notes and links. I'm converting every tag to a note, and then will be able to use them from anywhere(even text properties). I find it gives me more flexibility when browsing notes, I can have dashboards in the "tag note" that give me counters and whatnot, and filtering and "tagging" becomes simpler(IMO). The only thing I have to sacrifice is the # syntax and the native nested-capability of the tags, but that can be faked with convention on my "tag notes" too. (With aliases I still can make everything look like tags in the UI, while having my own syntax "on the back") For anyone having similar dilemma, this post kinda enlightened me about the dichotomy: forum.obsidian.md/t/a-guide-on-links-vs-tags-in-obsidian/28231 Would love to hear your take on one way vs the other, but regardless of that, Thank you so much for the content, helped me so much! :)
Hey @wanderingmoon9772! Sorry for that confusion. Something I must not have done a clear enough job on is that the Obsidian Dataview plugin is a prerequisite of sort for this video. blacksmithgu.github.io/obsidian-dataview/ The idea being that once you learn how to query for notes with this plugin, we can then talk about Dashboard design thinking. The core of it boils down to a codeblock in your note with the format you want, what kind of notes you want to look for (i.e., by tag, date, etc), and then any other limitations like how many you want to display. ```dataview LIST FROM #category LIMIT 10 ``` This alone should hopefully provide the context you need for the video to make more sense. Let me know if you have other questions though!
