extended attributes Vs fields in DCR

Hi,
Wanted to know if someone has a document which states when it is a good idea to have extended attributes and when it is a good strategy to put the metadata in the DCR itself.

I have used extended attributes, normally when we want to deploy the attributes into the database so that the personalization engine can use it to personalize the website and also when we want to search the documents using extended attributes.
Have placed the metadata attributes in DCR when wanted to put them in the HTML (generated pages) as meta tags.

Your expert thoughts will be greatly appreciated.

Thanks,
AKB

Edited by AKB on 01/13/03 08:13 AM (server time).

Find more posts tagged with

Comments

gzevin

my approach usually is that if something DESCRIBES a document, and is not displayed in visible part of HTML, it goes into EAs (and I would advise anyone to consider EAs as metatags as such). Also, sematically, your metadata, even META tags in your HTML are relevant more to your final HTML rather than the DCR you have used to generate it, and, hence, they should be attached to the final generated HTML.

I know there are some different opinions, and earlier many developers would put metadata was inside DCR. I don't agree with this approach .... Smiley Happy

Greg Zevin
Independent Interwoven Consultant/Architect
Sydney, AU

ProfessorX

I agree with gzevin.

It is good practice to keep the metadata as EA's. Since IW architects it's product around Metadata tagging content using EA's then in the future releases of IW Suite of products most likely will enhance the functionality using the same architecture. You then might be able to leverage that new technology with out having to do a complete rewrite.

My Opinion

The Professor-

gzevin

good you mentioned metatagger - I forgot to do it.. yes, this is also one of the reasons Smiley Happy

Greg Zevin
Independent Interwoven Consultant/Architect
Sydney, AU