OpenEdit User ForumWelcome to the OpenEdit DAM User Forum. You must be registered and logged in to post a new comment or topic. If you require dedicated support to your OpenEdit DAM project, please see our Buy OpenEdit DAM Support page for more information. new asset forcing scanWhen adding a new asset subfolder, metadata is acquired for all previous sub-folders. This is not ideal, as our install is handling thousands of images. In addition, if the acquisition of metadata fails (heap space errors, frequently), we are left with partially scanned assets which require a full rescan per sub-folder.
I would like to disable the scan of exisitng sub-folders. Can this be done safely? |
Hi,
If you're mounting this subfolder they you have to skip the "Synchronize" step, go into the new subfolder and run the Sync there. This will scan assets recursively through this new subfolder.
Thank you for your response!
I am finding that after clicking the "Add" button to add a new subfolder, there is a synchronization occuring without asking.
Watching the server logs, it retrieves metadata for all images before it adds the new sub-folder. This is where the process fails with memory errors.
We are going to be moving the openedit install to some new hardware, I will post if we have succcessfully done this, and what hardware we used to accomplish it.
Keep in mind, we are dealing with what I would consider to be massive amounts of images. ~75gb worth of jpegs and tiffs.
Yes, that's true we're forcing a sync when adding a new folder. This should be fixed sometime, but I don't think it's a priority right now. You can hire a consultant to get this done quickly.
I will keep an eye on this thread as i would like to know how it goes with your new hardware. I'm pretty sure OpenEdit will do fine. We have a client runing OpenEdit for 123GB of images on a Sun machine without problems. Good luck!
Hi!
I took a deeper look at this and came up with a solution very quick. I uploaded the new code so it should work as you wish if you upgrade your "Digital Assets" plugin.
Woot!
Working perfectly now.