Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Metadata and Extended Attributes
System
Hi,
Whats the difference between Extended atrtibutes and Metadata?
I want to set some of the metadata fields as part of HTML creation (from a .tpl)
When I use "iwextattr" to set extended attributes, the values that get set are separate from the metadata.
Is there any way to set the metadata from a .tpl?
Another query:
When I use DataDeploy to deploy only the metadata (and not the DCR) to a database (NOT using a DAS), can I configure it to write the extended attributes to the database?
Thanks
-Ashish
(ashish_deshpande@hotmail.com)
Find more posts tagged with
Comments
Michael
Hi Ashish,
As far as I was aware Metadata is stored as extended attributes. If you do File -> File Properties (or iwextattr -l) on a file which has metadata set you should be able to see these attributes.
You can set metadata as part of the generation process. If you call a script in your TPL than you can set an extended attribute. If you use the correct name (check an existing file with iwextattr -l) then you should see the results in your Set Metadata template.
Yes DataDeploy can deploy metadata... I suggest you take a look at the manual and if you have any specific queries raise another post.
Cheers, Michael.
Migrateduser
Thanks Michael.
I just need to prepend the external attribute with TeamSite/Metadata/ to set the metadata attribute.
abhishek_gupta
Whatever values you set from the iwmetadata.cgi file - i.e. from the $iw-home/local/config/datacapture.cfg file gets stored as metadata which can be deployed to the Database using DD.
Also, what I see from the File Properties is that the extended attributes are wrt to templating, for e.g which DCR the html file is created from, which TPL is used to create the file etc.
AK
Interwoven TeamSite Consultant
gzevin
just adding. For dataDeploy there is NO difference where the data is coming from - both EAs and DCR fields are deployed. In the end, all end up with key-value pairs that could be manipulated later with Tuple Preprocessor.
Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU