thanks for the diff. I integrated it with a few changes:
Can I have a XMP file created by Imatch for a test? I think, for you
it's no problem to create the JARs with the applied fixes (ant or
NetBeans)? Otherwise or if other users having the same problem, I will
create a new release.
BTW: Did you try VueScan?
So, in the last couple of days I've tried to make sense of IMatch various Visual Basic scripts, which are included in the distribution. Unfortunately Imatch doesn't allow the direct manipulation of XMP information through the embedded Visual Basic interpreter, but only indirectly through the setting of IPTC information, which then is written to the appropriate XMP tags.
So, in the end I was able to transfer the hierachical keywords from Imatch into IPTC dc:subject XML tags, which JPhototagger would correctly read. The keyword would look something like "Family.Children.<Childs Name>" or what ever. Imatch uses the same dot notation as for instance Java's import statement for class hierachis.
I've come to the conclusion, that I'm going to import all photos with this dot notation into JPhotoTagger. After that I will select all photos with the same keywords, retag them manually with the appropriate single word tags. Then I'm going to delete the dot notation keywords. Overall I had scanned roughly 125 rolls of films. Assuming 36 exposures, that would make roughly 5000 pictures.
I think, that would be the cleanest way to transfer the dot notation into a single word tag notation. Since Imatch also duplicates the transfered hierachical keyword information into the photoshop namespace, I could even keep this info around and use it sometime later.
Am I makeing sense?
I've notice one problem with the uppercase file name extension handling however during my experiments. JPhotoTagger correctly reads the XMP file with an uppercase .XMP, but when I've edited something within JPhotoTagger, the new ly written XMP sidecar file is written with lowercase ".xmp" extension. And the new file doesn't contain all informaton from the original .XMP file. So I've then basically two XMP files for a photo, one with .xmp and one with .XMP.
On 29.07.2012 22:51, chairraver wrote:
> package org.jphototagger.domain.metadata.xmp;
If a feature is requested often, it will be integrated into JPhotoTagger
(if I have time or onother - not yet existing - developer will do it).
For other tasks it's better to use the project "User Services" (added
today, before it must be organized manually) which will not have a
default implementation and will never be part of a distribution.
Otherwise you have always rebuild JPhotoTagger by yourself if you want
to be up to date. See http://www.jphototagger.org/dev/user_services.html
- especially the paragraph "User Services' project skeleton".