On Aug 26, 1:32 pm, Russell Adams <[email protected]> wrote: > All my CSV files from the bank have a header line, which gives > "english" names to each column. As you can see (from the sample I sent off-list) CIBC outputs no header. > > Two comment items are created by default, one line containing the > original CSV, (I really like that > the second containing an MD5SUM of the original CSV. the line or the file ? > There is duplicate detection on output (when enabled) which works > great for when you've downloaded files with overlapping date ranges. that's brilliant ! > > > When you say "setting up a rule".. is there an existing mechanism for > > that ? Maybe I'll try to have a local perl-monger make me a post-post > > processor to do this, that and the other. (If I succeed, I will > > > share) > > Setting up a rule in AccountMatching.yaml, use "ToBeEdited" instead of > a real account name (ie: Expenses). I can't say that I understand that.. > > Pairing becomes arbitrarily complex, I don't think its likely that I > would code it. However, you can always update the source and send me a > patch. ;] uhh.. sure.. perl, you say ? it won't be me, but I might have a local perl-monger have a look. >
> > Don't you think a set that was bundled for a specific institution would > > be way more likely to "just work" ? > > No. The header/field translation is only one piece of what goes into > FileMatches.yaml. Essentially. all the flags you could set on the CLI > get auto-set by matching the input filename to a regexp. This updates > header/field xlation, output file, image/file matching, duplicate > detection, etc. Only the header/field stays common between users. so a header field is essential to the process ? Am I going to have to graft one on ? OK, I understand how the interwoven solution is user-specific, not institution specific. Maybe some corner of documentation can collect tips for specific banks. > > > I could do it in post-post, but if CSV2ledger can be tweaked to do it, > > that would be cleaner. > > CSV2Ledger internally doesn't apply any special meaning to ';', so the > '; :online:' can simply be a part of your payee name. That makes sense too, as I can look for the full string, including card and payment-type clues, and have multiple payee outputs, tags or no. > > > > > > --- > > > - 'm/TORONTO HYDRO ELECTRIC/' > > > - 's/INTERNET BILL PMT ([0-9]+) TORONTO HYDRO ELECTRIC.*$/Toronto Hydro > > > $1 ; :online:/' > > what was that ?? looks like the right direction.. > > This is a sample Preprocessor.yaml rule. The file is yaml, and > consists of arrays of regexps. > > >> I don't know If you had thought about extracting some things to > > >> comments, but if it can be done, it would be a boon. > > Again, use regexps in the preprocess stage to create your payee comments. Alright, that's making sense ! > > > > How do I set the flag to cleared ? > > CSV2Ledger --help: > ... > -x Mark transactions cleared > > > > > > Hope this helps! > > Quite fantastic, and I hope I haven't been too dense. > > djp > > Enjoy! you're a prince ! ;-) djp
