Use case or problem
BASES only work with notes.
It is logical for a database, but actualy usecase and functional of BASES is not exactly like that.
They lack support for Nested properties for complex data strucutres.
Its main purpuce is organisation and catalogue of notes.
But use of bases liberaly would produce endless notes.
As one note, can hold only very small amount of data.
Proposed solution
Using Virtual notes, would solve all of it, in an incredibly easy way:
The idea is very simple:
Form perspective of bases, note is just a number of yaml properties.
It means Nested Yaml property, by Itself, also matches that definition.
By virtualsing nested properties with a specific keyword.
A single note can hold many data entris.
---
Book1:
Author: Author 1
Rating: 2
test: nya
Book2:
Author: Author 2
Rating: 4
test: nya
---
Is a simple example of that, albeit not very needed as books can fit nicely with one-note per book.
But not everything is like that.
Having a note per Event be it for a story, timeline or so one, gets out of hand quickly.
Or rather, it forces to make compromise, and compress data in less usefull strucutre.
Undermining the point of using a data driven sturcutre in the first place.
Another way to utilise that, is ability to add micro notes for information usefull, but otherwise overcrouding the note. For example this way, you can add data for characters in a book you read, without having to add a whole separate note for that.
At the same time, as it is still effectively a part of the book note, it allows to use formulas to sort and filter based on that!
Another example are location markers, and it is the main reason i belive this should be added as a feature into the core plugin of bases, rather then added as plugin on top.
While it makes perfect sence to have a note per marker at the largest scale.
For a map of the dungeon, or a small city. It makes much more sence to use single note, divided by headings. That how it was done with Leaflet. (Or if you need one note to have multiple makers…)
After i through of that, my conclusion is that ANY base view can benefit from such functionality. Witch is why i belive it should be added to the Bases core plugin rather then left alone to plugin authors to impliment.
Nice side effect, is that it effectively adds a way to manage nested yaml, something that was requested for a long time.
Execution proposal:
A new tab near “Filter”
“Virtual notes”
It has a toggle, and a space for filter formula to set whitch of the nested properties should be virtualised.
For a simplest implementation, all the “file.” do not change due to virtualisation
as it is the same file after all.
Still, for better compatibility - it is great to have an ability to select a property name that would substitute the link.
(It can be a subsitition with a full on markdown link, or it can be limited to heading in the note only)
This way, map markers for example would link to different places.
I don’t actually know where map marker takes its link, so possibly ability to select propertis to act as aliases for file.name and such, in general, is actually a better solution.
Current workaround
Is a test plugin with some from of such functionality added on top.
But it is mostly just an experiment site.