how to store extended attribute in DCR

We are trying to make extended attribute available in DCR.

Example:

If end user creates a new Data Content Record and selects image.gif for this DCR. The image.gif has extended attributes(keyword, author, etc). How can we retrieve the extended attributes of image.gif and store that information in DCR so we can use datadeploy to store DCR along with EA of image.gif in database.

Find more posts tagged with

Comments

james1

Can you deploy the DCR contents as-is (containing a reference to image.gif) with DataDeploy, and also deploy file EA's (including image.gif's EA's) with DataDeploy as well, and have your application find the image.gif EA's based on the image.gif reference in the DCR?

If you transfer EA's into the contents of your DCR, (1) how will you keep the EA's up-to-date, and (2) how will you prevent those values in the DCR from being modified or removed?

-- James

--
James H Koh
Interwoven Engineering

ming

James:

Can you for the reply.

We are only using DAS to deploy metadata (EA). We will have our own customized script for DCRs. We want to deploy metadata of the image file and other assets in the same table as DCR stores; it will be easier for the Portal server to retrieve that information.

We are planning to set those values in the DCR as Hidden value, so they can not be modified or removed. I guess that we will not synchronize the EA in DCR and the actual file (asset). We will update the DCR if end users update the asset (image.gif).

Adam Stoller

How about doing this within a PT - to generate an XML file with the information you want - including the EA's of the refernced image file - and then use DD to deploy data from the XML file rather than directly from the DCR?

True, it doesn't use DAS - but I think it would accomplish what you want...

--fish
(Interwoven Senior Technical Consultant)

Renata

Based on our business requirements we're capturing some information on a DCR then with the tt_data event we're pushing that information into teamsite metadata & e/a. We made these fields read only on Set Metadata form, so the information is displayed but can only be edited via a dcr.

We had to develop our own scripts for that and it works well and keeps the customer happy. Let me know if you'd need more details.

ming

Thank you for the reply. Our requirement is contrary to your requirement. We need to set e/a on Set Metadata form and store those e/a in DCR as hidden value based on the assets (eg. Img.gif) that user selects when creating the DCR.

I will be very appreciated if you can send your scripts to me so I can take a look to see whether we can borrow your ideas.