I am in the process of cleaning up my DS installation.
A huge part of that was to assign categories to all files in my runtime.
The goal each day was to have no files left in Categories/Unassigned.
For quite some time now I have struggled with the fact that always some files remain without a category:
- Geometry files (mostly .obj from .dpc content)
- Poser material files (either .pz2 or .mc6)
As I now finally realized the cause of all this is that those files are not part of the “Product”.
Only data related to files that are part of a product are included in the .dsa and .dsx files that are exported from the “Product Library” “Content DB Editor”
So even when one would take the time to assign Categories to the geometry or poser material files that are not part of the product those efforts could not be shared.
Adding the poser and geometry files to the “Product” would not be a reasonalbe solution because the main goal of having “Products” seems to be to have a quick way of selecting only those files that are needed for DS.
The way “Metadata” sharing works it seems just not possible to share any information about files that are not part of a “Product”.
The information that is not exported may be saved automatically as “User Data”.
But as far as I understand there is no way to share that “User Data” part.
- - -
Is there any way that the “metadata” like “Categories” “File types” “Compatibilites” can be saved inside every file we install and not as separate information that is read from the .dsa and .dsx files and after installation the database?
If I open any file on my PC there is additonal information saved in the “Properties”.
Could the CMS load the metadata by reading each new files information the first time it is loaded into DS?
For example in Content DB Maintenance there is an option to scan for new files.
Instead of just marking the files as new couldnt at the same time be read metadata information of individual files?
Would it be possible to give the user the option that the metadata information is directly saved into any content file whenever the uses makes any changes in the Content DB Editor or the Categories?
The CMS databases could still serve as a the main saving place for “User Data”. But all those who intentionally want to make any modifications to the metadata would have an option to do so on an individual files base.
Like that the only backup one would need to make is a backup of the whole runtime.
There would be no more metadata loss if the CMS crashes or the databases somehow get corrupted.
The metadata information would still be there in each individual content file.
- - -
I can understand that for sharing metadata it is useful to have a way to extract the metadata from the file and share only the metadata independently.
But for the purpose of installing and editing metadata Metadata information could be included in all files of an installer and not just those that are part of a “Product”.