Hi Bruno,
I must acknowledge and admit complete ignorance of the bullet journal method, until you mentioned it in your thread.
Much like @trebso, it would have sent me bonkers reviewing, rewriting and ‘migrating’ things (whatever those ‘things’ may be).
At first glance, Agenda seemed ideally suited to me going electronic with my journalling habits. All that was needed was the “Agenda Link” for a note to be immutable once it was created. That would allow a note to be tracked, no matter where it went , with its “Agenda Link” being a unique Object-ID.
I’ve attached the start of a day’s journal entry below. The dot-points are always on the left hand side of a page, with details starting on the right, continuing for however many pages are required. This way, dot-points can grow as a day progresses (I’d seriously worry if dot-points needed more than one page).
If/when a dot-point is complete for a particular day, I circle the asterisk in red. The remainder (even partially completed - they get marked slightly differently) roll over to next day’s dot-points, unless I’ve decided not to pursue an activity (or it’s too late, whatever).
This mechanism has served me well for decades, except for finding when something started and tracking its history. A unique “Agenda Link” would have permitted me to do all of that electronically. I would have had a note’s complete history tracked from inception to completion. No reviews, etc. Migration would be the equivalent of moving a note into a different category/folder in Agenda. I’ve kind of described what I was trying to do in my initial post/reply to this thread.
I understand implementation minutiae could explain why a note’s link changes when it moves. I’ve met this sort of thing before - many times. For example, I’ve had deep discussions over many years with developers of a very mature network monitoring and management system. I was looking to also use it as an on-line inventory management system of anything within our purview that was visible on a large, multi campus network. The biggest problem? As soon as a device had to move from one location to another, it lost its uniqueness. In essence, a device couldn’t ‘move’, it could only be ‘copied’.
So yes, implementation details may explain why a note’s ID changes when it moves from hither to tither. It doesn’t reflect life events or activities, not the way I see them anyway.
I repeat my plea to the Agenda developers … Please consider a unique and immutable identity for each note.
Please.
Thank you,
Paul