[claudio ercoli]

HI guys, I would like to propose some features that would be very useful, at least to me.

- Possibility to use the tokens also to set IPTC parameters. For example, setting the Job code, that value can be used also to write the IPTC keywords to the same value.

- possibility to set different parameters for each Job. For example, when I try to download pictures for different days from the same card/directory, the sw creates automatically one Job for each day, and this is great. The drawback here is that, for example, if I want to set some iptc parameter during the download, different from day to day, I have to modify that parameter for each day I'm going to download, without possibility to dowload all pictures together.

Hope it helps.

Claudio

[DavidB]

Possibility to use the tokens also to set IPTC parameters. For example, setting the Job code, that value can be used also to write the IPTC keywords to the same value.
If I understand this request correctly, DL Pro can already do this. For instance, I tend to use the Job Code as the common element of the caption in each set of images. So I have the Job Code dialogue come up when I start DL Pro. In my standard IPTC data set, the Description field is simply {J} (I am using version 2), so that what I set as the Job Code then becomes the basic caption.


possibility to set different parameters for each Job. For example, when I try to download pictures for different days from the same card/directory, the sw creates automatically one Job for each day, and this is great. The drawback here is that, for example, if I want to set some iptc parameter during the download, different from day to day, I have to modify that parameter for each day I'm going to download, without possibility to download all pictures together.
You can actually set Job Codes for each day, and then download everything in one go, using the Job Code as I have described. The trouble is that you cannot have separate sets of IPTC data for each day or job, and often you want to change keywords, for example, for different sets of images.

I do not myself regard this as a limitation of the software, but as an inevitable consequence of the fact that different groups of images will need different IPTC data. I can't think of any way in which the software could significantly reduce the workload which arises from this fact; indeed, I tend to add only basic IPTC data (i.e. data which is common to the whole download or which can be represented by tokens) in DL Pro and then use BB Pro (which has a much wider range of editing facilities) for the fine tuning.

[claudio ercoli]

If I understand this request correctly, DL Pro can already do this. For instance, I tend to use the Job Code as the common element of the caption in each set of images. So I have the Job Code dialogue come up when I start DL Pro. In my standard IPTC data set, the Description field is simply {J} (I am using version 2), so that what I set as the Job Code then becomes the basic caption.

This is true for caption but not for keywords, the most useful for me. Is it possible to add this ?

[QUOTE=DavidB]You can actually set Job Codes for each day, and then download everything in one go, using the Job Code as I have described. The trouble is that you cannot have separate sets of IPTC data for each day or job, and often you want to change keywords, for example, for different sets of images.

I do not myself regard this as a limitation of the software, but as an inevitable consequence of the fact that different groups of images will need different IPTC data. I can't think of any way in which the software could significantly reduce the workload which arises from this fact; indeed, I tend to add only basic IPTC data (i.e. data which is common to the whole download or which can be represented by tokens) in DL Pro and then use BB Pro (which has a much wider range of editing facilities) for the fine tuning.

Yes, it should build different, let me say, database for each job, but probably it is too much complicate. Anyway ok.

Claudio

[Chris Breeze]

Braces (aka curly brackets) are used for entering keyword synonyms and so you need to use the old style tokens for keywords e.g. %J for keywords.

[claudio ercoli]

Braces (aka curly brackets) are used for entering keyword synonyms and so you need to use the old style tokens for keywords e.g. %J for keywords.


Ahhh ok. Thanks.

it is working now.

Great

Claudio

[DavidB]

... and so you need to use the old style tokens for keywords e.g. %J for keywords.
Thanks, Chris; I was not aware of this, but then I always enter keywords as absolute values. Is the use of the old-style tokens documented anywhere? I haven't found it by searching the help file on either 'token' or '%'

[Chris Breeze]

Downloader Pro uses the same keyword catalog code as BreezeBrowser Pro and this uses braces for synonyms. Unfortunately this clashes with the delimiters used for DLPro's tokens and so for keywords only you need to use the old style tokens. These are the same as the new tokens except they are prefixed with % rather than enclosed by {}. Only pre-DLPro 2.0 tokens can be specified using old style tokens (which is most of the tokens).

[DavidB]

Downloader Pro uses the same keyword catalog code as BreezeBrowser Pro and this uses braces for synonyms. Unfortunately this clashes with the delimiters used for DLPro's tokens and so for keywords only you need to use the old style tokens. These are the same as the new tokens except they are prefixed with % rather than enclosed by {}. Only pre-DLPro 2.0 tokens can be specified using old style tokens (which is most of the tokens).
Thanks, Chris. I had understood most of this from your previous post. My point was that I have not found the information in the help file. Have I missed it?