Increased interaction during import, more accurate duplicate detection, ability to use regex captures in mapping file

[mondjef]

• Changed duplication detection to use MD5sum field and included source account so that duplication detection is more accurate.
• Adds MD5Sum of new transactions from import file so that duplication detection of duplicate transactions in import file itself can be detected.
• ability to be prompted for confirmation before entries are added to mapping file
• ability to use regex captures in mapping file... useful for transaction descriptions that share a lot in common for example: POS MERCHANT SOBEYS, POS MERCHANT LOBLAWS and you just want to use SOBEYS or LOBLAWS as the payee. Another example is ETF FROM name and you want the payee to be name and you want the account to be Assets:Receivables:name
• ability to be prompted before automatically skipping duplicates. This is handy when importing transactions that contain a lot of generic descriptions mixed with transactions with good descriptions. For example: ABM WITHDRAWL and the amount is commonly some denomination of 20
• ability to review the generated ledger entry and be prompted to either commit (accept the entry), modify (given the chance to re-indicate the payee and destination account), or skip (ignore and do not import transaction)

[petdr]

Thanks for this.

[mondjef]

glad to help out. Not a coder by trade...rather self taught and new to python for the most part. That being said, I am not totally happy with my additional call to journal_entry just to capture the return value to display for the review part but couldn't figure out how to avoid it. Maybe you know...

…

On Sun, Jan 29, 2017 at 5:13 PM, Peter Ross ***@***.***> wrote: Thanks for this. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#100 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AVDpaw2PvFbD7mMniyiYxudlXJbIuKi7ks5rXQ8cgaJpZM4LwJLX> .