Just exclude a title tag:meeting title:21060* -title:210601
But why not use todos and set the date?
They only differ in that there is a due_date and due_completed. Each note can also be easily converted to a todo or vice versa.
Todos are excellent for meticulous planning, where I already know a day/hour/minute until this has to be done.
But I often need a more flexible solution, when it comes to due_date. Could be that sth. is due this quarter, this week or on a particular day. Todos cannot reflect this, can they? So my workaround are the notes with the due_"timeframe" in the title. Maybe others have the same problem?
Cheers,
CoarseGrater
1 Like
Hi Jack,
I have some questions (Joplin 2.0.2 portable and Note overview 1.4.3)
1st: Will be posible to sort by tags?
2nd: When i try to do a search with due:day plus or minus a i obtain strange results.
These are some examples ( iĀ“m not sure if itĀ“s a date format (spanish so dd/mm/yyyy) But i change to yyyy/mm/dd and i obtain the same)
<!-- note-overview-plugin
search: due:day+7 iscompleted:0
fields: todo_due, title
sort: todo_due ASC
-->
Note count: 22
This search must show notes with due dates between today and 7 days after and if today is 3 of june 2021, i obtain due dates as these (remember day/moth/year): 18/06/2021 22/06/2021 20/08/2021 03/10/2021 21/10/2021 17/02/2022 01/09/2025
I donĀ“t understand becouse seams the get all the due dates after today
Show the same results than this one ( if today is 3/June/2021)
<!-- note-overview-plugin
search: due:20210603
fields: title, todo_due
sort: todo_due DESC
-->
Note count: 24 ( This include 2 alert more than day+7 3/6/21 and 5/6/21 )
<!-- note-overview-plugin
search: -due:day+7 iscompleted:0
fields: todo_due, title
sort: todo_due ASC
-->
Note count: 191 ( Show all due before today+7 in my case all before today and 2 notes with due 3/6/21 , 5/6/21)
<!-- note-overview-plugin
search: due:20210603 -due:20210610 iscompleted:0
fields: todo_due, title
sort: todo_due ASC
-->
Note count: 1
The result of these other search must be the same as the first one but only with this i obtain the correct values 05/06/2021
If i try to do with created i obtain a valid view
<!-- note-overview-plugin
search: created:day-7
fields: title, created_time
sort: created DESC
-->
Note count: 15 ( created dates between 27/5/21 till today)
3rd: If we have 2 search with the same code one with alarm with the same criteria as the search and other without it the results are diferent ( the search with alarm donĀ“t include itself in the view )
Finally Can i sugest that the search as code ( I have same notes with diferent search as documentation) donĀ“t be execute by the plugin (those who are inside ```). I tell you becouse i obtain a nasty screen every day i open joplin and when the refresh happens ( default value in my case 5 minutes ). At this moment i delete de code in my documentation notes to resolve the issue.
Tkx in advance.
No
The dateformat is only for displaying
due:day+7 = Gets all todos with due_date bigger today + 7 days
If you want all todos for the next 7 days: -due:day+7 due:day-0
due, updated or created means bigger equal
-due, -updated or -created means lesser than
created:202001 -created:202003 will return notes created on or after January and before March 2020.
The note with the query is exluded in the table
You have a note with the following contend?
```
<!-- note-overview-plugin
.....
-->
```
Thanks for your answer Jack. IĀ“d an unknowled about due: day-7 an now itĀ“s clear the use for me.
About the issue with the code note yes iĀ“d one. There was a best plugin to install in joplin and how to use it with example ( I Ā“ve it to add it in a basic documentation inside joplin if i install a pc for a friend and add joplin in the basic portableapps 7z. But I change the code with an image so you can forget it ).
Tkx again
1 Like
Ok, then it's fine if everything works 
For the problem, will show if I find a good fix. But it is not high priority.
This plugin has turned Joplin into my dream note taking app. Thanks.
I have a request/idea, right now the plugin returns a table would be possible/easy to just return normal text instead of a table?
I would like to compile 3 notes into a single noteā¦ sort of a combine notes (which can of course be achieved by combined notes plugin) but dynamically (which can be achieved by your plugin)
hm ... if I do a complete reimplementation. Then I could possibly include this as an advanced feature.
But I am not sure if I will do this
Hi @JackGruber
I see the prospect of using note/task sharing more and more in a professional context. So I'm thinking that it might be interesting to be able to search/filter shared notes in "note overview" to find them more easily.
As far as I know, this is not possible with the current filters... but what do you think?
Hm do you mean shared notes from the Joplin server?
Oh yes sorry I mean the notes shared with the Joplin cloud !
Do you mean to search notes in Joplin, which were shared?
When yes, this should be implemented in Joplin, simply make a features request.
Yes, in fact, I think it could be useful to be able to search among the shared notes... that would then allow to integrate them into "note overview". (@laurent)
Is it possible to choose whether the column titles appear in the output?
Do you mean centered, left or right aligned or the or the column position?
For the column position, the position in the fields key reflect the column position in the table.
I was wondering if it was possible to hide them completely. I often use the plugin to generate a table with only titles, so if I removed the column header "title" it would just be a list of notes. This is not a very big issue at all, just wasn't sure if it was already possible.
No not possible, but you can use an HTML space, but a empty table header will remain.
<!-- note-overview-plugin
search: -tag:*
fields: title
alias: title AS
-->
2 Likes
Hi @JackGruber I updated the plugin and the Joplin version to Joplin 2.0.11 on Windows 10.
I haven't made any changes to the code and it used to work perfectly fine before the update:
<!-- note-overview-plugin
search: tag: meeting
fields: created_time, title, notebook, size
alias: created_time AS Meeting Date, title AS Title, notebook AS Notebook, size AS File Size
sort: created_time DESC
-->
Here's the error that I've been getting since then and it keeps popping up every couple of minutes
I would be really grateful if you could help or point me in the right direction.
Cheers!
Error: Nested mappings are not allowed in compact mappings
Remove the space betwen tag: and meeting or enclose the search query in "
1 Like
Thanks so much, this fixed the problem!