From the context menu, which applies the labels to actual folder, files and stores in the meta data on NTFS or fall backs to ADS. I see this triggers the setting of archive flag.
A label which is applied to a path and is set somewhere centrally and not on the actual file. The archival flag isn't set here.
I prefer the second approach where the labels are stored centrally as it can facilitate quick retrieval.
Where are the centrally stored labels located
Is there a way I can apply labels to a path rather than the actual file from the folders context menu
How can we do a quick search for the centrally stored labels. I trust these are readily available as preferences section shows it and hence, don't want to trigger a file system search for this.
You can control where labels are stored by default via Preferences / Favorites and Recent / Labels / Automatically store labels in the file system if possible.
Searching by label can be done via Tools > Find Files > Advanced.
Labels that aren't stored in NTFS are stored in your Opus configuration. Note that that type of label points to the path they're assigned to, literally. It will not change if you move, rename or delete the file; it's still point to the path it was assigned to, waiting for a new file with that name.
Kind of what I want. I did expect that a DOpus rename, move would alter the label and delete from within DOpus would delete the label but this is OK.
\AppData\Roaming\GPSoftware\Directory Opus\ConfigFiles\foldercolors.oxc file has these labels
Will this do a file system search or lookup from the file. If former, is there a way I can do the later instead. If not, I'll resort to scripting but would appreciate pointers.
It does find even if Enable label storage in the file system (NTFS volumes only) is off. But as it's a file system search its slower. It looks for the label in the file system even though this is turned off. Appears that it first searches the file system and then checks the config file. Can we have an option to search only the config file?
Everything tool supports index ADS, it would be nice to see text in Everything tool, such as Red, and also to use scripts to search via Everything tool.
Turned that off and noticed that it doesn't read labels from file system which is OK. However; why does it still navigate the File System during find. Shouldn't it instead directly list the files from the config which have that label assigned.
Would it be possible to consider altering this behavior in a future version
Scenario 1: The find is triggered without labels. No change
Scenario 2: Only label search is done. This should just match the labels from the config file. If a computer wide search is triggered for a label, the speed boost will be immense as it only needs to check a single file to do the listing against navigating the entire file system. There is a possibility that some of the files in the config are no longer present on the file system and those can be filtered out or the missing files can be displayed as zombies.
Scenario 3: A label search along with other non-search criteria (AND). The current way is to do a filesystem search and apply the label criteria simultaneously. In revised way, it searches the labels first and then performs a find within find. Again, the speed gains will be immense.
Scenario 4: A label search along with other non-search criteria (OR). No change
