So, I might try thatIDimager software... $69... and I'm guessing I'd have to buy a full copy for each computer, too.
I'm wondering if this software (or some other software) can help me re-capture all the tagging I did with Picasa.
What exactly do you mean by tagging? Comments? "Star" ratings? Facial recognition name data? Image edits, like cropping and red eye removal?
I have my own definitions of tagging, and some of the references between me and Doug might have been a bit oblique. For instance, Doug mentioned that IDImager stored its data as SQL. I looked back at the IDIMager blurb pages and saw that they use SQLite. A few quick Google searchs showed me that SQLite is open source (yea!), and that it has bindings for all of the languages that I use.
SQLite project page
http://www.sqlite.org/
List of programming language bindings to SQLite
http://www.sqlite.org/cvstrac/wiki?p=SqliteWrappers
I asked Doug about IDImage's XMP support. He replied that IDImage did store metadata as XMP, in addition to the data that was stored in SQL tables. I knew from past experience that XMP is a flavor of XML, and that XML is readable programmatically by several means (because XML is standard ASCII text.)
With this information, I knew that I could write "glue" programs to extract any data that is managed by IDImager, either for use in my own programs. Or to reformat and import into some other program. IDImager might very well have ways to export data non-programmatically, but I'm more interested in being able to do it at all--i.e., that the data formats are well documented.
On the other hand, Picasa doesn't work like this. Most of the metadata that I mentioned in my first paragraph is stored in an undocumented binary file (or files), near as I can tell.
One area that I am still concerned is that IDImager (like Picasa) supports a certain amount of image editing, but it does it "non-destructively" On the face of it, this seems like a good idea. But this causes problems with data interoperability: any image edits that you have done don't really exist until you "export" the images (at which time the edits are applied.) This is a minor matter when you are working on a small collection of images, but can become a major problem if you want to process your image collection with a different program. Perhaps, to populate a web site. Or to load into a different image managment program.
If IDImager stored the metadata that describes the image edits as, say, ImageMagick
http://www.imagemagick.org/script/index.php
commands, then the editing metadata would be portable--any language can process images with ImageMagick (because it operates from the command line). But if IDImager has its own propitiatory method of editing images, then it has the same problem that Picasa has. (This problem can be partially sidestepped by using a different program to do image edits, so that all edited images live on disk. But then it is less palatable for non-technical friends and family.)
Also, when I looked closer at the IDImager page, I see that there are two versions. A $69 version, and a $139 "Pro" version. A lot of the features that are important to me only appear in the Pro version.
http://www.idimager.com/products/idimager/comparison-sheet
But it might be worth it. I think that I should stop waiting for Google to document Picasa's data formats on
http://www.dataliberation.org/ and find some other option for metadata interoperability. IDImager might be a usable solution. For me.
Wayne