Small project for importing from iOS App QuickFamilyTree export format

Hello everyone, I’m new to Gramps and more of a casual user using it to host a self-hosted Gramps Web Family Tree for family members.

For this, I wrote a conversion script in Python to enable quick import from the previously used iOS App QuickFamilyTree export format into Gramps Web via the Gramps CSV format. Are such tools or some kind of integrations / import support features of interest here?

If so, I’m leaving the public code link here: GitHub - jonas4climate/togramps: Conversion tool for QuickFamilyTree to Gramps Web for genealogical trees

If there is a place for these to be integratable and this is of interest, I might have some time to pursue this.

4 Likes

Welcome Jonas Schäfer!

.ftz (zip archive of a node.ftt) file, the .ftt (family tree text in TSV) file import (and export) and the Quick Family Tree iOS (and Android) app look interesting. (caveat: the app is adware) Thanks for sharing your work!

promo video on YouTube
blog entry about creating the app in Japanese
creator: Yoko at Digital Gene, Kyoto prefecture, Japan digitalgene.contact@gmail.com

@DavidMStraub can Gramps Web use IMPORT plugins built for Gramps for desktops?

@Nick-Hall do you think some sort of pipelining API feature would be possible? The Quick Family Tree FAQ says that they successfully tested Google Drive, email, and Dropbox file exchange. (Although Facebook, WhatsApp, and LINE file exchange tests have failed.) Maybe it could be integrated with a variant of David’s Gramps Web Sync… allowing tablets and phones to be used as live remote data entry and browsers for Gramps?

You could fork a copy of the .csv import plugin by @dsblank and adapt it to be a ‘.ftt’ import plugin. And the ‘.gpkg’ import plugin is an example that can handle a ZIPped format (.gpkg) that containing a compressed data.gramps XML format.

If you want to experiment developing an addon plugin, when you fork the built-in plugin, it will need a gramps registration file to accompany it. The registrations for the built-in importer plugins are collated into a single file. The CSV portion is here: import.gpr.py

2 Likes

Yes!

In practice, to make third-party plugins widely available in Gramps Web deployments, we need to install them in the default Docker container, but that’s easy to do once they addon is released in the addons repository.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.