Metadata Schema issue in Admin View vs Assets View

[gagandeepsaluja]

We have observed that in Admin View if a Metadata Schema is created and applied to a folder , those changes doesn't reflect in Asset View under Metadata Forms or on the asset properties. Vice a versa behavior is there when the Metadata Forms are created in Asset View. This will create confusion for the end user as they would see a diff. set of properties in both Admin view and Assets view. Also this would be a problem w.r.t manageability of these. 

Also if the Librarian has applied a metadata schema in AEM to a folder and when an author has uploaded an Asset in Assets View then the required properties might get missed as well.

Any thoughts by anyone on the above issue?

[digarg · Accepted solution]

As of today, you will need to build two separate schemas for both views.

Decide on your persona , which persona or user groups should be using which view.Today there is no restriction on using any of the views.All users can go into  both views but guidelines should be to use a consistent view 

Read only users should be instructed to use 'Assets view' , so you can hide any admin /sensitive metadata properties from assets view.

Keep metadata schema fields limited in assets view as it's mostly for intuitive and quick easy browsing view .For detailed metadata use admin view.

Mostly admin users should primarily be using the admin view.

You are right from manageability perspective as we have to manage at two places.

[hervea48749446]

If it is working by designed, then it is BAD design and it is INCONSISTENT with other features/settings shared between Assets View and Admin Views. Everything I read about the 2 views is that Asset View is simply a lightweight experience intended for Lightweight DAM users

• Admin View: The existing Assets as a Cloud Service user interface. Use the Admin View for all advanced Digital Asset Management capabilities including integrations, workflows, content automation, publishing and more.
• Assets View: Adobe’s lightweight asset management experience to store, manage, discover, and use digital assets. Streamlined user interface containing essential Digital Asset Management capabilities. Designed for the light-weight DAM users with a focus on upload, metadata management, search, download, and sharing.

This leads everyone to believe and understand that configuration done in Admin View by Administrator is reflected in the Asset View to be leveraged by the "basic" DAM users

In fact, folders, files, taxonomy are shared. If taxonomy is shared, why would metadata schemas be treated differently.

IMHO, you can provide admin a way to hide some metadata for users in Asset View if you want to keep the experience simpler but still allow to manage metadata schemas in one place

I strongly believe this is just an oversight and not a conscious design decision. If not, then it is a bad design decision

[mktackabery]

This reveals a fundamental misunderstanding by Adobe about what taxonomy and metadata truly are.

Taxonomy in AEM = folder structure, which, I guess, is why the folders are the same in both Admin View and Assets View.

Metadata are elements that are embedded into assets and should not change regardless of view. Instead, "Admin View" treats metadata correctly, sort of, and Assets View treats metadata as tags. Metadata elements are not tags.

The AEM Assets product continues to shrink to a lightweight product for web delivery, not a digital asset management tool.