I noticed that when the search results contain notes without front matter they're still displayed in the table as empty rows. Do you think it would be helpful to have a plugin setting to hide them?
If anyone starts using front matter regularly and would like to search notes by front matter properties, consider trying out the Inline Tag Navigator plugin.
Yeah, that is by design, but I could think about it. My use-case for this plugin is specific notebooks where each note is one item and I would want every item in the overview even if I was "lazy" one day and forgot the frontmatter.
Basically each note that gets returned by the search should be one row in the table, regardless of which properties are missing (except the note where the overview is defined).
But I could definitely add a setting for that if someone has a different use case! I'll look into it.
I've thought about it and I think it might be better to exclude notes without frontmatter locally per overview and not globally in the settings. There might be times when people would want to include them and other times they don't.
Not sure, what a good syntax could be, maybe just something like excludeEmpty: True as an optional parameter with the default being False?
That's a very useful plugin but I would have kept it more generic - something like "Multiple note overview". Then your logic could be the same but you could handle notes without frontmatter too - you'd use the actual note title, author, etc. by default. And if the frontmatter is present, you'd use this.
I say this because probably a lot of users don't know what frontmatter is, so that makes your plugin look unnecessarily technical when it could actually be useful to anyone.
Do I get it correctly that Note Overview plugin is alternative to Frontmatter if you don't want to have custom metadata based filtering and want to only stick with basic note properties?
I've been planning to write this plugin for a while and after I wrote a script to turns properties in an even more specific syntax into a static table overview.
So turning my notes into frontmatter and calling the plugin that was actually already trying to appeal to a broader audience for me haha.
I had actually added the functionality of adding more of the actual note properties into columns, but since most of them don't return the info in a nice, human-readable way, I decided against it.
And also to answer @executed, yes I think the Note Overview plugin already handles that use case.
Although, I don't think frontmatter is only good for filtering based on metadata. It's also just a nice way to capture info about the content of the page in a structured way, so that I can look at a page and know that the info of when I read that book is at the top. I also use it to keep track of the games I own (how many players can play it, how long it takes, when I bought it, link to the rules, etc).
And this plugin allows you to have an overview over those properties.
I love your plugin. That's what I've missed so far for organising my books and reading list.
I used Note Overview Plugin so far but I love this frontmatter thing to have all (for me) relevant informations directly in the header of my note.
Hey, I've just been thinking about how to do certain things in my notes, and this could be really useful for me!
I'd like to request one thing, though: 'backmatter' support. While I like the idea of frontmatter, it annoys me by being, well, in the front of the document. It wastes valuable space and I don't really want to see it instead of the 'regular' note contents. If the plugin supported the same thing, but at the end of the file, that would be perfect.
Thank you for your interest, but unfortunately this is not something I'm interested in adding support for (at least at the moment). The reason for that is that the parsing of the frontmatter is actually handled by this package, so for me to be able to support "backmatter" I would need to handle the parsing myself or rewrite the package.
I guess it would be possible to write a plugin that would hide the frontmatter in the viewer, though it would still be at the top in the editor.
