One thing I found helpful in the zettelkasten node references. When I inserted the gnx of a node into a referring node, I also inserted its headline. The search script only used the gnx, but the headline was useful for the human looking at it.
An example: :link: TomP.20200225100827.1 About Leo On Thursday, February 25, 2021 at 9:51:30 AM UTC-5 Edward K. Ream wrote: > On Thu, Feb 25, 2021 at 7:14 AM tbp1...@gmail.com <tbp1...@gmail.com> > wrote: > > This sounds similar in concept to the scheme I came up with for the >> zettelkasten work. Any zettel node can contain references to others by >> referring to their gnx. To make it work in a practical way required a >> couple of scripts. One of these scripts inserted the gnx of the node to be >> referenced, and also inserted a backlink into that node. >> > > Thanks for this reminder. I'll take another look at your work. Snippets > would require similar scripts. > >> The big challenge in this kind of system is to keep everything in sync. >> Trying to locate gnxs is fine; trying to match any text that a person may >> edit is fragile and prone to getting out of sync. >> > > Not a big problem, imo. Snippet descriptions need only be unique to a > particular node. In the usual case, there will be only one snippet in the > node, so the description isn't needed. A warning could be given if the > description in the reference isn't the same as the description in the > defintion. In any case, the gnx can't change, so it will be easy to have > Leo link to the offending node. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/957a7d67-ade1-4786-a33e-7cb75d6bf0e7n%40googlegroups.com.
