Expand my Community achievements bar.

SOLVED

I would like to standardize asset schemas

Avatar

Level 3

We have developed a custom metadata schema in AEM Assets. I would like to share the AEM Assets schema with Adobe Photoshop or Adobe Bridge so that I can populate the defined schema in the asset properties and have those properties get auto updated when the asset is loaded to AEM Assets.

 

We have some automated processes used to load assets into folders that are not manually maintained by any users. Getting the metadata created and loaded to an asset from the outset would support data standardizations.

 

Some additional insight into this inquiry and potential product request.

  • We have custom metadata schema fields created including "Product type" and "Customer type" fields. These are the custom fields that we would like to include on the native asset so that they are included in the full asset lifecycle. We are using the standard metadata fields like "Title" and "Description" to help support the asset understanding.
  • Our automation is a passing of files from a product MDM tool to AEM that have been uploaded in the MDM solution.
1 Accepted Solution

Avatar

Correct answer by
Level 6

Hi @james-mke ,
could you please elaborate on what you mean with custom metadata schema?
Forgive me please if i now explain away with the stuff you already know
Did you create new properties, or did you just rearranged existing values?

In case you use the standard XMP properties, you should find all your values within every asset.
And if you use the standard values (dc:title, dc:description, prism:expirationDate, etc.) they will populate the file within the aem as well as in the file itself. 
Since i probably not understand it correctly, im not certain... but your request sound like a customisation of the photoshop/bridge/xmp mask instead of something the AEM can provide.
The other thing, you have an automated process that sorts your files into folders depending of ... how many stars an asset has / Which initial the title uses / which year the file was produced at? You see this is where i loose you. How is sorting files into folders creates metadata for you? 
I am interested to learn more about this if you would like to share more.
I also was interested to create a workflow that adds tags and other metadata based of the filename an asset has.
Currently i used a csv export, excel powerquerry adaption, csv import to enrich files based of filename, creation Date, folder path. 

View solution in original post

2 Replies

Avatar

Correct answer by
Level 6

Hi @james-mke ,
could you please elaborate on what you mean with custom metadata schema?
Forgive me please if i now explain away with the stuff you already know
Did you create new properties, or did you just rearranged existing values?

In case you use the standard XMP properties, you should find all your values within every asset.
And if you use the standard values (dc:title, dc:description, prism:expirationDate, etc.) they will populate the file within the aem as well as in the file itself. 
Since i probably not understand it correctly, im not certain... but your request sound like a customisation of the photoshop/bridge/xmp mask instead of something the AEM can provide.
The other thing, you have an automated process that sorts your files into folders depending of ... how many stars an asset has / Which initial the title uses / which year the file was produced at? You see this is where i loose you. How is sorting files into folders creates metadata for you? 
I am interested to learn more about this if you would like to share more.
I also was interested to create a workflow that adds tags and other metadata based of the filename an asset has.
Currently i used a csv export, excel powerquerry adaption, csv import to enrich files based of filename, creation Date, folder path.