Everything in Alfresco is a node, and every node is described by a content model. The content model is the schema that defines the types of content you store, the aspects (reusable bundles of behaviour and metadata) you attach to them, and the properties - the individual metadata fields - that carry descriptive, administrative and preservation information. Getting the model right is the single most important design decision in any deployment, because it drives search, retention, workflow and interoperability.

Models are defined in XML dictionary files and grouped under namespaces so that custom fields never clash with the out-of-the-box model. A well-designed model maps cleanly onto recognised metadata standards, which is what lets your content travel to other systems and remain intelligible over time.

Types, aspects and properties

  • Types (d:type): the primary classification of a node, e.g. cm:content, cm:folder, or a custom type such as ahg:caseFile. A node has exactly one type.
  • Aspects: cross-cutting mixins added to any node - for example cm:versionable, cm:auditable, or a custom aspect carrying rights metadata. A node can have many aspects.
  • Properties & constraints: typed fields (d:text, d:date, d:int) with constraints such as LIST (controlled vocabulary), REGEX or length, plus associations that link nodes together.

Aligning to metadata standards

Alfresco ships with a Dublin Core aspect, and its model is flexible enough to express richer descriptive standards used across the GLAM sector. Map your properties deliberately to the standard your community expects.

  • Dublin Core for baseline discovery metadata across mixed collections.
  • EAD / ISAD(G) concepts for archival hierarchy and provenance.
  • PREMIS for digital preservation events, fixity and provenance where Alfresco feeds a preservation workflow.
  • Controlled vocabularies enforced via LIST constraints or category hierarchies for consistent indexing.
In practice. Never overload the base cm:content type with dozens of custom fields. Instead, model reusable aspects (e.g. a "rights" aspect, a "retention" aspect) and attach them where needed. This keeps the model modular, avoids sparse metadata, and lets you evolve one concern without breaking others.

Making metadata usable

A property only earns its keep if it can be captured and found. Alfresco binds models to the UI through configuration - property sheets, forms and search fields - and to ingest through metadata extractors that read embedded metadata from files (EXIF, PDF, Office) on upload. Plan capture, display and index together, not as an afterthought.

Key takeaways

  • The content model is a schema of types, aspects and properties, defined in namespaced XML and central to search, retention and workflow.
  • Prefer reusable aspects over bloated types, and enforce controlled vocabularies with constraints for clean, consistent indexing.
  • Map properties to recognised standards - Dublin Core, EAD/ISAD(G), PREMIS - so content stays interoperable and preservation-ready.

Check your understanding

Last modified: Saturday, 1 August 2026, 11:56 AM