I understand well your point! I don’t have any coding knowledge or similar and I’m not a young too. I’m a simple obsidian user helping others with the knowledge I acquired in using obsidian along a year.
The question here is: you don’t need to know code or similar, but you need to know how to write your notes (particularly the metadata) to work with the tool “dataview”. An example. If you read the documentation, you know that there’re implicit fields and the “created fields”, ie, the first are fields like “file name”, “creation date”, “modification date”, “file tags”, etc. (similar to the data you see in your system); the last are fields created using specific rules.
You said you can’t use the “creation date” because the daily notes created before the right date. So, if you have this habit and you don’t want to change your title format, then you need to think if it’s better create a field to define the right date.
You can create new fields via yaml frontmatter or inline. For now we can exemplify with a frontmatter field.
To add yaml frontmatter fields to your notes you need to write in the first lines of your notes (first lines, without anything before) something like this (3 dashes + fields + 3 dashes):
---
myfield: my value
note-date: 2022-03-02
---
In the example above, note-date can work as the field to use in your task query (because it’s in the right format, it’s the date you wanted and it’s independent from the creation date).
With this type of metadata you can create a DQL query similar to this:
```dataview
TASK
WHERE !completed
WHERE note-date AND note-date < date(today)
SORT note-date DESC
```
This is an example. But there are other ways.
I insist: you need to know something about the tool to know what and how structure your metadata. (mainly the “logic”, not the code knowledge)