[Eji1700]

I think the one thing that really kills me is "consolidating" data is harder than it probably should be.

A simple thing I started with was "lets track movies and shows people recommend to me and I watch".

Ok, page for each rec, and then I can use props to tag them with things like if I watched them or not, who recommended them, genre's, and most importantly, if it's just for me, or also something the wife would enjoy.

Well....obviously I'd like to have a quick view on some page of the recommendations, and then ideally the recommendations that are tagged to include my wife so I can glance view between the two.

Thiiiiiis is not as easy as it should be. I'm writing this as some massive sql vquery on a couple billion records churns away. I'm not great (i'm much less impressive than that previous comment sounds in fact), but im way above beginner. I'm shocked at how hard this seems to be.

Tag searching is possible, but it gets ugly fast and sucks to constantly have to do and the bookmarks weren't clear.

Want to do queries, oh there's a plugin for that. Kinda odd but ok. Oh but wait those too are ALSO kinda of unintuitive (to me, i suspect it's a syntax and style I just haven't used to some extent), and why do I need to do a massive custom dataview query to just get what I feel should be built in? Why can't I just say "put in a query result for anything tagged with x and y", since that's what i'm typing out the hard way?

I haven't really "dug in" on this issue in awhile. I know they made some changes somewhat recently that allow some of this, but it seemed like it wasn't enough. It's baffling to me, because having a "dashboard" is the end goal of almost all these systems, and yet it seems so difficult in obsidian even for technically minded users. I can learn it, but god knows I don't need ANOTHER personal research project on my pile.

I'll admit that by griping about this i'm praying I get they "hey idiot" response below that explains how I should've done this.

Edit- To be clear, this new change certainly seems like it might help. It'll depend on how those views work in practice, and obviously appeals to me in my databasing mindset.

[bitexploder]

Remember, this is basically your own personal Wiki. You can either embrace and accept a rigid organizational structure or not. You are signing up for a lot of up front maintenance and design this way. The alternative is to heavily use links, tags, and other tools that make it easy to find data later.

For a personal knowledge base I think the latter approach saves time in the long run. I have clusters of well organized information. Well tagged and linked. I can always find my movie ideas, projects, and deep thoughts when I want them. I like the idea of just curating the clusters I care about. Just enough organizing. I then have a few highly connected entry points to my clusters. Often I find people don’t link enough in their Obsidian. It’s free and puts things in a more graph oriented layout that the tool can show you.

Edit: oh, also remember, these are text files. Grep still works. Also, we have very powerful CLI LLMs to summarize and categorize text data rapidly. Like “suggest 3 tags for this document based on <prompt magic here>. :)

[Waterluvian]

No “hey idiot” but for what it’s worth: are you making things too complicated? It almost feels like you’re a bit distracted by all the dimensions of data you want to track. Could this all be one page with a bulleted list, each one might have sub bullets if you care to record things like who shared it and other notes? You can just Ctrl+F for “wife” when you need that sub query.

[Eji1700]

This is kinda where I get to "then why use obsidian?". Like to me the whole point is to kinda have some linking and clean notes organization, and i'm keeping it fairly simple (just some basic tags). But yeah I suspect a large part is trying to bend it into something it's not.

[al_borland]

I’ve been using Obsidian at work for a few years now, and things like this are why I ignore almost all Obsidian content on the web. Everyone seems to create these really complicated setups, in the name of zettelkasten, that seem nearly impossible to maintain and use in real life. If I want to make a list of movies to watch, I use a simple checklist in one note and move on with my life. I keep Obsidian simple so it gets out of my way.

I tried going down the road like you’re talking about one for managing past, present, and future trips. It technically worked, but it was so fiddly that I hated using it. I just made a few folders instead.

I suppose now, if I wanted all the metadata you’re talking about, using a base would make the most sense. But I’d still need to be realistic about how I’m going to use it. Do I care enough about future sorting abilities to turn adding a movie to a watch list into a multi-field form, where I need to consider all these potential futures to fill it out, creating a lot of friction to the action?

[azeirah]

The default search is not great and the syntax of the dataview plugin is not amazingly well designed. Even the author of dataview admitted to that.

The author started working on a new dataview-like plugin called datacore, but that project is stalled afaik

[Ezhik]

Hyperlinks are all you need: https://ezhik.jp/hypertext-maximalism/

[Eji1700]

I sorta agree, but i feel like i just want the "one more step" of dynamic content for this.

The hubs described are nice, but they don't always reflect larger changes. Updating a hub becomes a dependency that seems silly as I feel like that should be one of the easier things to keep up to date with a basic code overlay. It's one of the first things I wrote when messing with Obsidian, and part of why I really like dendron (easy refactoring, but it's got other issues).

[simgt]

I like that simple rule, I'll give it a go. Thanks for this shameless plug ;)