Fixing confused bayesian matching data?

Wm tcnw81 at tarrcity.demon.co.uk
Mon Jul 18 09:58:08 EDT 2016


On Sun, 17 Jul 2016 21:24:56 -0400, in gmane.comp.gnome.apps.gnucash.user,
Philip Matthews <philip_matthews at magma.ca> wrote:

> Just wondering if anyone has any advice on what to do with some very confused bayesian matching data?
> 
> Right now, when I import new transactions (either CSV or QFX), they mostly don't find a match anymore. Only around 20 - 30% match.   This is probably because I like to rejig my accounts from time to time as I continue to figure out what works best for me.  Looking through the ".gnucash" file, I see lots of slot entries with account names that don't exist any more.
> 
> For a while, I was just putting up with it and assigning transactions to accounts by hand, but now I am starting to get tired of this.
> 
> A couple of options have occurred to me:
> 
> 1. Just delete everything between <act:slots> and </act:slots> for each account.  This is simple, if rather drastic. But do I do this again in a month when I make another small change to my account structure?
> 
> 2. Write a Python program that goes through the .gnucash file and deletes slot entries that point at accounts that don't exist any more. 
> 
> Comments?  Other thoughts?
> 
> Running GnuCash 2.6.11 on a Mac.

Notwithstanding JohnR's reply are these one off
getting-your-accounts-started transactions or something you're going to be
doing on a regular basis?  I'd have thought different answers required
depending.

-- 
Wm



More information about the gnucash-user mailing list