writing advanced PDF metadata (Copyright, for example)?

[naglists]

Hiya,

Has anyone had any success populating the advanced metadata (document
properties) in PDFs?

I am able to set:
Title
Author
Subject
Keywords

I can't set:
Author Title
Description Writer
Copyright Status
Copyright Notice
Copyright Info URL

I'm mostly interested in the last three.

(If you search the archives for atidmd you will probably see a discussion
in which Susanne shared part of her book that relates to this, but like the
PTC documentation, those advanced properties are not addressed.)

I don't know what the correct Key names are for them. They don't work
as-is. Removing the space or replacing it with an underscore doesn't work.
Replacing it with %20 crashes the formatting engine (whee haw!).

--
Paul Nagai

[GarethOakes]

I think current APP releases are able to set these via the XMP metadata feature. I assume you're on FOSI though. The easiest way might be via post-process of the PDF? A basic PDF tool such as PDFBox should do the job.

// Gareth Oakes
// Chief Architect, GPSL
// www.gpsl.co

[naglists]

Hi Clay,
Thanks for the info. That is (more or less) the FOSI coding I tested. And,
you're right. Those values show up on the Custom Properties tab. I didn't
think to look there.

I'm not sure the authors / legal folks will be OK with copyright info
buried in the Custom properties tab, though. I'd like the ability to update
the Additional Metadata dialog. (Choose File > Properties > Description tab
> Additional Metadata button.) That dialog has three fields dedicated to
copyright data:
Copyright Status (a drop down supporting Unknown, Copyrighted, Public
Domain)
Copyright Notice (a text area)
Copyright Info URL (a text field)

And I'm viewing in Adobe Reader X (10.1.0).

Probably time for a case to see if support knows how (or can confirm it
isn't possible).

[naglists]

Ah ... I have Adobe Reader X *Pro*. Sorry. Forgot the Pro part. But that
raises a good point. We'll need to be aware that what displays will be
dependent on reader technology. (I love those matrices. NOT!)


On Wed, Jul 30, 2014 at 10:37 AM, Clay Helberg <chelberg@terraxml.com>
wrote:

> Paul--
>
>
>
> Are you sure you're using Adobe Reader X to see that Additional Metadata
> dialog? What you describe matches what I see in PDFXchange, but in Adobe
> Reader X (10.1.1), I don't see an "Additional Metadata" button:
>
>
>
>
>
> Anyway, if you find out a way to do what you are after with FOSI, I hope
> you'll post the solution so we can all see how it works. I agree that this
> is something that could use better documentation, both on the Arbortext
> side and on the Adobe side.
>
>
>
> --Clay
>
>
>
> *From:* Paul Nagai [
>
> <atidmd:docview mode="bookmarks" fit="fitPage" destination="">
>
> </atidmd:docview>
>
> </atidmd:documentmetadata>!' placemnt="before"></usetext>
>
> <usetext<br/>>
> source="!<atidmd:documentmetadata>
>
> <atidmd:docinfo>
>
> <atidmd:entry>
>
> <atidmd:key>Title</atidmd:key><atidmd:value>Moby
> Dick</atidmd:...













">http://www.copyright.com</atidmd:value>
>
> </atidmd:entry>
>
> <atidmd:entry>
>
> <atidmd:key>Copyright
> Status</atidmd:key><atidmd:value>Copyrighted</atidmd:value>
>
> </atidmd:entry>
>
> </atidmd:docinfo>
>
> </atidmd:documentmetadata>!" placemnt="after"></usetext>
>
>
>
> But, if you are using PDFXchange, it will not report non-standard metadata
> fields, unless they are defined in the XMP format that Gareth mentioned.
> So, to set the copyright fields (and have PDFXchange map them correctly),
> you would need something like this inserted into your PDF stream:
>
>
>
> <<
>
> /Type /Metadata
>
> /Length 3336
>
> /Subtype /XML
>
> >>
>
> stream
>
> >¿" id="W5M0MpCehiHzreSzNTczkc9d"?>
>
> <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="XMP" core=" 4.1.1&quot;=">
>
> <rdf:rdf xmlns:rdf="&lt;br"/>>
>
> <rdf:description rdf:about=""&lt;br"/>>
>
> xmlns:xapRights="
>
>
> <xaprights:marked>True</xaprights:marked>
>
> <xaprights:webstatement>
> ">http://www.manualcopyright.com</xaprights:webstatement>
>
> </rdf:description>
>
> </rdf:rdf>
>
> </x:xmpmeta>
>
>
>
> You would probably also need this kind of format if you are trying to
> enable any automatic processing of copyright status.
>
>
>
> I don't know if FOSI can produce XMP metadata, in fact I'd be surprised if
> it can. But maybe Susan or Trudy knows some secret FOSI sauce to make that
> work.
>
>
>
> --Clay
>
>
>
> *From:* Paul Nagai [

[naglists]

PTC confirms that Arbortext doesn't currently support writing XMP metadata
to PDF output by Editor or PE. I submitted a feature request (technically,
a Product Idea) here:

>>
>>
>>
>>
>>
>> Anyway, if you find out a way to do what you are after with FOSI, I hope
>> you'll post the solution so we can all see how it works. I agree that this
>> is something that could use better documentation, both on the Arbortext
>> side and on the Adobe side.
>>
>>
>>
>> --Clay
>>
>>
>>
>> *From:* Pa...
>>
>> <atidmd:docview mode="bookmarks" fit="fitPage" destination="">
>>
>> </atidmd:docview>
>>
>> </atidmd:documentmetadata>!' placemnt="before"></usetext>
>>
>> <usetext<br/>>>
>> source="!<atidmd:documentmetadata>
>>
>> <atidmd:docinfo>
>>
>> <atidmd:entry>
>>
>> <atidmd:key>Title</atidmd:key><atidmd:value>Mob...














">http://www.copyright.com</atidmd:value>
>>
>> </atidmd:entry>
>>
>> <atidmd:entry>
>>
>> <atidmd:key>Copyright
>> Status</atidmd:key><atidmd:value>Copyrighted</atidmd:value>
>>
>> </atidmd:entry>
>>
>> </atidmd:docinfo>
>>
>> </atidmd:documentmetadata>!" placemnt="after"></usetext>
>>
>>
>>
>> But, if you are using PDFXchange, it will not report non-standard
>> metadata fields, unless they are defined in the XMP format that Gareth
>> mentioned. So, to set the copyright fields (and have PDFXchange map them
>> correctly), you would need something like this inserted into your PDF
>> stream:
>>
>>
>>
>> <<
>>
>> /Type /Metadata
>>
>> /Length 3336
>>
>> /Subtype /XML
>>
>> >>
>>
>> stream
>>
>> >¿" id="W5M0MpCehiHzreSzNTczkc9d"?>
>>
>> <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="XMP" core=" 4.1.1&quot;=">
>>
>> <rdf:rdf xmlns:rdf="&lt;br"/>>>
>>
>> <rdf:description rdf:about=""&lt;br"/>>>
>>
>> xmlns:xapRights="
>>
>>
>> <xaprights:marked>True</xaprights:marked>
>>
>> <xaprights:webstatement>
>> ">http://www.manualcopyright.com</xaprights:webstatement>
>>
>> </rdf:description>
>>
>> </rdf:rdf>
>>
>> </x:xmpmeta>
>>
>>
>>
>> You would probably also need this kind of format if you are trying to
>> enable any automatic processing of copyright status.
>>
>>
>>
>> I don't know if FOSI can produce XMP metadata, in fact I'd be surprised
>> if it can. But maybe Susan or Trudy knows some secret FOSI sauce to make
>> that work.
>>
>>
>>
>> --Clay
>>
>>
>>
>> *From:* Paul Nagai [