I have found this plugin immensely useful for organizing my notes. Thank you! I am generally a fan of Joplin plugins, also having stuff like the backlink tool added. And this is where there appears to be a bit of a conflict.
I have two Note Overview searches in a folder that list notes created today and the last 3 days, and those work brilliantly as expected. I would also like to have a stored search for notes I have changed/updated the current day and the last n days. Something like this:
<!-- note-overview-plugin
search: updated:day-1
fields: title, notebook, tags, user_updated_time
sort: user_updated_time DESC
alias: user_updated_time AS Updated, title AS Title, notebook AS Notebook
-->
Alas, the combination of several search notes and the backlink plugin updates a lot of notes all the time, so this search includes too many notes.
I have found the field "user_updated_time" (seen above) which appears to do what I want - ie it is updated when I type something in the note but not when a plugin adds something. Please correct me if I am wrong here. However, I haven't found a way to search using this field in the Note overview.
It would also be brilliant if it is possible to search for notes added last 24 hours (or whatever), not only added the last n days which becomes empty past midnight. Let me know if I am missing something.
Edit: With a bit more testing I see that the user_updated_time field is also updated whenever a note is touched by the backlink plugin. I would love to have a time field that is only updated when a note is edited manually.
You can try to use exludes some notes.
All my noteoverviews have a tag noteoverview and I exclude this from my overviews with -tag:noteoverview, since I do not want to see them in the changed list.
This does not exist, because it is only tracked when the note was edited, there is no differentiation by which action type the note was edited. In short, edited is edited and is reflected in the date fields.
The difference user_created_time/user_updated_time (for example to correct the date after an import/set it to the value of evernote) and created_time/updated_time is only that the user_* can be edited, but the others remain on the real date for the sync.
No the time filters works for the complete day/week/month/year (user_updated_time:day-1 means from/including yesterday's day [updated >= 07.05.2021 midnight])
You can try to make a feature request for a real hours filter.
Thanks for trying, I think I'll wait for nested queries . Somehow that search just returned all of my notes! No worries, I can change my workflow slightly for now.
FYI, I have been able to really put this plugin to use on a new project and has been very helpful, thank you!
I love this plugin (maybe I have mentioned this before :-)).
Still, to get me closer to GTD heaven I am still missing 2 functionalities:
1. A filter for due:today
In GTD methodology, I have anote for today, one for "next action" and one for a "waiting for".
The note created for "today" gathers my todos for this day.
I currently filter my todos like this: "search: title:210512" This does not seem to be possible with note-overview and the set of filters that are available currently - all todos without fixed due-date are automatically set to todo_due:1970-02-01 or something. I played around with due:day-0 or due:day+2, but that gives me all future todos indiscriminately.
And related to this:
I would love to have a date format set to YYMMDD (which is nicely sortable and in my eyes more readable). But my understanding is that this would be a Joplin setting.
It's certainly not a technical problem to add another date format. But we thought that we had already covered pretty much all common formats.
There are a few options available depending on Laurent's decision:
add a new format to the core
add an input field to allow custom formats set by users to the core
create an API call to allow setting the date format to a custom value
create a plugin that makes use of the API call
They are listed in order of complexity and the 4th depends on the 3rd. The question is, if we want to spend time on something that only comes up once every few years.
I know that this is important to you, but there are more critical issues to tackle. Since we don't have 20 full time developers, we have to prioritize often more stricly than we want to.
Yes, I agree that there are more critical issues. I thought maybe the sorting aspect gives YYMMDD a bit more weight, as well as readability. But that's just my personal flavour and most certainly not my decision, since I am neither a programmer nor familiar with the priority list.
I installed the update and now get this error Nested mappings are not allowed in compact mappings, but I don't know what it means. Here's the search.
search: tag: * post
fields: updated_time, title, tags
alias: title AS Title, updated_time AS Last
sort: updated_time DESC
I use the note it lives in as an Index of things, so there are 2 other note overviews in the same one (in case that affects things?). The overview still seems to be generating correctly (EDIT: ah. i think it is cached, not regenerating).
EDIT2: It seems like this was caused by the space before the colon next to the word tag: Changing it to tag:*post seems to have fixed it. Leaving this in case someone else hits this error.
Oh, this is from the cange to real YAML syntax. When you really want tag: * post as search query, than write it the following way: search "tag: * post", but i think the search is invalid with tag:` becaus the tag has no parameter.
I will include this in the documentation as a hint.
EDIT1:
Error: Nested mappings are not allowed in compact mappings
This error message occurs when a colon is used in the option value and an space character follows the colon. Just enclose the value of the option in quotes like alias: "title AS : Title :".
This has been one of the favorite plugins. This latest update (image field) broke at least one of my existing searches, and it even pops up a messagebox on each refresh which forces me to remove the search note completely.
It is the implicit map keys errors. The search:
<!-- note-overview-plugin
search:sourceurl:*reddit.com*
fields: title, notebook, created_time
alias: created_time AS Created
sort:created_time DESC
-->
The error box:
I have tried to move the colons around to no avail.
. Somehow that search just returned all of my notes! No worries, I can change my workflow slightly for now.
