How to create custom metadata tag for CQ - metadata

I am trying to create a custom metadata tag for all JPEG images. Following the documentation this is what I did in /apps
However, when I upload a new JPEG file I don't see the tag I've added (Atest)
Am I missing something? I copied /libs/dam/content to /apps/dam/content and just kept the assetededitors folder and I modified the formitems under the image/jpeg folder as shown in the screenshot.

The asseteditors node allows you to change the classic DAM metadata editor, available under the /damadmin. The screenshot attached in the comment presents new touch UI which can be enhanced using Javascript as in this article.

Related

How to add custom metadata value to an image such that it retains while the image is downloaded and extracted on the next upload of the image in AEM?

In order to add a custom metadata field inside Adobe Experience Manager, you can create any new custom metadata field in the metadata schema but that gets associated with the image only internal to the tool.
My requirement is to add custom metadata fields to an image such that on the download of the same, the custom metadata added is also associated with image and on extraction of metadata the value for those fields are intact with the image.
Any ideas to do it in AEM tool or to do it with Java would be of utmost help. Thanks!

TinyMCE 5 - Is there a way to accept only uploaded Image, using the "image" plugin?

I want to allow uploaded images only, not images linked from external websites. Is there a way to only display the "Upload" section of the "image" plugin/dialog?
The image plugin does not have a built in configuration option to do what you want. As TinyMCE is released under an open source license you could certainly modify the code of that plugin to get your desired outcome.

how to include aem custom dam asset handler in a workflow

i followed the custom dam handler blog and was able to achieve what was mentioned in that. My requirement is that i need to get thumbnails created for Doc and Xls files when any dam asset is uploaded. I have gone through the DAM UPDATE ASSET workflow and the steps in that just work fine for TXT, IMAGES and PDF files.
i have tried adding application/vnd.ms-excel and application/msword MIME types but didnt work. May i know what i am missing and where i am missing ? in custom handler what code do i need to write to get thumbnails to be created ?
thanks,
Tarun Singh

Save image with Tinymce

I implemented Tinymce on a website and it's being used as a content editor by the owner of the website (the content is saved in a .txt file). I would like to know if it is possible to save an image uploaded in the tinymce editor into a specific folder on the server.
Thanks!
You'll be able to choose a specific location for image uploading using the images_upload_url property. You can read more on that and our Image Uploading API here: https://www.tinymce.com/docs/configure/file-image-upload/

Add custom metadata fields for DAM assets in a particular folder

I created custom metadata fields for DAM Assets in CQ 5.6.1 using the steps detailed here. However, as described in the document, these changed fields are available for ALL assets in the DAM.
I need these metadata fields to be made available to only a specific folder, say /content/dam/foo instead of every asset.
How can I achieve this?
In my knowledge, there is no straight forward way to achieve this but there is one trick to handle this.
AEM DAM has the notion of meta schema editors. These editors are tied to asset file type, meaning - jpeg, mov, etc. For an asset MIME type, you can define the meta data and its associated form.
AEM 6.0 provides choral UI interface to achieve this --
http://localhost:4502/libs/dam/gui/content/metadataschemaeditor/schemalist.html/dam/content/schemaeditors/forms
Am not aware of any such interface in AEM 5.6.1. The nodes tied to this are at /libs/dam/content/asseteditors/image/jpeg/formitems. You could overlay them at /apps to add the required metadata.
Coming to the question, the trick is to add the file type into your dam content hierarchy. Example - /content/dam/jpeg/foo, /content/dam/png/foo, etc. This way, you would get different metadata for different folders of the dam.
Adobe recommends this approach as AEM 6.0 introduced the concept of processing profiles which you could attach to folders. This way, your different file types could get different treatments.