nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Newbie:Metadata

raghavsrinath

Hi,
Can any body tell me is it necessary to apply metadata to all the pages you create or only to the DCR you create

Raghav

Find more posts tagged with

Comments

iwovGraduate

Setting up metadata is optional alltogether. Templating will automatically set the necessary metadata to the html pages created from DCRs.

nootopian

is there an easy way to write the keywords entered into the metadata capture form into the meta keywords within the html doc?

akshathp

One way is to extract the Extended Attributes of the file and inject them as a tag in the html file. What you could do is have a perl script which uses TeamSite CLTs like iwextattr to fetch the EAs and iwmetatag to inject them as a <META> tag within the html. This perl script could be run either as an option from TeamSite GUI (after you alter and add this in the iw.cfg) or it could be run via a workflow.

Hope this helps.

Akshat Pramod Sharma
Interwoven Inc.

mogoo

This is what we've found...

put this line in your tpl, for each metadata field you want to pull from
--------------------------------------------------------------------------------------------------
my $eavalue = getEA('/default/...', 'TeamSite/Metdata/...');
#where /default/... is the path to the html file you want to extract metadata from, and TeamSite/Metadata/... is the specific meta field you want the value from

this was actually in our local utils.pm, left behind from our IW consultant
--------------------------------------------------------------------------------------------------
sub getEA
{
my $file = shift;
my $eaname = shift;
my $eacmd;
my $value;
my $eaargs;

if ($eaname)
{
$eaargs = "-g \"$eaname\" \"$file\"";
}
else
{
$eaargs = "$file";
}

$eacmd = "$iwhome/bin/iwextattr $eaargs";
chop( $value = `$eacmd` );

return $value;
}

Hope this helps,
maureen

Adam Stoller

Based on the original question (the thread seems to have diverted) - if you mean: is it necessary to apply TeamSite Extended Attributes to all the pages you create or only to the DCR you create - the answer is:

A DCR is identified by having a specific Extended Attribute associated with it (TeamSite/Templating/DCR/Type="category/datatype" - where 'category' and 'datatype' are the values of the templating category and datatype - not the literal strings)

This enables TeamSite Templating to bring up the view or edit DCR window when you attempt to view or edit a DCR within the TeamSite GUI - regardless of what file extension (if any) exists on the DCR.

Pages generated through the templating interface have multiple extended attributes associated with them:

TeamSite/Templating/Encoding=
TeamSite/Templating/PrimaryDCR=name_of_dcr_file
TeamSite/Templating/PrimaryDocumentType=category/datatype
TeamSite/Templating/PrimaryPT=name_of_presentation_template
(again, the values to the right of the '=' are figurative here not literal)

These extended attributes allow TeamSite to "do the right thing" when you select one of these files and select the File > Generate / Regenerate options (or some name like that, I don't have the GUI up at the moment) in the WebDesk Pro UI or the Regenerate link in the WebDesk UI.

Some other Interwoven products may make use of other extended attributes (for instance, VisualAnnotate stores annotation information within extended attributes).

All other extended attributes applied to files within TeamSite are purely optional and can be used at your discretion (some folks tag files with expiration dates for instance)

--fish
(Interwoven, Curriculum Development)

Renata

I am trying to set up such a script and it seems not be able to pass the values back into the final HTML.

in my HTML I call <iw_value>
<meta name="dc.creator" content="{iw_value name='$title}"/>
this worked when we're passing values form a dcr not from a varaible, but when my $title is defined as:
my $title = getEA("templatedata/generic/data/dcr1", "TeamSite/Metadata/Title");
the <iw_value> doen not return any value?

I suspect I'm not calling the right EA or not passing the right arguments for $title. I could not find any info on how to pass this kind of arguments in ... would anyone know more about that? thanks a lot in advance.

mogoo

syntax? or was this just a typo on the post?...
<meta name="dc.creator" content="{iw_value name='$title}"/> should be...
<meta name="dc.creator" content="{iw_value name='$title'/}">

Renata

that was just a typo ... I think the problem is that I've entered my getEA() onto a Utils.pm and my template can't access this module. As soon as I have the function within the template it works. I'm working on resolving the porblem with this module.

thanks