Hi @sogden  you can just check the timeline of the asset (see snapshot below). It lists jcr:created and jcr:createdBy properties of the asset.   For bulk viewing , use OOTB Asset report.

I would suggest to install wknd package and check if you are able to replicate issue on wknd site on test env. If yes, it must be an issue with your cstom component.  You can view source and see if you see image html. Also check image component policy on template 'width section'

Is it happening on a specific env ? Install wknd reference package and check if you can reproduce the issue on wknd. https://github.com/adobe/aem-guides-wknd/releases I am unable to reproduce the issue on my local cloud with image v3 core component on wknd reference site.   Are you able to upload th...

Hi @Vani1012  , before you browse for image make sure to uncheck this 'inherit' box for description , then browse for asset and add alt text. This seems to be an issue in hide behaviour. 

@Vani1012 : can you try to upload same image from dam as well as  from your local i.e  same name and type , extn? Also , are you able to upload in both ways and you can see the file node in crxde like below when uploaded from local system?

Is it a custom component that you are using to render image or core component? When you use image from Dam - its reference is stored in the property called fileReference but if you browse and drop image from local system - it creates a file node with binary.   If custom component , you can refer tea...

@Vani1012  : can you just try and search for the other image which is missing by its name - is it showing up?You can try to run Dam update workflow on it and try again. Is it in a processed state , can you try and upload it again ? 

Asset will use metadata schema applied on the folder or its parent folder where it is present. All assets in a folder will have the same schema. You can check schema applied on folder using folder properties as mentioned in my above post.

OOTB Rollout won't trigger translation on its own , you'll have to write a custom rollout to trigger asset translation post-rollout. Like it does for XF's .

@Vani1012  : Check on two things : a)same metadata schema with same set of fields etc exists on both env. Check here :  http://<server:port>/mnt/overlay/dam/gui/content/metadataschemaeditor/schemalist.html?formPath=/conf/global/settings/dam/adminui-extension/metadataschema   b)same metadata schema h...