Convert IM3.6 Workflow to IM5

[ggblue]

Hi,
under IM3.6 I work with a 4-step workflow, which is based on the old powerfull SAMBA/GAMB/SINUS scripts. In short, these scripts rename and import the image files in a timeline-based folder hierarchy, import ipct-data from properties and exif, call specific photoshop macros and stores the processed image (copy) in a result-folder under the timeline. Alle that stuff is administered with the help of some workflow categories.
My simple(?) questions are: Is it possible to build a similar easy to use WF under IM 5?
Is it possible to migrate the IM 3.6 Scripts to IM5.

Thanks a lot for any help or tipps
ggblue

[Mario]

import the image files in a timeline-based folder hierarchy,

If you want to create folders based on metadata (date and time), check out the corresponding options in the Renamer. The Renamer can rename and move/copy files.

Also check out the built-in time line in IMatch 5.

import ipct-data from properties and exif,

You import property data and EXIF into legacy IPTC metadata?
In IMatch 5, properties have been replaces with the much more advanced Attributes.
You can import Attribute data, EXIF data and other metadata into legacy IPTC data using a Metadata Template. But you should always work with XMP metadata in IMatch 5, not with legacy IPTC data.

Regarding running Photoshop macros, IMatch 5 cannot help you directly. You will need a custom script which controls Photoshop. Or check out the Batch Processor, which may be able to do what your custom PS scripts do.

Note about working with legacy IPTC metadata

IPTC metadata has been declared legacy many years ago. It should not be created anymore for new files, in accordance with the recommendations of the Metadata Working Group.

IMatch implements the MWG rules. It has a XMP-centered metadata workflow. IMatch keeps legacy IPTC and EXIF in synch when you make changes to XMP data. See the corresponding sections in the help for details.

In short, this means that if you update metadata in a script of via a Metadata Template, always update the XMP metadata tag (best: Use the Standard Tags provided by IMatch) and do not update legacy IPTC data. This way IMatch can ensure that changes you make are properly synchronized between IPTC/EXIF/GPS/XMP in both directions.

[ggblue]

Thanks for your remarks and hints, Mario.

I suppose the best way is to analyse the functionality of the old IM 3.6 macros in deep and then write a new code using the object-model of version 5.

ggblue

[Ferdinand]

Is it possible to migrate the IM 3.6 Scripts to IM5.

This question didn't get a direct answer.  Yes it is possible.  All scripts will at least need some minor editing, but some will need more work. 

However as Mario pointed out, a lot of workflow scripts are no longer needed as IMatch has much of this functionality built in.

[unterwasserfoto_at]

Ok Mario, we should use allways the Database wenn we write metaden.
But how is the way to write the information from the DB into the File, in a script?

[Mario]

See the topic Metadata Classes in the IMatch help system, plus the corresponding sample scripts.
You cannot directly write metadata from a script to a file. You use the Metadata classes and let IMatch take care for the rest.

[unterwasserfoto_at]

I have seen the script. But the update Write it only into IMatch.
I would like a methode or a Order to IMatch to to it finish

Is there a Way ?

[Mario]

The Metadata classes use the write-back settings configured for IMatch. If use immediate write-back, IMatch will write-back the metadata at the next opportunity.

Please remember: IMatch is processing many things in the background, even while your script runs. IMatch may currently be reading metadata, write-back metadata, update collections or categories. When your script would be able to write-back data to a file which is currently read by another IMatch task, results would be potentially disastrous. Better to leave it to IMatch to write back the metadata.