Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: new file name variable {{first_highlighted_date}} #77

Open
MiroStW opened this issue Nov 26, 2024 · 0 comments
Open

Feature request: new file name variable {{first_highlighted_date}} #77

MiroStW opened this issue Nov 26, 2024 · 0 comments

Comments

@MiroStW
Copy link

MiroStW commented Nov 26, 2024

Right now we can use {{last_highlighted_date}} in our file name config. I use this, because I want to name my notes in obsidian by the date I read the document instead of naming them by their {{published_date}}.

This however, will naturally cause new highlights that come in on another day to end up in a separate file. E.g.:

readwise-articles-2024-11-25-my-article-12345678.md
readwise-articles-2024-11-26-my-article-12345678.md

This is not ideal, because I will need to switch between different notes. Also the 2nd (3rd, 4th,..) note won't have a frontmatter header.

I don't care so much about the exact date I finished reading the document, I just want to organize my notes by the approximate time I read them. That is why I want suggest the introduction of a new variable called {{first_highlighted_date}}. This will always be the date of the first highlight that exists right now for the given document.

Depending on what is easier to implement this date could either be fixed permanently or would update in case you deleted the first note you created for the document.

Crucially the effect would be that however many highlights you add on following days, they would all be synced to the same note in obsidian.

@MiroStW MiroStW changed the title Feature request: Feature request: new file name variable {{first_highlighted_date}} Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant