Hi jmurphy, I have joined the FHUG in order to try and address issues and concerns about Clooz. We are also available, almost 24/7, at our support function ( email@example.com
) for issues that might not be appropriate for general discussion.
We are specifically interested in the problem you mention about using a FH gedcom input to Clooz not providing desired source results. We would like to take a look at this issue, because the import "should" work properly. Would you mind making a test gedcom export from FH and forwarding it to us as an email attachment to our support address shown above? In your email, please state the exact results that you are seeing, and the results that you had expected.
As Colin mentioned, our new release next year will be much improved and have a gedcom export, as well. However, we feel that a direct interface, such as the terrific interface that Rich developed with Legacy would be preferable for our FH and Clooz users. As I'm sure you understand, in order to effect such a powerful interface, we always need the cooperation and support of the other program's development manager(s). Hopefully we can come to an agreement with FH.
As an interim measure (as Colin mentioned) the free version of Legacy can be used temporarily as the "middle man". I can assure you from my personal use of Clooz with Legacy that the export of data from Clooz is exceptional. As I mentioned in the HoA video, after implementation I opened blank files in each program, processed over 40 documents in Clooz, exporting them as I finished. The end result was a Legacy Family Tree file for which I had never typed a single character in Legacy itself. I really don't know anything about the supposed problems with the Legacy gedcom output, but as a temporary measure, it might prove worthwhile if you experimented a bit to determine if the results are acceptable to you.
No matter what the issue, since you already own Clooz, I strongly recommend that you continue processing your documents in Clooz while waiting for Clooz 4 later next year. That will insure that your database continues to build (especially for using the Composite View). As a dedicated Clooz user myself, long invested in FTM (they won't even discuss an interface) since version 1, IMHO the additional steps needed until Clooz 4 will prove worthwhile once a proper interface medium is available.
We really appreciate such discussions as this one. We are dedicated to continuing improvements, and have a stellar track record of listening to our users. Obviously we can't just snap our fingers and make everything happen, but as practicing genealogists ourselves, we are truly sensitive to user discussions, and try very hard to communicate, even when we have to report "bad news".
We are happy to continue to work with you and others to improve our genealogical environment. Thanks for sharing your thoughts.