Reporting on interaction with Apple. As I mentioned, I reported the problem to Apple. I was contacted on 11/3 by a gentleman at Apple asking for more details and a small sample. I described the problem and sent in two photos: in one the faces were offset. In the other, adding a name did not stick (when you went back to the photo the name was not there). I only submitted two photos due to file size limits.
My last comment was: "I really just need to know if this is repairable or I just need to give it up."
Apple's reply on Nov 4: "Thank you for the details. I will pass this to engineering. If we feel we can recover it, I'll let you know."
That reply was significantly less of a commitment than I had hoped for. So iPhoto's database got contaminated, I ebuilt it in Aperture, and now Aperture is contaminated. I decided to rethink my logic that brought me to these two products in the first place. I purchased my first personal computer in 1978 and have never been without one since. When I moved to Apple, it was like a weight had been lifted from my shoulders: I don't have to be a system engineer to make all the stuff work together. That was true until recently. Now, I see the same kind of problems that occurred in the Windows world popping up in Apple country: specifically, it's up to me to figure out workarounds to software bugs. I really don't want to have to do that.
I did some research on alternatives to iPhoto and Aperture and believe I have found the critical flaw: Apple stores all the information about my photos in a database that it manages--and that database is proprietary and cannot be repaired with the tools provided to repair it. I was also shocked to find in one article that the author could find no professional photographers that use either product!
Looking for value, I looked at Picasa. While I have a prejudice against Google for their recent actions relative to Apple (namely Android), they use a different logic: store all information in the photo itself, then extract from the photos to make up the display. This approach has one big upside: NO DATABASE! While Picasa does store faces in a .plist, you can also have them added to the photo. The cure for a contaminated faces database in Picasa is to delete the database and have Picasa recreate it by reading the photo data.
My research indicates there is no standard for storing name data in a photo. That means Picasa has it's way (which it understands), but there is no guarantee that anyone else can make sense of the data. Not too excited about that, but found an app on the app store called Photo Meta Edit. It shows all the data stored with the photo, and allows you to directly edit it. I kinda like that. Here's how a face is stored. It is in the XMP section in 3 sub-sections. Here are the entries:
mwg-rs:Area
stArea:h 0.0556586
stArea:unit Normalized
stArea:w 0.0300926
stArea:x 0.721065
stArea:y 0.580705
mwg-rs:Name Bernice McCoy
mwg-rs:Type Face
I think the program was $3-4.
So, I'm thinking about migrating from Aperture to Picasa. I'd do that by exporting each event into a new physical folder, exporting the current version (which is edited). Maybe keep Aperture as a storage spot for the originals. Picasa interface is kinda intuitive. I like it shows all the photos with location info, and the date when the photo is selected.
I'd like your experiences and recommendations.