Mindful that the fundamental idea - i.e. to discover areas in your knowledge base that haven’t been reviewed in a while, and to easily navigate it across time - has already been brought up a few times. That said, it struck me that there was no “single idea” that captured the point fully, hence I thought it’d be interesting to float a more holistic approach and see what the feedback would be to that in the community.
I personally think it’d be amazing to have a uniform view which makes time the variable by which you screen your notes. To illustrate, I put together a high-level mock-up below (a picture says more than a thousand words after all):
In my view, this ultimately boils down to three key UX elements:
- A “inbox / working memory” action area of sorts, which shows the items which you’ve been editing lately (i.e. “Edited in the past week”), and which allows you to quickly access these top-of-mind files
- An action area which allows you to in turn browse your notes over time in a consistent way
- A visual summary timeline / calendar view which allows for very quick and intuitive access to specific points of interest (the mock-up above uses a timeline concept, however, a github-esque “contribution” calendar would work just as well, if not better), based on some of key metric
- E.g. by amount of content created/edited on a specific day (for evaluating productivity), or by a score which summarizes the amount of notes with a lot of links and content, that have not been viewed in a while (for finding old important notes and reviewing them)
I think a card view is very powerful in this kind of scenario, as it allows for the most organic way to display the key information with clear visual feedback. E.g. the background of the note can fade the longer a note has not been viewed (a bit like Trello’s implementation). It also translates well to any other form of filtering that might be applied down the line.
Would be great to hear people’s thoughts - I personally think this a key missing link in Obsidian’s current core toolset (as there currently simply isn’t any clear way to efficiently review notes and understand ones note creation patterns). Mindful that the mock-up is probably a bit too ambitious, but even an MVP which ticks any of the elements above, would be really useful in making Obsidian a full knowledge management tool.