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?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
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.
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.
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.
Views
Replies
Total Likes