Creating a content model - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

This is the Spring Bean configuration file for your new content model:

<beanid="aio52-platform-jar.dictionaryBootstrap"parent="dictionaryModelBootstrap"depends-on="dictionaryBootstrap">
  <property name="models">
    <list>
        <value>alfresco/module/${project.artifactId}/model/content-model.xml</value>
        <value>alfresco/module/${project.artifactId}/model/workflow-model.xml</value>
    </list>
  </property>
  <property name="labels">
    <list>
       <!-- Bootstrap Resource Bundles for the content model types, aspects, properties etc -->
       <value>alfresco/module/${project.artifactId}/messages/content-model</value>
    </list>
  </property>
</bean>

This Spring bean links to your model file. It causes the model to extend the existing model, rather than replace it. The bean definition indicates that this model is to use a bootstrap deployment, which will require a server restart in order to take effect.

This is your new custom model. Replace the contents with the following text:

<?xml version="1.0" encoding="UTF-8"?>
    
<!-- Definition of new Model -->
    
<!-- The important part here is the name - Note: the use of the my: namespace
     which is defined further on in the document -->
<model name="my:contentModel" xmlns="http://www.alfresco.org/model/dictionary/1.0">
    
   <!-- Optional meta-data about the model -->   
   <description>Example Custom Model</description>
   <author>Alfresco Documentation Team</author>
   <version>1.0</version>
    
   <!-- Imports are required to allow references to definitions in other models -->   
   <imports>
      <!-- Import Alfresco Dictionary Definitions -->
      <import uri="http://www.alfresco.org/model/dictionary/1.0" prefix="d"/>
      <!-- Import Alfresco Content Domain Model Definitions -->
      <import uri="http://www.alfresco.org/model/content/1.0" prefix="cm"/>
   </imports>
    
   <!-- Introduction of new namespaces defined by this model -->
   <!-- NOTE: The following namespace my.new.model should be changed to reflect your own namespace -->
   <namespaces>
      <namespace uri="http://www.mycompany.com/model/content/1.0" prefix="my"/>
   </namespaces>
       
   <types>
    <!--  Enterprise-wide generic document type -->
        <type name="my:doc">
            <title>MyCompany Generic Document</title>
            <parent>cm:content</parent>    
        </type>    
        <type name="my:marketingDoc">
            <title>MyCompany Marketing Document</title>
            <parent>my:doc</parent>    
        </type>    
        <type name="my:whitepaper">
            <title>MyCompany Whitepaper</title>
            <parent>my:marketingDoc</parent>    
        </type>         
   </types>
</model>  

This is the custom model that will extend the existing core model framework. The model adds three new types of document, a generic company document, a marketing document, and a whitepaper.