Expand my Community achievements bar.

Applications for the 2024-2025 Adobe Experience Manager Champion Program are open!
SOLVED

Title property: any docs on ./jcr: vs ./customname?

Avatar

Level 1

Just wondering if anyone can point me to a clear piece of documentation to differentiate between when we would use ./jcr: and when we would use a custom value such as ./customname?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

 

 

The jcr: namespace is used to define system-specific properties and elements in the repository. In AEM, these properties and elements are essential for the proper functioning of the content repository and the management of content-related information. Some common system-specific properties in the jcr: namespace include jcr:primaryType (indicating the primary node type), jcr:mixinTypes (indicating mixin node types), and others.

 

Since, these are have a specific purpose, please avoid using "jcr:" namespace for custom properties.

 

Use custom namespace for custom properties. Namespace primarily helps you organize and manage your metadata. For example, it could help you:

  • Identify custom metadata against OOTB metadata
  • Identify a metadata’s source: when metadata flows-in from from multiple 3rd party systems
    • In such scenario, you could easily identify the source of metadata, by mapping a namespace against the metadata’s scource.
  • Filter what should be written on to an asset binary by Metadata Writeback Workflow. The DAM metadata writeback workflow would only write a metadata that has a namespace.

    https://techrevel.blog/2020/01/23/aem-custom-namespace/

Aanchal Sikka

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

 

 

The jcr: namespace is used to define system-specific properties and elements in the repository. In AEM, these properties and elements are essential for the proper functioning of the content repository and the management of content-related information. Some common system-specific properties in the jcr: namespace include jcr:primaryType (indicating the primary node type), jcr:mixinTypes (indicating mixin node types), and others.

 

Since, these are have a specific purpose, please avoid using "jcr:" namespace for custom properties.

 

Use custom namespace for custom properties. Namespace primarily helps you organize and manage your metadata. For example, it could help you:

  • Identify custom metadata against OOTB metadata
  • Identify a metadata’s source: when metadata flows-in from from multiple 3rd party systems
    • In such scenario, you could easily identify the source of metadata, by mapping a namespace against the metadata’s scource.
  • Filter what should be written on to an asset binary by Metadata Writeback Workflow. The DAM metadata writeback workflow would only write a metadata that has a namespace.

    https://techrevel.blog/2020/01/23/aem-custom-namespace/

Aanchal Sikka