Automatic Reference in Daily Note to Moved Content
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 204
- Forks
- 82
- Avg merge
- 22h 27m
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
I use Daily Notes to keep track of various tasks and notes throughout my day. Sometimes, these notes are associated with ongoing, long-term projects. I love that the Filer plugin allows me to easily move content to a corresponding project notes via the ‘move note links’ command. However, after moving content, I often need to retain a reference in the Daily Notes indicating that specific content has been moved to a project note (as a summary or log of my efforts throughout the day related to different projects).
Describe the solution you'd like
I would like to see an enhancement to the Filer Plugin that automates the process of adding references in the Daily Notes to the newly transferred content. This can be achieved by appending a link to the project note, where the content was moved, directly within the Daily Note. Additionally, I’d like the option to append a tag (e.g., #ignore that is already built into the plugin) at the end of this reference. This tag would act as an identifier, ensuring that if I run the 'move note links' command again on the same day, it would not re-process that new reference link.
I'm hoping it's as simple as:
- Use the Filer Plugin to move a piece of content from a Daily Note to a project note.
- Automatically insert a reference link in the Daily Note that points to the specific heading containing the moved content .
- Have an option to append a customizable tag (e.g., #ignore) next to the reference link.
Describe alternatives you've considered
I have been manually creating these reference links. It works but it is not efficient, particularly when dealing with numerous notes and projects.
Additional context
Below is what I think the final output may look like:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Filer plugin implementation and the entry point for the “move note links” command. Trace how moved content and its destination heading are represented, then define the expected Daily Note reference and configurable ignore tag; done should be demonstrated by the command producing that reference without reprocessing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100