Skip to main content

Custom metadata templates: what to decide before you click Save

  • Nov 17, 2026 7:50 AM UTC
  • 0 replies
  • 0 views
  • Translate All

josephinerohner
Community Manager
Forum|alt.badge.img+2

Hi everyone 👋

Custom metadata templates let you describe your assets with the fields your organization needs. Several settings are locked once a template is saved, so a few decisions made up front save a lot of rework later. Here is what to check.

1. Pick the right tab

Use the Basic tab if portal users must see the metadata. Use the Admin tab if the metadata is for internal use only: it shows in the back office and in catalog management tools such as the Dataset connector, but never in the portal. The Interoperability tab (DCAT, INSPIRE) holds system templates, so you can’t create a custom template there.

 

2. Settle these choices before you save

  • Template identifier. The API uses it, and you can’t change it after creation.
  • Field identifiers. They are generated from the field name and are also fixed after creation.
  • Field type. Text, Single-Select, Date, Boolean and the others can’t be changed later.
  • Translations. Once the template is saved, you can’t turn translation on or off for its existing fields.

 

3. Use the Catalog filter option

Turn it on for a field, then add the filter in Catalog > Settings on the catalog page. The field then works as a filter in the catalog and in the Explore API.

 

4. Check the impact before you change a template in use

  • If you make a field mandatory, contributors can’t publish an asset until it’s filled in. Automatic updates of published assets, scheduled or from a form, fail until the field has a value.
  • If you delete a template or a field, its metadata is permanently lost.
  • If you deactivate a template, its metadata is hidden everywhere but kept. Reactivating it shows the metadata again. To retire a template, deactivate it.

The full step-by-step procedure is in the user guide:  Creating and editing metadata templates.

 

What custom fields have you added to your templates, and which ones do your portal users actually filter on? 💬