Introducing Custom Item Templates

What is a Custom Item Template?

A custom item template in the Aristotle Metadata Registry enables registry users to tailor the appearance of metadata records to their specific requirements. It empowers users to create new records with a distinct layout or structure by selecting and using a custom template created by a registry administrator.

Why Custom Item Template?

Custom item templates provide Aristotle Metadata Registry users with flexibility and customisation options when creating metadata records. They enable users to customise the appearance of metadata records to meet the specific requirements of their organisation or project. With custom item templates, registry administrators can define the layout, fields, and other attributes of metadata records, ensuring consistency and efficiency in data management practices.

Custom Item Templates in the Aristotle Metadata Registry
The Aristotle Metadata Registry administrator can create or edit Custom Item Templates by accessing the ‘Administrator Tools’. Below is an example of the page for creating a new item template:

You can create as many templates as you’d like for the metadata records of your choice. Below is an example of how the metadata record will appear using the template created above.

How are Custom Item Templates Helpful?

  1. Tailored Appearance: Custom item templates enable users to create metadata records with a layout and structure that best suit their needs, improving the overall usability and accessibility of the information.
  2. Consistency: By defining standardised templates for metadata records, custom item templates ensure consistency across records created by different users or within different projects. This consistency enhances the quality and reliability of metadata within the Aristotle Metadata Registry.
  3. Efficiency: Custom item templates streamline the process of creating metadata records by predefining fields, layout, and other attributes. This saves time and effort for users, allowing them to focus on content creation rather than formatting.
  4. Organisation: Custom item templates facilitate organisation and categorisation of metadata records by providing options to define metadata types and attributes specific to different projects or data domains.
  5. User Satisfaction: Custom item templates empower users to customise metadata records according to their unique requirements, promoting user satisfaction and engagement with the metadata management system.

How to Get Started
We’ve got you covered with comprehensive guidance on implementing the Custom Item Template . Our dedicated help page on ‘Custom Item Templates’ will guide you through the process, ensuring a smooth and successful setup. Additionally, there’s a video demonstrating the steps involved in creating a custom item template on Aristotle Metadata You Tube channel. Here’s the link: If you have any questions or need further assistance, please get in touch with us via email at

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.

1 Like

I’ve used the custom item templates to create one for our indicators as a test/sample. So far it has been well received, however we have noticed a couple of missing components/fields in the template creator:

  • Outcome area
  • Quality statement
  • Framework Dimensions
  • Numerator/Denominator/Disaggregator (only the ‘description’ fields for these are available, not the fields that show the links to data elements)

Also, the option to make content collapsible is very useful, but it would be helpful if there was also the option to set fields/containers to collapsed by default.


Thanks for your feedback.
We are looking at this as a priority and will get back to you with an update as soon as possible.

Hi @A_Gore

I have an update for you. As part of the initial release for the custom item template, only the dataset was ready with all the metadata attributes. Our development team is working on getting all other metadata types ready as well for it’s next version release. I will keep you informed once it’s done and released.

Regarding the collapsible option for containers and fields, in their settings, you need to check the ‘Include Header’ checkbox first to be able to see the ‘Content Collapsible’ option for containers and fields.


Hi @A_Gore

The missing components/fields for the indicator have been added to the custom item template creator.

Once again thanks for your feedback!


Thanks Shikha. I’ve checked & those fields are now in available to add to the editor fields.
However, they aren’t yet appearing in the dropdown selection in the template.

I have another thought/request (though I understand it this is a bit tricker):
We can currently control the visibility of custom fields - limiting visibility of fields in public items to internal users (Workgroup, Stewardship Org, Authenticated, etc).

Would it be possible to add this feature to ‘containers’ in the template?

Giving us the option to hide multiple fields & restrict visibility to internal users this way?

Some metadata attributes are complicated to render, so we have added them to widgets. In the ‘View Template’, create a widget, and you will see the mentioned attributes in its dropdown selection.

We can do that. I have added the task to our Roadmap.

However, please note that when visibility options are added to containers, if a user changes the custom view to the default Aristotle View from the item page, the fields in the containers will be visible on the Aristotle default view, unless they are custom fields with selected visibility settings.

This will restrict visibility if it’s a custom item template view and users don’t change it to the Aristotle default view.

Let me know if that works for you, or if you have any further questions or suggestions.


Thanks Shikha, that would be great.

That absolutely works for us. The main push for this feature, is we want to avoid duplication of indicators (e.g. having to create internal AND external) & simply capture everything in one item, with certain information only visible to staff who are logged in.

Thanks Again!

1 Like