Import Strategy - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

There are several import strategies that can be used to import module data.

If you know the UUID(s) of the spaces/files you are importing, you can choose from a number of import strategies.

If you are using XML, you will have to manually add a sys:node-uuid tag to that node. (Generated ACP files automatically contain the UUIDs.)

Example:

    <view:properties>
        <sys:node-uuid>b7c6b88a-e5fd-4ccf-b134-69a2460c3b89</sys:node-uuid>
        ...
    </view:properties>
</cm:content>
</cm:contains>
</cm:folder>
</view:view>

You can add the following: CREATE_NEW, CREATE_NEW_WITH_UUID, REMOVE_EXISTING, REPLACE_EXISTING, UPDATE_EXISTING, THROW_ON_COLLISION (org.alfresco.service.cmr.view.ImporterBinding.UUID_BINDING). This can be added globally for entire bean, or per bootstrap view.

Global for the entire bean:

<beanid="myModule.bootstrap"class="org.alfresco.repo.module.ImporterModuleComponent"parent="module.baseComponent">
  <property name="uuidBinding">
    <value>REPLACE_EXISTING</value>
  </property>
  ...

Per BootstrapView:

  <propertyname="bootstrapViews">
    <list>
      <props>
        <prop key="uuidBinding">UPDATE_EXISTING</prop>
        <prop key="path">/${spaces.company_home.childname}/${spaces.dictionary.childname}</prop>
        <prop key="location">alfresco/module/yourmodule/bootstrap/myimport.acp</prop>
      </props>
      ...
    </list>
  </property>
</bean>

Space Names Reference

The following are the substitution tokens that can be used for bootstrapping purposes. These tokens can be redefined in the configuration files if needed.