Multilayer collection structure is not restored in a new computer

On my laptop there is a multilayered structure of Collections.
Dopus installed on C. The files and collections on Drive N

On a new computer I have the same configuration of drives C and N.
I duplicated the files structure on the new drive N

I used the fully backed up configuration file from the laptop
to restore in the new PC.

The collections having only one layer (root) were reproduced correctly
BUT
Collection trees (coll1>subcoll2) were empty.
Could it be that the collection tree information in the old computer is saved somewhere else on old drive C or N ?

Collections are stored in

/dopusdata\Collections

If you suspect the collections might be corrupted or incomplete on the new computer, copy the folder from the old installation. Note that Opus removes entries from collections if they point to unavailable files. For example, if the N: drive hasn’t been attached for a while, that could explain the issue.

1 Like

Thanks, it s an idea...
I did find a "collections" file on the old C drive (C:\Users\bloch\AppData\Roaming\GPSoftware\Directory Opus)
It seem to contain the correct multilayer structure! If I understand your advice it is to copy it to the same place to the C drive in the new PC.I will try it BUT still does it not what the configuration file was supposed to restore ?

You need to copy collection config files while Opus is not running. (File > Exit Directory Opus; don't just close the window.)

1 Like

The copying of the collection folder solved the problem.
Thanks to both Ipx and Leo.
Still, it seems that the config file that is used to backup and restore the program has a problem with embeded collections (perhaps related to a non english alphabet (Hebrew) that should be fixed.

Do you still have the config backup? You can rename the extension to .zip to check which files it had inside it.

I followed your advice and renamed the config file to zip.
It seems that all the collection folders that were originally in the Hebrew language, appear now with garbled fonts ( like it was not translated correctly by Ansi or Unicode) . BUT, they contain the right subcollections (still with garbled fonts).
Remind you that in DP these same collection folders appear as empty.
I therefore deduce that a config file does not handle correctly foreign fonts perhaps because fo lack of complete Unicode support. Therefore DP does not recognize them as collection folders.
Does this make sense to you ?

I think you have probably misdiagnosed the issue there. The way the data is displayed will be down to your text editor and the way XML encodes strings, and doesn't reflect how Opus itself will interpret the data.