Content models describe how data should be stored in the repository and the metadata that can be associated to the content and folders within that model.

Each model is identified by a unique namespace, prefix and name, and made up of custom types, aspects, properties and constraints.

Properties

The properties of a content model are:

Create a content model

Content models can be global in scope, so they are available to import into multiple projects or they can be created at an individual project level.

Create a global content model

To create a global content model:

1. Sign into the Modeling Application and click on Content Models.

2. Click the NEW dropdown.

3. Select Content Model and enter a name and optional description.

To use a global content model within a specific project:

1. Sign into the Modeling Application and open a project.

2. Click the NEW dropdown.

3. Select Import > Content Model and choose the model to import.

Create a content model in a project

To create a content model in a project:

1. Sign into the Modeling Application and open a project.

2. Click the NEW dropdown.

3. Select how to create the content model:

   • Create > Content Model creates a new, empty form.

   • Upload > Content Model allows for uploading an existing content model .xml file into the Modeling Application.

   Alternatively use the + or Upload buttons next to Content Models in the left-hand menu.

4. Enter a name and optional description.

Content model modeling

Content models are created within a project and are exclusive to that project unless the content model scope is changed to global. Once a content model is global it will appear at the same level as projects in the modeling application and can be imported into other projects.

Use the Turn global option under actions when a content model is selected to change the scope to global.

Note: It is not possible to change the scope back to a single project once the Turn global option has been used. The content model will need to be removed from the project and either recreated, or reimported.

Custom types

Custom types set the properties and relationships that a file of that type can support. Custom types can inherit the properties of a parent type. Content and Folder are two example types that are already defined in Alfresco Content Services.

The properties of a custom type are:

Custom types are stored as JSON, for example:

Code copied to clipboard.
{
  "parentName": "cm:content",
  "name": "supplier-invoice",
  "prefixedName": "finance:supplier-invoice",
  "description": "An invoice received from a supplier.",
  "title": "Supplier Invoice",
  "properties": []
}

Aspects

Aspects are a collection of properties that can be used to describe data and behavior. A file must be of one type, however it can have multiple aspects attached to it. Classifiable and Versionable are two example aspects that are already defined in Alfresco Content Services.

The properties of an aspect are:

Aspects are stored as JSON, for example:

Code copied to clipboard.
{
  "name": "isArchivable",
  "prefixedName": "finance:isArchivable",
  "description": "The status of the document for archiving purposes.",
  "title": "Archivable",
  "properties": []
}

Properties

Properties are the metadata that describe content. Author is an example property that is already defined in Alfresco Content Services used for specifying who wrote the content.

Properties can be assigned to a custom type or an aspect. Select which type or aspect to create the property under before creating it.

The properties of properties are:

The options for data types of properties are:

The options for constraints of properties are:

The index options of properties are:

Properties are stored as JSON, for example:

Code copied to clipboard.
{
  "name": "datePaid",
  "prefixedName": "finance:datePaid",
  "title": "Date Paid",
  "description": "The date the invoice was paid.",
  "dataType": "d:date",
  "facetable": "UNSET",
  "indexTokenisationMode": "TRUE",
  "multiValued": false,
  "mandatoryEnforced": false,
  "mandatory": false,
  "indexed": true
}

Actions

The actions that can be run against a content model are: