wish: preprocessing script and/or CSV map files

Bug #1738601 reported by Matthew Palermo
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
HomeBank
Confirmed
Wishlist
Unassigned

Bug Description

It would be useful to have HomeBank automatically run transaction data through a customizable transformation upon import. For example, it would be helpful to be able to run HB_Convert (or something similar) automatically on importing a csv. This would also be helpful for other formats such as QIF. In the QIF files exported from Bendigo Bank Australia, the memo and payee fields are identical and includes information such as the amount in the original currency. It also includes useless categories that I'd rather not import.

Perhaps this feature could be as simple as running an external program of the user's choosing. The external program would receive a single row of the transaction via STDIN and return more useful information for the transaction via STDOUT.

I know it's possible to do all this manually, but doing it manually takes time that could be spent doing more important stuff in HomeBank. Also, it would make the transformation programs much simpler and more standardized. This would allow for a repository of such transformations. Such repository would be a open source alternative to the data parsing component of Yodlee.

Maxime DOYEN (mdoyen)
tags: removed: wish
Revision history for this message
Maxime DOYEN (mdoyen) wrote :

As we are here focused on CSV, I more think about some external mapping file to could be share and enable to map any csv format to HB fields.

tags: added: file-import-export
Changed in homebank:
importance: Undecided → Wishlist
Revision history for this message
Maxime DOYEN (mdoyen) wrote :
Maxime DOYEN (mdoyen)
summary: - wish: Transaction data transformation on import
+ wish: csv mapping for import
Maxime DOYEN (mdoyen)
summary: - wish: csv mapping for import
+ wish: csv mapping external file for import
Maxime DOYEN (mdoyen)
Changed in homebank:
status: New → Confirmed
Maxime DOYEN (mdoyen)
summary: - wish: csv mapping external file for import
+ wish: preprocessing script and/or CSV map files
Revision history for this message
Maxime DOYEN (mdoyen) wrote :

from 1863814
All banks use their own layout in CSV export - some have multiline headers and footers, some only have a sing-line header. Number of columns and their order is different as well as delimeters, date and number formats.

It would be nice if HomeBank had support for user-configurable CSV import profiles (presets):
1. Number of header rows (before first data row)
2. Number of footer rows (after last data row)
3. Date format (already present in preferences + can be redefined during file import)
4. Numbers format (decimal symbol, thousands separator)
5. Mapping of column (by name/number) to HomeBank transaction fields

Such profiles could be also linked to accounts (most probably same format form the same source will be used for one account at all times, but one profile might be applicable to several accounts).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.