Batch rename: using the Directory field

[B.Douille]

If you select "Directory" as a field to use in the renaming template you get something useless:
"C-\Documents and Settings\Username\My Documents\..."

The column after the drive letter is replaced already but not the backlash. I understand that a user can take profit from the Replace option but it's not obvious. Is this normal behavior?

Anyway I don't see the benefit of naming a file with it's original path It may drive to very long names except if you used to store your images near the root directory. Other users may explain/confirm usage.
May I suggest to replace this field with another? Say the parent folder name. This may allow to set names like "Holiday_Belgium_004" where files are stored in a directory structure like
"C:\...\My Pictures\Holiday\Luxemburg"
"C:\...\My Pictures\Holiday\Belgium"
...

[marsh]

Confirmed.

[xnview]

If you select "Directory" as a field to use in the renaming template you get something useless:
"C-\Documents and Settings\Username\My Documents\..."

The column after the drive letter is replaced already but not the backlash. I understand that a user can take profit from the Replace option but it's not obvious. Is this normal behavior?

So replace all '\' by '_'??

Anyway I don't see the benefit of naming a file with it's original path It may drive to very long names except if you used to store your images near the root directory. Other users may explain/confirm usage.
May I suggest to replace this field with another? Say the parent folder name. This may allow to set names like "Holiday_Belgium_004" where files are stored in a directory structure like
"C:\...\My Pictures\Holiday\Luxemburg"
"C:\...\My Pictures\Holiday\Belgium"
...

You have <foldername>

[B.Douille]

If you select <Directory> as a field to use in the renaming template you get something useless:
"C-\Documents and Settings\Username\My Documents\..."

The column after the drive letter is replaced already but not the backlash. I understand that a user can take profit from the Replace option but it's not obvious. Is this normal behavior?

So replace all '\' by '_'??

Probably the most obvious, yes.

Anyway I don't see the benefit of naming a file with it's original path It may drive to very long names except if you used to store your images near the root directory. Other users may explain/confirm usage.

How do we know if the field is still in used? As the renaming function has evolved over time, there are chance that the field <Directory> became useless. Can we put this as a "proposal for change or removal" in the next release?

May I suggest to replace this field with another? Say the parent folder name.
This may allow to set names like "Luxembourg_Old houses-004", "Luxembourg_Museum-002"... where files are stored in a directory structure like
"C:\...\My Pictures\Holiday\Luxembourg\Old houses"
"C:\...\My Pictures\Holiday\Luxembourg\Museum"
"C:\...\My Pictures\Holiday\Luxembourg\Tonton"
"C:\...\My Pictures\Holiday\Belgium\See side"
...

You have <foldername>

I though of parent folder: the level under <foldername>. My examples wasn't obvious. I amended in the quote above and here is a sample template: "<parent>_<foldername>-#". So you classify, visually the pictures in relevant folders and start renaming.
As we are in the late stage of delivery for 1.90 I propose to keep the idea and move this post in the list for the next release, awaiting remarks form actual users of <Directory>, if any.
What do you think?

[xnview]

Anyway I don't see the benefit of naming a file with it's original path It may drive to very long names except if you used to store your images near the root directory. Other users may explain/confirm usage.

How do we know if the field is still in used? As the renaming function has evolved over time, there are chance that the field <Directory> became useless. Can we put this as a "proposal for change or removal" in the next release?

May I suggest to replace this field with another? Say the parent folder name.
This may allow to set names like "Luxembourg_Old houses-004", "Luxembourg_Museum-002"... where files are stored in a directory structure like
"C:\...\My Pictures\Holiday\Luxembourg\Old houses"
"C:\...\My Pictures\Holiday\Luxembourg\Museum"
"C:\...\My Pictures\Holiday\Luxembourg\Tonton"
"C:\...\My Pictures\Holiday\Belgium\See side"
...

You have <foldername>

I though of parent folder: the level under <foldername>. My examples wasn't obvious. I amended in the quote above and here is a sample template: "<parent>_<foldername>-#". So you classify, visually the pictures in relevant folders and start renaming.
As we are in the late stage of delivery for 1.90 I propose to keep the idea and move this post in the list for the next release, awaiting remarks form actual users of <Directory>, if any.
What do you think?[/quote]
Yes

[marsh]

If you select "Directory" as a field to use in the renaming template you get something useless:
"C-\Documents and Settings\Username\My Documents\..."

The column after the drive letter is replaced already but not the backlash. I understand that a user can take profit from the Replace option but it's not obvious. Is this normal behavior?

That part is fixed in RC1. Dash '-' is replacement character.

[B.Douille]

Ok, thanks for the improvement.

Still the longer term proposal for change: I'll post in another forum so we can close the story for this release.