Feature Release: Item Template Sub-Pages

Introducing sub-pages, a new addition to metadata item templates that allows for even further customisation!

What are sub-pages?

A sub-page is a customisable template-within-a-template accessed as an alternate view/page from the item page of a templated metadata item. Sub-pages are created from the editor of a pre-existing metadata item template, which means that they cannot be created at the same time as the rest of the template, but can be added by selecting ‘Edit’ on the appropriate template after its creation.

Once editing an item template, you can find the new sub-pages section at the bottom of the editor. A sub-page can be created by selecting ‘Create New Sub-Page’.

Name the sub-page based on what word(s) you want to be clicking on when switching to its view. This will appear alongside the default, and templated view modes already present for any templated metadata item.

If desired, you can then choose a custom URL slug for the sub-page, and a description for the context of any future editors.

Select who is able to view the sub-page using the ‘Sub-Page Visibility Permission’ dropdown.

Combined with the appropriate registration and custom field settings, this can be used to make certain metadata item information visible only to certain roles (such as registry Administrators), even if the item itself is visible to a wider role group.

If you’d like this sub-page to show the templated item’s infobox, tick the ‘Include Infobox’ checkbox.

Now you can start creating the sub-page! Containers represent a section of the sub-page, and can contain fields, widgets, custom HTML or even more containers! Add as many as you like, selecting the contents of each as desired.

You can then customise each container, field, or widget even more deeply by selecting the appropriate cog icons.

Once satisfied, complete the sub-page by selecting ‘Submit’.

Once you’ve added all of the sub-pages you need (via as many presses of the ‘Create New Sub-Page’ button), be sure to select ‘Save Changes’ in the parent item template’s editor.

Once you’ve created a metadata item using the relevant template, any created sub-pages will now appear as-designed to any user with permission to view them alongside the usual non-templated, and templated view modes.

How do sub-pages benefit users?

Sub-pages were developed as a way for users to present alternate pages, or ‘views’, of a metadata item. They retrieve information from the same metadata item as their parent template, but can be customised to contain totally different fields or be visible to totally different users.

This makes for greatly expanded options and uses of templated metadata items. Some example uses of sub-pages include:

  • Presenting role-specific information about an item that is otherwise visible to the public (e.g. separate sub-pages for public users, Administrators, data collection teams, data access teams, etc.)
  • Separating information that could overcrowd the main item page (e.g. long lists, large graphs, statistics, etc.)
  • Having separate views for technical users and non-technical users.

Your feedback matters

Your feedback is invaluable as we continue to innovate and improve the Aristotle Metadata Registry. We’ve designed this feature with your metadata management needs in mind, and we want to hear from you. Please don’t hesitate to reach out with suggestions, ideas, or questions.

2 Likes

Hi Tagan,

We’re pretty excited about this release! Really glad to see this rolled out!

The only bit of feedback I have is that I believe the first ‘Default View’ tab should be removed.

If we put effort into curating a view for users, it doesn’t make sense to give them an obvious option to deviate from that curated view. We would like information to be read in a specific order, particularly where the user is not an authenticated user (i.e. public viewers).

The previous custom template function didn’t allow public users to see the default view, and I think this feature functionality should be retained.

Internal users with the appropriate permissions will already have the ability to switch to the default view by using the ‘Actions’ button dropdown.

1 Like

Question: Does the “Default View” tab simply show the 1st page of an item (after sub-pages have been added) or does it show the page as it is without the custom template applied?

If it is the former, great; I’m keen to test them with some of our items!
If it is the latter, then I do agree with Sarah’s comments.

Our custom templates have been developed with public (non-internal) users in mind, & giving them an easy way to essentially bypass all that work would certainly be of concern to our governance group, who endorsed our use of custom templates to restrict the visibility of certain details within our items.

I’m looking forward to trying this feature out, but I did want to get some clarity on this particular aspect before diving in!

1 Like

Hey @SarahS and @A_Gore!

So long as an item is not published to a registration state that has public visibility (see here for instructions on adjusting registration states), the item will not be visible to public users.

I was about to say that I love having the default view there :-). As it is much easier to switch back to that view, and for our internal users who aren’t as familiar using Aristotle and wouldn’t know that a default view exists and to check the Actions menu for it. Maybe an option that can be configurable…

1 Like

Interesting! Maybe the difference between approach is partly around having publicly viewable items for non-authorised users :thinking:

For us, we are trying to build templates to include everything that the general user might need to see (with only item editors needing to see the default view). This is particularly because we don’t currently have granular visibility controls for non-custom fields, like we do for the custom fields. At the moment we can either make the entire item public (including all non-custom fields), create duplicates of the non-custom fields (not preferred) or not make the entire item public at all (also not always preferred).

An option to select or unselect the default view (maybe a ‘Show default view’ option) would solve our issue though!