Automatic Reference in Daily Note to Moved Content
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- JavaScript
- Sterne
- 204
- Forks
- 82
- Ø Merge
- 22 Std. 27 Min.
- Gemergte PRs (30 T.)
- 3
Beschreibung
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:
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne damit, die Implementierung des Filer-Plugins und den Einstiegspunkt für den Befehl „move note links“ zu finden. Verfolge, wie verschobener Inhalt und seine Zielüberschrift dargestellt werden, und definiere dann die erwartete Daily Note-Referenz und das konfigurierbare Ignorier-Tag; als erledigt gilt dies, wenn der Befehl diese Referenz erzeugt, ohne sie erneut zu verarbeiten.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- javascript
- Bereich
- tooling
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 45/100