Directory Opus labels support

[err_24546]

Happy holydays void, I hope you had a wonderful time.
Closely related to this other post, where Directory Opus Tags were finally supported, would there be a way to extend that support to Labels?
As far as I can see, like tags, they are also written in OpusMetaInformation.
And the ADS Hex column value for that file is:

Code: Select all

14000000010000000000000000000000000000001D99C35E49F935458FB34769EBEC85DF

Here is the test file if it can help you at all.

test_labels-DO.zip

(170 Bytes) Downloaded 310 times

Thank you very much for your time!!!

[void]

Happy holidays!



Labels are no longer stored in the OpusMetaInformation stream.



The label is likely stored in the [5]SummaryInformation stream.



Could you please send a copy of the Alternate Data Stream Hex values:

• Right click the result list column header and click Add columns....
• Select Alternate Data Stream Hex and click OK.
• Select a file with a label.
• Right click under the Alternate Data Stream Hex column and click Copy Alternate Data Stream Hex.
• Could you please paste the value in your reply.

[err_24546]

Labels are no longer stored in the OpusMetaInformation stream.

I thought so, since the file I uploaded in the first post was newly created, I put a label on it and looked at Everything.
In Alternative Data Stream Name only appeared OpusMetaInformation

please send a copy of the Alternate Data Stream Hex values

Code: Select all

14000000010000000000000000000000000000001D99C35E49F935458FB34769EBEC85DF

Is from the same file from the first post.
Thank you very much for taking a look at this.

[void]

Thank you for the hex values.

I have put this on my TODO list.

The label is unfortunately not stored in the [5]SummaryInformation stream.

[err_24546]

The label is unfortunately not stored in the [5]SummaryInformation stream

Exactly, is stored in OpusMetaInformation stream, like Tags. That's why I was wonder, since support for Tags was already achieved (see here), it would be more easy to extended the support for labels as well.

[void]

Tags are now stored in the [5]SummaryInformation stream.

Tags (keywords) are now included in the [5]SummaryInformation property set.

Labels are not included in the [5]SummaryInformation property set.

I need to work out where Directory Opus is storing labels.

[err_24546]

Sorry for caussing you some confussion. I was talking about Directory Opus Tags. Those are written in OpusMetaInformation as well. In this post, you give support for Directory Opus Tags in Everything

[err_24546]

I've done the following steps to verify where Directory Opus stores labels

• Create a new text file, so I make sure that I don't have any ADS at the beginning.

• Set a label via Directory Opus to the created file.

• I used the Nirsoft Alternative Data Stream Viewer tool to see what streams the file contained. The only stream it has is is OpusMetaInformation.

The bad thing is that the saved stream content is quite cryptic. (probably not able to read by other programs)
As a sidenote, I've also checked where Directory Opus stores own tags, and it is also in OpusMetaInformation, but in this case, its stream content is more accessible (seems hex value for plain text).

[WKen]

Response from Directory Opus developers:

I guess a problem with labels would be that some of them are defined by rules (e.g. a wildcard) rather than written into the filesystem (NTFS ADS).

The ones written into NTFS ADS should have a GUID for the label(s) which can be turned into a name via the definitions in:
%APPDATA%\GPSoftware\Directory Opus\ConfigFiles\colorgroups.oxc

Matching all labels would be a lot more complex, and it probably wouldn't make sense for Everything to re-implement everything, as it'd have to keep being updated as we make changes. We could provide an API to query the labels for a list of paths, or something along those lines, maybe.