Custom Metadata in Asset View

[David_Fischer92]

We have been using the admin view for a few years now in our organization and we're looking at migrating over to using the assets view for the bulk of our users.  I'm trying to configure the assets view with our search filters and metadata however i'm not seeing any of our custom metadata fields we've created in code in the metadata forms in assets view.  Is there a special way i need to make my custom metadata available in assets view?

[narendiran_ravi]

Hi @David_Fischer92 ,

Please check if this documentation helps -https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/assets-vi... . We can create custom metadata forms similar to schema for assets view. 

[ArchanaS]

Hi @narendiran_ravi , this page is telling us how can I create metadata form using the available metadata property but we need to create metadata property, which I want to use while create metadata forms. From where these Metadata properties are fetched in dropdown ? How can we add new custom properties? 

I want to add  a property in metadata and want that to be visible while creating form.

[shubhanshu_singh · Accepted solution]

Hi @David_Fischer92 @ArchanaS - 

Assets Essentials provides many standard metadata fields by default. Organizations which have additional metadata needs and need more metadata fields to add business-specific metadata can add properties with namespace while configuring the form. There is no specific way to import your existing metadata from Assets Admin View(Touch UI interface you are used to ) to Assets View. You will have to create a new form and manage it by UI.

Refer to the tutorial video mentioned below.
https://experienceleague.adobe.com/en/docs/experience-manager-assets-essentials/help/metadata#metada... 

[kautuk_sahni]

@David_Fischer92 Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!