Both Ocean .oet and Better native.json have a templateName/ TemplateId field , distinct from the root archetype name, whixch allows for a long form version of the template name e.g. 'One London - Living arrangements' vs. 'Living arrangements' as the toot archetype node name. This can be very helpful for templates as it os not uncommon to have multiple templates with the same root archetype name. It may occasionally also be useful when specialising localised archetypes.
This is only required for tooling. In AOM/ADL2 the specialised archetypeId should remain the technical name that is carried in the LOCATABLE/archetyped_details/template_id
Activity
Show:
Pinned fields
Click on the next to a field label to start pinning.
Both Ocean .oet and Better native.json have a templateName/ TemplateId field , distinct from the root archetype name, whixch allows for a long form version of the template name e.g. 'One London - Living arrangements' vs. 'Living arrangements' as the toot archetype node name. This can be very helpful for templates as it os not uncommon to have multiple templates with the same root archetype name. It may occasionally also be useful when specialising localised archetypes. This is only required for tooling. In AOM/ADL2 the specialised archetypeId should remain the technical name that is carried in the LOCATABLE/archetyped_details/template_id