Idea Delivered

This idea has been included in SDL Tridion Sites 9.5.

There will be a possibility to sort and filter on the Schemas in a given list. We have dropped the separate "Type" column as the information is available via the icon and in the information for the item. The item types as well as Schema column can also be used to filter on.

Folders will include the Schema name and Pages will show any default Schema they have set as well.

Add Schema Name Column to the Explorer View

Currently the CME interface has columns for name, type (component, folder, etc), publication, and modified date.

It would be helpful if there was also a way to display what the schema for a component is. This could take the form of a new column.

Or augmentation of an existing column.

This can be done by custom GUI extensions, but it seems like a no-brainer for a native feature.

Parents
  • "Would it be equally valuable to see the Page Schema/Type in the list view?"

    "Alternatively, you can argue that Page Templates acts as Page Types; would it be useful to see the Page Template? Would that be more useful than Page Schema?"

    Based on what I understand about page schemas, I think it is appropriate and consistent that the column shows which schema the current row uses, be that component, page, etc. I am not sure if folder and structure group metadata schemas would also be included in that view, as it may cause confusion since pages can also have a metadata schema (which may be inherited from the new "page schema").

    Page template may be useful for older implementations, but since switching to using DXA, the number of page templates we use has reduced and they are all identical other than the names.

Comment
  • "Would it be equally valuable to see the Page Schema/Type in the list view?"

    "Alternatively, you can argue that Page Templates acts as Page Types; would it be useful to see the Page Template? Would that be more useful than Page Schema?"

    Based on what I understand about page schemas, I think it is appropriate and consistent that the column shows which schema the current row uses, be that component, page, etc. I am not sure if folder and structure group metadata schemas would also be included in that view, as it may cause confusion since pages can also have a metadata schema (which may be inherited from the new "page schema").

    Page template may be useful for older implementations, but since switching to using DXA, the number of page templates we use has reduced and they are all identical other than the names.

Children
No Data