Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Metadata in LiveCycle

Avatar

Level 4

Is there a way to set up meta data in LiveCycle that will map over to Adobe?  In the adobe properties there is a "Keyword" section.  Where can get enter the Keywords in LiveCycle to that they will map over to that keyword section in Adobe?

Thanks!

Jodi

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

In the xml you want to add this:

<dc:subject>

            <rdf:Bag>

              <rdf:li>Keywords</rdf:li>

              <rdf:li>keyword 2</rdf:li>

              <rdf:li>keyword 3</rdf:li>

            </rdf:Bag>

</dc:subject>

The meta data in XML is located at the bottom.  Locate the following and add the script.

<rdf:Description xmlns:xmp="http://ns.adobe.com/xap/1.0/" rdf:about="">

        <xmp:CreatorTool>Adobe LiveCycle Designer ES 8.2</xmp:CreatorTool>

        <xmp:ModifyDate>2011-04-04T13:15:27-05:00</xmp:ModifyDate>

        <xmp:CreateDate>2006-03-24T12:09:19-05:00</xmp:CreateDate>

        <xmp:MetadataDate>2011-04-04T18:17:18Z</xmp:MetadataDate>

      </rdf:Description>

      <rdf:Description xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/" rdf:about="">

        <xmpMM:DocumentID>uuid:2b8434e9-051b-4cd4-946d-4a430813611d</xmpMM:DocumentID>

        <xmpMM:InstanceID>uuid:f38d5eb5-91f9-4597-83de-d564cb55505a</xmpMM:InstanceID>

      </rdf:Description>

      <rdf:Description xmlns:dc="http://purl.org/dc/elements/1.1/" rdf:about="">

        <dc:format>application/pdf</dc:format>

        <dc:subject>

            <rdf:Bag>

              <rdf:li>Keywords</rdf:li>

              <rdf:li>keyword 2</rdf:li>

              <rdf:li>keyword 3</rdf:li>

            </rdf:Bag>

        </dc:subject>

Ida Eve.Tracy

View solution in original post

16 Replies

Avatar

Former Community Member

Click on File --> Form Properties

Add meta data to the Info tab.  Anything entered here will carry over to Adobe.

Avatar

Level 4

HI Ida!  Thanks for the info.  the problem is that "keywords" isn't a choice in the info tab.

Hopefully in the next version of LiveCycle it will be

Avatar

Former Community Member

You might have to code it in the xml code along with the encoding. I am testing your issue now on one of the forms I am currently working on and will let you know what I find out.

Eve Tracy

KDA/ IRT

(785) 368-6261

Eve.Tracy@kda.ks.gov

Avatar

Level 10

Hi,

the keywords can be definded manuall in the XML source.

Look for the following segment ...

<rdf:Description xmlns:pdf="http://ns.adobe.com/pdf/1.3/" rdf:about="">

         <pdf:Producer>Adobe LiveCycle Designer ES 9.0</pdf:Producer>

</rdf:Description>

... and insert a tag with your keywords, so it looks like.
<rdf:Description xmlns:pdf="http://ns.adobe.com/pdf/1.3/" rdf:about="">
         <pdf:Producer>Adobe LiveCycle Designer ES 9.0</pdf:Producer>
         <pdf:Keywords>keyword1, keyword2, keyword3,keyword4</pdf:Keywords>
</rdf:Description>

Avatar

Correct answer by
Former Community Member

In the xml you want to add this:

<dc:subject>

            <rdf:Bag>

              <rdf:li>Keywords</rdf:li>

              <rdf:li>keyword 2</rdf:li>

              <rdf:li>keyword 3</rdf:li>

            </rdf:Bag>

</dc:subject>

The meta data in XML is located at the bottom.  Locate the following and add the script.

<rdf:Description xmlns:xmp="http://ns.adobe.com/xap/1.0/" rdf:about="">

        <xmp:CreatorTool>Adobe LiveCycle Designer ES 8.2</xmp:CreatorTool>

        <xmp:ModifyDate>2011-04-04T13:15:27-05:00</xmp:ModifyDate>

        <xmp:CreateDate>2006-03-24T12:09:19-05:00</xmp:CreateDate>

        <xmp:MetadataDate>2011-04-04T18:17:18Z</xmp:MetadataDate>

      </rdf:Description>

      <rdf:Description xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/" rdf:about="">

        <xmpMM:DocumentID>uuid:2b8434e9-051b-4cd4-946d-4a430813611d</xmpMM:DocumentID>

        <xmpMM:InstanceID>uuid:f38d5eb5-91f9-4597-83de-d564cb55505a</xmpMM:InstanceID>

      </rdf:Description>

      <rdf:Description xmlns:dc="http://purl.org/dc/elements/1.1/" rdf:about="">

        <dc:format>application/pdf</dc:format>

        <dc:subject>

            <rdf:Bag>

              <rdf:li>Keywords</rdf:li>

              <rdf:li>keyword 2</rdf:li>

              <rdf:li>keyword 3</rdf:li>

            </rdf:Bag>

        </dc:subject>

Ida Eve.Tracy

Avatar

Level 4

Thanks!!!  That is new to me.  I don't know where to put that code in the form?


Avatar

Former Community Member

Next to your Design View tab, there should be XML Source tab.  If not, right click on the space next to the Design tab and select XML.

Avatar

Level 4

Thank you again!!! I will try it !

Jodi

Avatar

Former Community Member

No problem, let me know how it works out.

Eve Tracy

Avatar

Level 4

I actually did it!  It is there!  Woo Hoo!  Thanks again soo much!   I

Avatar

Level 6

radzmar,

Your approach worked great, but is there a way to add values to the keyword tags automatically (via Javascript) by retrieving such values from user input (field data)?

Example:

Name.rawValue = John

State.rawValue = FL

Results:

"John"  and "FL" both shows up as a keywords in Properities.

Thanks

Shaun

Avatar

Level 10

Hi,

you won't be able to change that values at runtime as the matadata is not part of the form template itself but contained in the PDF.

http://partners.adobe.com/public/developer/en/xml/xfa_spec_3_3.pdf#page=1252

At design time you could use Designer's macro capabilities to create new metadata without entering the XML source.

But there is currently no such macro that can do this, so it needs to be developed by someone.

Avatar

Level 1

Is there anyway to remove or hide metadata as highlighted below?

metadata.png

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----