Using Custom Content Models in Property Mappings for PDF Metadata Extraction - Using Custom Content Models in Property Mappings for PDF Metadata Extraction - Alfresco - Alfresco Content Services - Alfresco/Alfresco-Content-Services/23.4/Alfresco-Content-Services/Develop/In-Process-Platform-Extension-Points/Metadata-Extractors-and-Embedders/Using-Custom-Content-Models-in-Property-Mappings-for-PDF-Metadata-Extraction - 23.4 - 23.4

Alfresco Content Services

Platform
Alfresco
Product
Alfresco Content Services
Release
23.4
License
ft:lastPublication
2026-04-22T22:35:19.567073
ft:locale
en-US

Next requirement is most likely to map properties to custom content models. There is an ACME content model tutorial where the base document type has an acme:documentId property. You might want to add a document identifier to the PDFs you are uploading and have it automatically set in the ACME content model. Start by updating the the PdfBoxMetadataExtractor_metadata_extract.properties configuration as follows:

#
# PdfBoxMetadataExtracter - custom mapping
#

# Namespaces
namespace.prefix.cm=http://www.alfresco.org/model/content/1.0
namespace.prefix.acme=http://www.acme.org/model/content/1.0

# Mappings
author=cm:author
title=cm:title
DocumentId=acme:documentId

Here the custom document property DocumentId has been added so it is mapped to the ACME content model property acme:documentId. When doing this you also need to define the new custom namespace acme. For this to work you need to have a rule on the folder that applies the acme:document type to any PDF document uploaded to the folder. This type has the acme:docuementId property.