Running your sample code we get the following:
PART 1.
Name: RE_ Bend aeration basins(5).pdf
Description: “Griffiths, Jim/CVO” 5/3/2011 RE_ Bend aeration basins(5).pdf
Mime Type: application/pdf
PART 2.
Author: null
Producer: Adobe PDF Library 15.0
Creation Date: 4/1/17 4:25 PM
Keywords: null
Modify Date: 4/1/17 4:25 PM
Subject: null
Title: null
PART 2. is metadata associated to the PDF attachment, which is different from the
metadata in the portfolio PDF, so this does not help us in this particular case
PART 1. is metadata associated to the file in the portfolio PDF, but does not include all the
information we are trying to extract. For reference we are trying to migrate from another PDF
library which provides the metadata in the portfolio as a dictionary with a set of arbitrary
keys and value. and for example provides for the file attached to this portfolio PDF a dictionary
with the following 7 entries:
Folder Location: Archive Folders/old projects/Old Projects/Bend
Date: 5/3/2011
From: Griffiths, Jim/CVO
Guid: 000000002076ACD34AFEF2458D464E15938F9BE4849D2400
Subject: RE_ Bend aeration basins(5).pdf
To: Menniti, Adrienne/PDX, Griffiths, Jim/CVO, Burton, Kevin/BEL, Brown, Gene/CVO
Cc: Elkins, Lori/CVO, Rose, Sterling/CVO, Leaf, William/BOI
So the FileSpecification.Description field that Aspose PDF returns, collapses 3 of these fields
(From Date and Subject) into a single one. We have to process arbitrary PDFs which might
have different metadata fields, so this API makes it hard even to retrieve 3 of the 7 fields we’d need.