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.

Travis Repetto
Parents

  • Schema names in the list view are helpful for us because many times our folders contain components which are all related and component linked to each other, often with similar names and each belonging to a different schema. Currently we would need to name each component based on it's schema.

    Example: (Parent folder = something)

    something-container

    something-hello-text

    something-goodbye-text

    something-config

    something-home-link

    something-detail-link

    something-hello-image

    something-goodbye-image

    Now imagine that I didn't add the -container, -text, -config, -link, and -image to the component names, and that's what we're looking at now. We could add the component schema name to the component names manually in this way but naming components based on their schema seems like a unnecessary extra step when that information already exists, and doesn't allow for the same filtering and sorting that a new column allows for.

    We will be programmatically importing tens of thousands of components from legacy systems into our SDL Web instance and although we could add the schema name to the component name on import, that seems like the wrong thing to do. Content producers creating content manually will have to follow the same process if they want to keep things consistent.

    The legacy systems we're importing from display the content types (schema) in their list views and our users expect it from SDL Web. From our experience across multiple CMS's, it's been a standard feature.

Comment

  • Schema names in the list view are helpful for us because many times our folders contain components which are all related and component linked to each other, often with similar names and each belonging to a different schema. Currently we would need to name each component based on it's schema.

    Example: (Parent folder = something)

    something-container

    something-hello-text

    something-goodbye-text

    something-config

    something-home-link

    something-detail-link

    something-hello-image

    something-goodbye-image

    Now imagine that I didn't add the -container, -text, -config, -link, and -image to the component names, and that's what we're looking at now. We could add the component schema name to the component names manually in this way but naming components based on their schema seems like a unnecessary extra step when that information already exists, and doesn't allow for the same filtering and sorting that a new column allows for.

    We will be programmatically importing tens of thousands of components from legacy systems into our SDL Web instance and although we could add the schema name to the component name on import, that seems like the wrong thing to do. Content producers creating content manually will have to follow the same process if they want to keep things consistent.

    The legacy systems we're importing from display the content types (schema) in their list views and our users expect it from SDL Web. From our experience across multiple CMS's, it's been a standard feature.

Children
No Data