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; } } }

can it be possible to set metadata for DCR generated html page in teamsite?

kumar123

Hi,

There is a requirement to set a Metadata for a DCR generated html page.

We have a template called press release. The user filling details in a DCR and generating HTML page.

Is there any way we can set Metadata automatically for the Teamsite generated html page?

Other than adding rules in datacapture.cfg and metadata-rules.cfg.

Find more posts tagged with

Comments

CRB

you can do it thru a workflow or use iwextattr -s in a script.

kumar123

you can do it thru a workflow or use iwextattr -s in a script.

can you please give some example on it?

vpatel

can you please give some example on it?

iwextattr is explained in the CLT guide.

Adam Stoller

Hi,

There is a requirement to set a Metadata for a DCR generated html page.

We have a template called press release. The user filling details in a DCR and generating HTML page.

Is there any way we can set Metadata automatically for the Teamsite generated html page?

Other than adding rules in datacapture.cfg and metadata-rules.cfg.

Is the metadata that is to be set something which has already been captured within the DCR? Something which is programmatically determinable? Or something for which some individual (content author?) would have to be responsible for providing using their own judgement?

If either of the first two, and you are using Perl-based PT's, you should be able to utilize iwextattr within the PT code to set the EAs on the generated output right there and then.

If it's the last case - you need to provide the UI for setting metadata which can either be done via the CCStd "wizard" interface (ugh) or add an explicit task for checking metadata, and if not present invoking the UI, within your submit workflows.

kumar123

iwextattr is explained in the CLT guide.

I have a script (ipl) which generats meta_include.html and title_include.html file when I push the html (ex: index.html).

the requirement is, with out adding tag (metadata) values it should add title and description values to meta_include.html

The script includes variables called date,title,keyword and description.

Date value has been added as "META name=****" in the meta_include.html file. This is included by calling system date.

I want to include the title and description of DCR into meta_include.html file as "META " tag when the script calls.

please check the part of script including title,date and description.

=============================
if (-f $file_path and ! ($file_path =~ /_include/) and $file_path =~ /\.html/) {
my %attrHash = ReturnExtAttributeHash("$current_env_vpath/" . $files[$i]);
my $title = $attrHash{"TeamSite/Metadata/Content Title"};
if($title eq "") {
$title = $attrHash{"TeamSite/Metadata/Title"};
}
my $keywords = $attrHash{"TeamSite/Metadata/Keywords"};
my $description = $attrHash{"TeamSite/Metadata/Description"};

# write the title include file if title attr. exists.
if ($title ne "") {
my $titlefile = $file_path;
$titlefile =~ s/.html/_title_include.html/;
unless (open FH, "> $titlefile")
{
$task->CallBack(1, "file handle creation failed");
}
print "writing $titlefile...\n" if($DEBUG);
$title =~ s/\n//mg;
print FH "$title\n";
close FH;
$titlefile =~ m/$iwmnt$current_env_vpath\//;
print "adding file to task $'\n" if ($DEBUG);
$task->AddFile($', $ADD_FILE_CMT);
}

my $metafile = $file_path;
$metafile =~ s/.html/_meta_include.html/;
unless (open FH, "> $metafile")
{
$task->CallBack(1, "file handle creation failed");
}

print "writing $metafile...\n" if ($DEBUG);

# get the file date and write date meta tag
my $mtime = (stat($file_path))[9];
my $mday = (localtime($mtime))[3];
if ($mday < 10) { $mday = "0" . $mday; }
my $mon = (localtime($mtime))[4] + 1;
if ($mon < 10) { $mon = "0" . $mon; }
my $year = (localtime($mtime))[5] + 1900;
my $dispDate = $year . "-" . $mon . "-" . $mday;
print FH "<meta name="\"DATE\"" content="\"$dispDate\"" />\n";

# write the keyword meta tag if the attribute exists
if ($keywords ne "") {
$keywords =~ s/\n//mg;
print FH "<meta name="\"KEYWORDS\"" content="\"$keywords\"" />\n";
}

# write the description meta tag if the attribute exists
if ($description ne "" and $description ne $title) {
$description =~ s/\n//mg;
print FH "<meta name="\"DESCRIPTION\"" content="\"$description\"" />\n";
}
close FH;
=============================

the title and description are getting called based on the Metadata (my $title = $attrHash{"TeamSite/Metadata/Content Title"}; my $description = $attrHash{"TeamSite/Metadata/Description"} Smiley Wink

Is there any way I can call these two fields directly from DCR and include in meta_inlcude.html file with out tagging?

Adam Stoller

The code you posted uses subroutines / methods not in evidence, so therefore we can only guess that they work correctly.
The code also appears to be part of a workflow externaltask script.

Is there any way I can call these two fields directly from DCR and include in meta_inlcude.html file with out tagging?

This question does not make any sense - nothing is being called from the DCR - the DCR is static.

The DCT could perhaps call something but (a) that's not the code you're showing and (b) I think that would be wrong.

The PT could perhaps call something but that's not the code you're showing either.

So - do you want to get this working as an automated step in your workflow? Do you want to get this working as an automated part of the PT? Or do you want to do something else?

For your existing code - add debugging statements and see what's happening - if you can't figure it out from that you need to hire someone who knows what they're doing to come in and figure it out for you (and possibly rewrite the whole thing better).

kumar123

The code you posted uses subroutines / methods not in evidence, so therefore we can only guess that they work correctly.
The code also appears to be part of a workflow externaltask script.This question does not make any sense - nothing is being called from the DCR - the DCR is static.

The DCT could perhaps call something but (a) that's not the code you're showing and (b) I think that would be wrong.

The PT could perhaps call something but that's not the code you're showing either.

So - do you want to get this working as an automated step in your workflow? Do you want to get this working as an automated part of the PT? Or do you want to do something else?

For your existing code - add debugging statements and see what's happening - if you can't figure it out from that you need to hire someone who knows what they're doing to come in and figure it out for you (and possibly rewrite the whole thing better).

Thanks Ghoti.

I tried automated external script in workflow. unfortunately it failed. I find another way and set the EAs successfully to html page after it generats.