If you delete the folder or its contents after installing the content and before starting DS then the new items won’t be added to the queue and you won’t be prompted to process them.
Not sure what you are answering here Richard.
With Install manager the metadata is written directly to the database as part of the install process. For Carrara users this means no more opening DAZ Studio to populate your Smart Content tab. For DS users that means no more delay on open to process new content.
I tried to follow this thread as good as I can. I understand that there are users who do not use metadata at all.
For me as someone who invested two months to categorize my content with “categories”, “file types”, “compatibility bases”, “scene IDs” and “Tags” it is a huge deal how the DIM now does not seem to give the user the option to choose if metadata is installed or not.
For new products I will want the official DAZ metadata.
And I also appreciate the “mini-metadata” added for old products that do not have proper metadata.
But for many reason when I spent hours to customize the metadata of a product I do not want those customizations just to be overwritten by the DIM without giving me an option to say stop.
I will certainly want to install the updates to the product. But I may not want to install any updates to the product metadata if I allready customized it myself.
Before this could just be done by choosing not to process the metadata added to the queue at startup. How is this done now?
- - -
I have two questions:
Is there in the current version of the DIM really no option at all included to prevent the DIM from writting directly to the database?
If the DIM is writing directly to the database are there still any files placed in /runtime/support?
- - -
Currently I am under the following impression:
The only way to prevent that customizations made to products are kept is to go to the “Product Library” “Content DB Editor” and export the .dsa and .dsx files to /runtime/support and make a backup in another location that needs to be reimported AFTER the DIM has finished installing.
The normal “User Data” is not enough to make sure those changes are not lost. Exporting and Importing needs to be done on a “product” level.
- - -
In any way I spent a lot of thought on the consequences for metadata management with and without the help of the DIM.
To be able to use all the useful functions of the DIM I am currently preparing to reinstall my whole runtime once again.
I would like to do the reinstallation the way DAZ officially suggests and hope DAZ can provide a complete guide how to do that especially for users that allready created a large library of customized metadata that I would like to call “User Product Data”.
“User Product Data” is a term I would like to introduce for metadata “products” that were customized by the user and then exported as .dsa and .dsx files to /runtime/support from the “Product Library” using the “Content DB Editor”.
The “User Data” as introduced by DAZ is a collection saved in just one file of all changes a user made that are NOT saved in a “product” and exported.
Currently I am very worried that DIM and also the current DAZ metadata management tools are mainly designed towards the users that just use “User Data” as a quick way to customize content.
To make full use of the CMS and all the metadata tools I am strongly convinced one has to be able to make use of the “User Product Data”, making backups on a product level ready for export and import as a preparation for updates and complete reinstallation of the whole runtime.
- - -
I am also aware that not all people are interested in metadata.
As there has been said there is not just one way to organize a runtime.
I can understand that it is not easy for DAZ to come up with solutions for all those different needs.
The introduction of the DIM seems a good opportunity to completly reinstall the whole runtime.
I put together some kind of a step by step guide how that process was done before the DIM and now invite those interested to have a look at it and share and discuss how that process could be updated with the new options the DIM introduces:
Metadata Management - complete reinstallation preparation - step by step
I see this step in step guide as a collection of the status quo and work in progress document until DAZ makes an official document available that deals with all those questions a complete reinstallation of all content WITH all metadata brings.
It would be great if those people who worked on the DIM could share their experiences if those steps I came up with are reasonable or if I am missing some importent points that may alter the way metadata reinstallations were done in the past that I have not yet mentioned.
I can understand that you cannot share all information now until the DIM is officially released.
But I would be very happy if you could provide some useful tips and suggestions as soon as the official release is available.
- - -
Thank you for reading.