[pended] All Products are in Lost & Found...
Topic in Commons about finding content had me wondering too, and led to the following.
1.) DS has an estimated 680 ‘lost & found’ entries with grayed out tiles that say 'u'. They are in products, load fine, etc.
a.) Manually deleted three entries in DS and their 'DZX' files in explorer. Load OK.
b.) At least two ‘DSX’ files do not show in DS.
Do *not* delete:
IM00018869-02_PostgreSQLCMSWin64bit.dsx
IM00018869-02PostgreSQLCMSFromValentinaCMSConversion.dsx
(These are required for DRM?)
2.) Can the automated by a script?
That’s quite a few entries to delete in DS because it won’t allow me to select > 1 of them.
3.) Perhaps most important. What path in DS or the DIM might be incorrect if this many ‘lost & found’ entries?
thanks for reading
--Bruce
Comments
The product .dsx files are used in DS only if you reimport metadata so I'm not quite sure what you are meaning.
Thanks. You’re very patient as always.
1.) What might be causing products to go into Lost & Found?
Some items don’t show up in categories, only under product name.
Example: “Classic Pipes” shows in Products. Does not show under “Props” ; “Moped” shows in Products but not in Transportation & so on.
2.) If I take the time to remove the grayed out ‘lost & found’ tiles in DS, are they just going to reappear the next time I use the DIM? If they are, will not waste time on it.
3.) Hate to sound dense, but for recovery better to leave .dsx files, delete, or makes no difference? They have nothing to do with the 'lost & found / categories' problem?
Thanks again. Learning DS is hard and so are some of the technical things. Appreciate your time.
1. Lost and Found is just stuff that isn't categorised. If you are looking at the Products tab of Smart Content then products will appear there even if only one of their files (for example, a store link) is uncategorised.
2. No, Userdata (your categorisation) will not be overwritten
3. Lost and Found is not an error, it's just the way things are categorsied. If you zap the .dsx files then you won't be able to restore the base categories by reimporting metadata, and fresh install may overwrite your own categorisation as there won't be a record of the original vendor data to flag as superseeded.
OK, sounds like .dsx files should stay if run into problems-- thanks.
Don’t want to belabor the ‘Lost & Found’ question, so maybe screen shot would help.
1.) Any idea why almost everything in DIM would show in Content Library as “Lost & Found” ? (Important for question 2)
2.) Is there a way to clear all entries in “Lost & Found” at once, or I’d have ‘delete & confirm’ approx 600 times?
Prefer all categories clean & ‘default’ as it were. Backup DS before I make any custom categories. Lot of money involved, so want to err on the side of caution. I appreciate your patience.
"Lost and Found" isn't an error or a problem, it's not a place things are it's a collection of things thata ren't in another palce. That means you can't batch remove items, except by adding them to another catch-all category.
That said, it does seem highly unlikely that all of those products should be there so it may indicate a communication issue. Make sure you don't close DS and launch DIM immedately as that can lead to the database not being available during install. You could try reimporting metadata - Content Library option menu (the lined button in the top corner, or right-click the tab)>Content DB Maintenance, then check the reimport option, then use the master check box to select all products at ince and click Accept.
Good advice-- I learned something-- but it didn’t work. One last idea, then will probably just live with it.
Where is DS getting the metadata-- would the path make any difference?
default path on “C” (My Daz Library) is empty. Another set of more detailed .dsx files are in C:\Users\... path ... Installmanager > Manifests
Content is on “E” (My Daz Library) these .dsx files if required are all 1KB and just seem to be 'proof of purchase' nothing about what is installed or where.
I know you must be very busy, so thanks again for your help.
The Manifests folder is used by Install Manager to ercord what it has installed. The metadata files used by DS to eimport the metadata are in the /Runtime/Support folder of the content directory you installed to. They are diffrent files for different jobs.
Would’ve like to have marked topic ‘solved’ but seems not in the cards. Not for want of trying though. Appreciate your replies-- learned about metadata, directory structure and file extensions so still very helpful.
thanks!
--Bruce
Here is the issue I am having, and hopefully someone can answer and/or help me. I will sort a product into its proper folders, locations, etc. I will use the Content Package Assist to make it into an install format the DAZ installer will install. I install the product, and it shows up in products and works fine. I make a few other tweaks, but everything is working. I then take the time to categorize everything and use the CB Editor to link everything. It shows up in Smart Content, works beautifully. I then export the metadata file, and replace it in the duplicate zip file under support so I can reinstall and have all my categories done, and have the smart content show up with no more work. However, it doesn't work. When I then try to fresh install that product, with all the categories in the support file, it is re-installed into lost and found, and the DAZ installer does not have a check marks showing there is a metadata file. When I open the text file in notepad, it is showing all the categories there. Any help will be greatly appreciated.
Thanks.
I did notice a small gotcha in CPA that might trip you up if you haven't noticed it. In the Settings, there is a checkbox for "Auto Clean /Runtime/Support" that will remove any .dsx file that you include. If you generate the package when the support file is not in the folder, no entry for it is made in the manifest.dsx. If you later add the metadata support file to the archive, it won't get installed. (Got me a couple of times)
When installing a product with no metadata, DIM will generate a .dsx file with virtually nothing in it except for Asset and SupportAsset statements with no content type or categories, overwriting the one that was in the library's support folder, resulting in dumb content.