On Wed, Oct 10, 2018 at 10:16 AM Justus Pendleton <[email protected]> wrote:
> On Wednesday, October 10, 2018 at 6:31:24 AM UTC+7, Martin Blais wrote: >> >> BTW you should consider using a ^link for that; they were designed for >> that purpose. >> When there's a unique transaction id available from the files I import, I >> always add them as a link. >> > > Could you explain that a bit more? The documentation for links says "You > may think of the link as a special kind of tag that can be used to group > together a set of financially related transactions over time". Except in > this case there is no "group" of transactions; there would only be exactly > one transaction with the link. Since there's no group, I guess it didn't > naturally occur to me to use them for this. Are there any benefits to using > a link instead of metadata? (Ergonomics, easier searching, better UI > handling?) > No benefit. Same as tags, but I've been using them differently. I use links to link together multiple related transactions (of which, initially, if imported as suggested here, there would be a unique one for each imported transaction, but you can then link others manually). Tags tend to be used for larger groups of transactions, e.g. a trip, a category. In the end those could be merged. I've had it in the back of my mind to merge them if I ever write 3.0. -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhMFQV%3DZGzu4m4rA9xpY656X%2B7%2ByW4LxG76ABqCXSudhkg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
