


Overall, while there may be some challenges involved in exchanging data between two different databases, it is certainly feasible to do so using Digikam’s built-in support for SQLite databases and its API. With the API, you could write a script or application that reads data from the family tree database, uses that data to update the metadata on the corresponding image files in Digikam’s database, and then retrieves any updated metadata for further processing or comparison. Digikam provides a powerful API that allows you to access and manipulate metadata programmatically.

You could also use Digikam’s API to automate the process of updating metadata. For example, you could write a script that reads data from the family tree database, uses that data to update the metadata on the corresponding image files in Digikam’s database, and then writes any updated metadata back to the family tree database. To exchange data between the two databases, you could use SQL commands to query and update data in both databases. Digikam has built-in support for SQLite databases and can read and write metadata to image files. Yes, it is feasible to exchange data between Digikam’s database and another SQLite database, such as a family tree database. With Digikam, would it be feasible to exchange data between its database and a sqlite family tree database that Digikam would write to the image files and retrieve for comparison. There are many other applications and tools available, depending on your specific needs and preferences. These are just a few examples of applications that can connect to a SQLite database and read-write metadata on image files. It also has built-in support for SQLite databases and can read and write metadata.
