I am trying to integrate the opus collections systems into other process and workflows. I have figured out most of what I need, accept for the attr,access, create, modify, reserved and size node attributes:
...
<item access="+1db1742+6944ffd7" attr="32" create="+1d94071+b09a93db" modify="+1db1742+6116c1b5" reserved0="0xa000000c" size="225">C:\temp\file1.txt</item>
<item access="+1db1742+69451e3c" attr="32" create="+1db0533+698ee29" modify="+1db1742+61170fcc" reserved0="0xa000000c" size="228">C:\temp\file2.png</item>
...
Can developers please chime in on what each attribute denote to?
Lastly, what date/time format doe the strings +1db0533+698ee29 use?
I am working with .net so I am confident in decoding them on my end but I have yet to Identify them. I am aware of DopusRT, ideally I would like to just remain within .net and work with the existing collections files, rather calling DopusRT to generate an Xml file.
I asked chatGPT and its not sure:
The string "+1daeaa2+503bca64" does not immediately correspond to a standard or recognizable data type like a date or timestamp. Based on its structure, it appears to be:
-
Hexadecimal values: The string seems to contain two segments,
1daeaa2and503bca64, which are both valid hexadecimal numbers (composed of digits 0-9 and letters a-f). -
Custom encoding or identifier: It could be part of a custom encoding or identifier system, possibly used for things like:
- Unique session or user IDs.
- Data hashes or checksums.
- A string for cryptographic purposes.
Why it's not a date:
- It doesn’t follow the typical format for a date string, such as
YYYY-MM-DD,MM/DD/YYYY, or ISO 8601 formats (YYYY-MM-DDTHH:MM:SSZ). - There are no obvious date/time-related components (like numbers representing year, month, or time).
If you were expecting this to represent a date, you might need additional context (e.g., how this string is generated or where it's coming from).