Hi Cynthia, this isn't possible with Asset Essentials and Lightroom. Asset Essentials doesn't allow for custom integrations. For that you would need AEM Assets Enterprise. Lightroom isn't an out-of-the-box connection to Asset Essentials, so you'd either need the Adobe product team to build an out-of...

Perfect!  Thank you for the quick reply!

We are getting an error when trying to generate a Smart Crop on a very narrow image (32x1200).  Dynamic Media is throwing an error: "The supplied auto-swatch generation parameters (SmartCrop) led to an invalid swatch. No auto-swatch operation was applied to this image."  Our Smart Crop swatch parame...

I would note that 14k assets is not a large AEM Assets repository.  Most customers don't purchase AEM Assets until they have at least 10k assets.  I've seen the system scale to well over 10M assets and Adobe has indicated the system theoretically scales to a petabyte.  If you're having issues with o...

There is no out-of-the-box function that will do what you're looking for.  All out-of-the-box asset reports export information on assets and only include folders as part of the path. You can likely configure a report that meets your needs with ACS Commons Reports (https://adobe-consulting-services.g...

I think the Export Metadata function would be the best way to capture all the entered asset descriptions.  If you did this at the top-level of your /content/dam folder tree, you would get all the entries for selected metadata field(s) for the entire repository into a CSV.    One tip to mention: in a...

We are trying to work around the limitation that you cannot apply Dynamic Media Image Serving and Image Rendering API syntax to Smart Crops.   The base use case is that we need to generate large square Smart Crop and then create 5 smaller images from that Smart Crop starting point.  (For clarity, we...

Request for Feature Enhancement (RFE) Summary:Dynamic Media currently restricts outputs to 25 megapixels.  Many customers have larger source files and may need renditions of higher quality as well.  You can configure higher quality renditions as static renditions, but these renditions aren't availab...

You can get this by creating separate tag fields.  Instead of relying on cq:tags (which I've always found a weird decision in Adobe's out-of-the-box metadata schema), I think better user interface (and better data structure) is to have separate tag fields.  So you could have 1 for Devices that only ...

Thanks for the update.  Since we posted this, we did find a way to make this functionality available via security updates rather than customization.  We have only verified this functionality in 6.5.  The security adjustments may not be possible in AEMaaCS.