I want to use PRINT FOLDER to dump the content of a very large coll:// with nested collections
There doesn't seem to be any way to associate which file is in which collection folder. For instance,
Create a collection called ABC
Inside ABC, create collections A, B and C
Add image1.jpg to A, image2.jpg to B, image3.jpg to C
Dump the collection with:
Print FOLDER coll://ABC CALCSIZES=no AS=csv FLATVIEW=grouped FORMAT=JP TO={dlgopen|Select location to save folder list...|{alias|mydocuments}folder_list.csv} QUIET
Off the bat, this seems to work. Now add image3.jpg to A and you get:
It seems mind boggling that there isn't a folder format which includes a column like "Collection name" or "Collection path".
It also seems very reasonable to have a column Collection Fullpath which would be the fullpath to the file within the collection I.e., coll://ABC/A/image1.jpg
So what are my options? dopusrt.exe /col export is really lackluster since it can't recursively export.
Right now the collection I'm generating has 3,856 subcollections. So exporting it means running nearly 4,000 dopusrt.exe commands
Reading the data directly from GPSoftware\Directory Opus\Collections\ is an option but I'm not sure how reliable it will be. There seems to be some delay in how these files are written. Do you know what triggers dopus to write the .col files in this directory? Is there any command I can issue to force it to flush to these files?
Are there any other options besides the two I mentioned?
If you have that many subcollections it's probably going to start causing performance issues. (Opus updates collections each time it starts, for example.) Collections may not be the best tool for the job here, not just due to Print Folder not doing what you want.
Taking a step back, what is it that you want to use the collections for and do overall? There may be a better way.
