Hello @akhilraj
To push your Campus metadata into a PDF’s properties and use it for segmentation:
1. Create a proper DAM metadata field for Campus
In Tools → Assets → Metadata Schemas, add a field to the PDF schema and map it to a JCR metadata property, for example:
./jcr:content/metadata/dc:subject (reuses Dublin Core “Subject”)
or
./jcr:content/metadata/campus:campus (custom namespace)
This makes Campus a first-class AEM metadata property you can search/filter on.
2. Enable XMP writeback so it is embedded in the PDF
Use/enable the DAM Metadata Writeback workflow or launcher so metadata under ./jcr:content/metadata is written into the PDF’s XMP :
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/admin/xmp...
3. Use AEM metadata for segmentation, not the PDF UI
- Segment PDFs by Campus using AEM search facets, filters, or reports against that JCR property.
- The fact that Campus is also in the PDF binary is mainly for external systems; AEM’s segmentation should rely on the repository metadata.
So :
AEM metadata field => JCR under metadata => XMP writeback => AEM-based segmentation.