Well, before getting the GF1 my workflow was simple:
- ingest, rename, set an IPTC template and write to provisory folders nemed by date with XnViewMediaDetector.
- if geodata available I used Geosetter to write them into the NEF
- copy/rename the folders to my "Image" tree and develop with B4/B5, the jpg/tiff go to a Bib subfolder
- open the NEF folder in IMatch, complete IPTC, catalogue and synchronize between NEF and Bib subfolder using your Image synchronization script (thanks alot)
So every metadata in the NEF or jpg, the rest in IMatch, easy to retrieve in whatever form needed.
Now with the RW2 from the Pana GF1 this didn't work, IMatch has the IPTC editor greyed out, and XnViewMediaDetector couldn't show the RW2 vignettes (I asked Pierre Gougelet about this but he had a lot of other things to do, so...).
So I bought Photomechanic. I use it for ingestion, rename, write to provisory folders, write all IPTC metadata, geotag images.
Photomechanic has two nice features: 1) a very easy to use, intuitive, customizable and complete IPTC/XMP editor, 2) there is just one editor which writes the full metadata either as IPTC into the NEF or to an XMP sidecar to the RW2. I hope the future all in one editor of IMatch5 is as good so I can drop PM and do everything in IMatch/B5/ASP (and rarely PWP).
The rest of the workflow stays the same, at present PM, ASP, IMatch. Works well for me. The XMP is no problem neither for ASP nor for IMatch despite the idiotic xxx.RW2.xmp naming of the former bib files. I am quite confident with PM, Exiftool, Imatch writing to the NEF, never had a glitch over the years. RW2 is less documented, there is no Panasonic SDK that I know of, so I play it safe, and B5/ASP reads the xmp sidecars written by PM OK.