Configurable default action for folder names

[G8DHE]

Yes I've added other directories including ones with spaces in the name no problem.

[RobiWan]

Hello Hert,

Save attached file in your AppData folder to have the default action for a folder named NKSC-PARAM to be "No Action".

thank you for this.
But - "0" is for "no action". Do you have anther numbers for another actions?

And its possible to use this for files too?

[Hert]

I did mention that you can also use this for files. The name can be a mask and is used to match files and folders. Note that if the mask matches both a file and a folder then you won't be able to reliable configure that in the file. So use it wisely.

Folder Not in Catalog:
0 = No Action
3 = Add Folder to Catalog
4 = Ignore this Folder

Folder in Catalog, not on File System
0 = No Action
1 = Remove Folder from Catalog
2 = Map to the Correct Physical Folder (advise: do not use this one in the mentioned file)

File Not in Catalog:
0 = No Action
7 = Add File to Catalog

File in Catalog, not on File System:
0 = No Action
5 = Remove File from Catalog
6 = Map to the Correct Physical File (advise: do not use this one in the mentioned file)

File changed on File System compared to Catalog:
0 = No Action
8 = Import Data from File
9 = Export Data to File
10 = Update File Signature

[RobiWan]

Thank you Hert

[fbungarz]

A question about naming masks:
Is it possible to configure folder or file names using wildcards?

As filing convention I use the date picture taken to name folders, e.g., today: 2022-09-23.

Could I use something like this:
2022-09-**=0
... which might mean that all folders named September 2022 will be scanned with "no action", the * used as a wildcard for any digit.

Another question:
When using different database can the VerificationUserDefaultActionsConfiguration.txt be different for each database?

[fbungarz]

It seems like using wildcards does work.
Just out of curiosity, I created some folders named "original" and others "originals".

In the VerificationUserDefaultActionsConfiguration.txt file, I then added:

original*=0

Using the asterisk * as a wildcard.
When scanning for missing folders and files, both folders, "original" and "originals" are set to "no action".
That's great.

Unfortunately this all doesn't work on subfolders.

Say, I have a parent folder with two subfolders:
parent: images
subfolder 1: originals
subfolder 2: edited

Now, I only want to add images that are in the parent, not the folders or images in the subfolders.

So, I add ...
original*=0
edited=0
into VerificationUserDefaultActionsConfiguration.txt

Then, I scan the folder "images" for missing folders and files.
The parent "images" is set to "add folder to catalog", but by doing so, its subfolders "originals" and "edited" also get added, despite them being configured to be set to "no action"...

[G8DHE]

That's strange because that's how I'm using it but don't have the need for wildcards ?
In my case the editors I use create a sub directory to hold recovery information, so I don't want those folders/files listed in PSU they can occur at any level in my folder tree so I simply have the named folders (one name for each type of editor) marked as to be "no action" i.e. =0

[fbungarz]

Hi Geoff,
sorry, I should have been more precise.
When I scan a folder for missing folders and files, then the subfolders immediately below get set to "no action".
But when I scan a folder which has a subfolder and that subfolder has other subfolders, then the exclusion list no longer works.

In my case I have:
\\plates\plate_1\originals
\\plates\plate_1\edited

I want the images in \\plates\plate_1
But I do not want the images in \originals or \edited

If I create a mask that sets edited=0 and originals=0, but scan \\plates, then \plate1 is set to "add folder to catalog", and if I click ok, the subfolders get also added, even though I have set them to "no action".

Perhaps the only option doing this to set: originals=1 and edited=1. Then run the import on \\plates, which will add everything, immediately followed by another run, which will again remove all \edited and \originals...?

[G8DHE]

Ah I think I can see why I don't suffer that problem. All my images get loaded directly into PSU in there folders before any editing takes place, hence at that stage all wanted folders are included. Only after they are loaded in PSU will any editing take place, at the next scan the editor recovery folders are seen but "no actioned" but the original folders are already there and hence remain there and any changes in the files are picked up and included.
I'll have to try scanning some folders where the images have already been edited and the unwanted folders are present, maybe then the entire branch & twig will appear because the branch folder is included .......

[G8DHE]

Yes can confirm that is what happens, created a new set of folders, edited image at the lowest level hence creating a "recovery folder", then allowed PSU to scan the whole tree and it created the full set, the pre-existing folders were indeed ignored, but when it built the tree itself it then included the directory as it was a descendent of the one above!;

treetest-1.JPG (166.75 KiB) Viewed 3159 times

treetest-2.JPG (18.06 KiB) Viewed 3159 times

[fbungarz]

I think that actually does make sense: adding a folder to the catalog, you'd normally assume its subfolders are added too. But it would be nice to have an additional option to only add the folders, not their subfolders if these are set to "no action".

[fbungarz]

I just realized I cannot use the "1 = Remove Folder from Catalog" option, because that works ONLY if the folder doesn't exist on the hard drive, if the folder exists "1" means "add to catalog".

Would have been too nice, if there was an option to automatically remove folders (not deleting the files), based on a file mask