I’m trying to find a way to use bases without creating a new page for every single iteration, every single view and every single filter setting.
I have e.g. video games in my vault, one page per game.
I have pages for the relevant franchises. On those pages, I have lists of all the games belonging to that franchise (right now I use Dataview).
If I embed my existing games Base and filter it to show only the games belonging to that particular franchise, this filter is applied to all pages that have this base embedded.
Meaning, I would need to create a new base for every page, and sometimes more than one base per page.
Is that intended? I’m not sure this will scale very well.
You can create a dedicated view, filter the dedicated view using the menu This view instead of All views (in Filters) and then you can embedded the dedicated view where an when needed using ![[myBase.base#mySpecificView]] …
e.g.: if your game notes have a key franchise and you create a view meant to be embed in a “franchise” note, you could potentially use a This view filter stating something like: where contains(franchise, this.file.name).
The view won’t display anything within the .base file (due to this.file.name) but it could (depending on how your Properties/Frontmatter setup) return the list of the game per franchise by comparing the value of the franchise key to the name of the “franchise note” in which the view is embedded.
… or you can create a view per franchise, use directly the value of the name of the franchise within the This view filter and embed that view within the corresponding franchise note.
(This one should return results within the .base file)
There’s no right or wrong here … As it would depend on the use you want to make of base or one of its view (your frontmatter/properties setup, etc…) …
…