Perl csv2qif for CSV exported by GnuCash to import back into GnuCash

[Art]

Hi Lewis,
It appears I failed to explain problem properly since you seem to think I needed to understand the concept of a transaction.
The problem: I entered 105 transactions in the  database of server 'A' which I intended to enter in server 'B'.
The possible solution spaces: 1) Have GC export the data from server 'A' and import it to server 'B'. - No, GC does not have a functional homomorphic mapping capability that I am aware of. (It exports CSV which it refuses to import, but QIF has worked, so I thought I'd map csv2qif, but existing scripts I reviewed lacked the flexibility I needed to handle 2 banks, 2 credit cards, and 20 expense accounts with descriptions so I don't lose the information I already entered)
2) Ask the community about possible solutions to this (I am way too lazy to deal with the tedium of re-entering data, unless it'll take too long to develop a programmatic solution).3) Read the journal back.
Solution: Read the journal back - All 105 transactions I initially entered into server 'A' are now in server 'B'. It was a trivial 3 minute operation - double-clicking on 7 journal files (it could've been done in 10 seconds, but I was careful this time).I looked at the piecash link. I'll have to review it when I have time. This was a fun and learning exercise for me as it refreshed some of my Perl and Python skills.

      From: Wm <tcnw81 at tarrcity.demon.co.uk>
 To: lewis at keywild.com; pinaart at yahoo.com 
Cc: gnucash-user at gnucash.org
 Sent: Thursday, April 28, 2016 12:24 PM
 Subject: Re: Perl csv2qif for CSV exported by GnuCash to import back into GnuCash
   
In article <5725A6B1.9000001 at keywild.com>
Lewis Balentine <lewis at keywild.com> wrote:
>
> If you have gotten to importing transaction then you are much further
> along than I am ... I am still stuck on customer records.

You and Art are both being silly.

Accounting transactions are very simple and involve no more than
Date
Description
Amount

and you can sometimes get rid of the description if it is causing 
problems.

A Date and a Number are all you actually need to make sense of a 
set of transactions.

If you are struggling with organising your data ask nicely.  Don't 
pretend it is a GnuCash problem until you've played with the 
software *before* checking if it is right for you and your data.

If you want to take this seriously, go back and forth to the ledger-
cli family of transactions, it can be done if you are not lazy, and 
the tools are availble in popular scripting languages.

Look at Sebastien's piecash for a good, modern view of GnuCash data 
and how to deal with it.  He provides a lot of stuff for free.

http://piecash.readthedocs.io/en/latest/

Sebastien: if you prefer another link let us know.

-- 
Wm