Review Data Dictionary

One of the more common sources of failed imports are incorrectly deployed custom content models, or incorrectly referenced types, aspects or properties in a shadow metadata file. These errors are fatal, and will terminate the bulk import.

Example Exceptions

org.alfresco.service.namespace.NamespaceException: Namespace prefix [prefix used in a shadow metadata file] is not mapped to a namespace URI

Data Dictionary Web Script

Both of these issues can be troubleshot via the Data Dictionary Web Script that's included with the tool. This Web Script displays a simple HTML representation of the entire Data Dictionary (i.e. content models) deployed to the running Alfresco server - if a custom content model isn't visible on that page it has not been deployed correctly.

The Data Dictionary Web Script is an HTTP GET Web Script located at service path /bulk/import/datadictionary. If you have a default local install of Alfresco, this equates to: http://localhost:8080/alfresco/s/bulk/import/datadictionary

This Web Script has no parameters or options, and can generate quite a substantial amount of output. The easiest way to use it is to use your browser's built-in search function to look for the type, aspect or property that's causing issues in your import. If you can't find it, it is not known to Alfresco, and either the model containing that element has not been deployed correctly, or there's a typo in the name in the shadow metadata file.

---

Back to usage.