Use case or problem
First of all: I love Bases – thank you for this amazing core plugin!
One powerful feature is the ability to define filters for:
- All views in a base, and
- Specific additional views (a filtered subset of the all-views-view)
This opens up great possibilities for organizing notes.
In my setup, I use a total of 5 views within a base:
- One main view: “Reste-Table”
- Four additional views: e.g., for folders like
Atlas/notes,Atlas/Maps, etc.
The idea is to use “Reste-Table” as a catch-all view that lists only those notes not covered by the 4 additional views.
To achieve this, I create a manual filter in “Reste-Table” that excludes the views used by the other views. This results in a “cleaned up” remainder list, which is very helpful for spotting uncategorized or leftover notes.
For the purpose of greater clarity I use it like this: The first view, called “Reste-table”, lists all files, which are not included in the 4 additional views (I use a filter to excluded these 4 additional views):
Proposed solution
It would be extremely useful to have a filter property like:
!view.contains("XYZ")
…or a more intuitive UI filter like:
Exclude notes shown in view: [Dropdown with existing view names]
This would allow users to define remainder or differential views much more easily — especially helpful in complex Bases setups.
Benefit
- Simplifies creation of exclusive views
- Reduces redundancy and manual errors
- Encourages more creative use of multiple views
Current workaround (optional)
To create this kind of “exclusive view,” I have to manually replicate here the filter used in the other views’ filters. This is tedious and error-prone, especially when maintaining or restructuring views later.