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

Calling metadata capture form from DCT

conmgmt

How do I call metadata capture template from a DCT?

When the user edits a dcr, we want the user to set/view metadata for that dcr. We are thinking of providing a callout from DCT that would pop up the metadata capture template for that dcr.

Find more posts tagged with

Comments

Adam Stoller

This is a tricky thing to do at best - because the DCR doesn't exist until you've actually saved it - so if you try to call the metadata capture CGI as a callout on the DCR before it's been saved ... it's probably not going to work right.

A cleaner solution - though it involves seeing multiple windows - is to have the closing of the Edit DCR window trigger a workflow - and in that workflow have a cgitask that runs the metadata capture CGI.

--fish
(Interwoven, Curriculum Development)

Test_invoice.txt

conmgmt

I would agree to the solution you suggested. How do I get control on save DCR and add cgitask ? In other words, which files need to be modified ? I haven't tired this before; do you have any examples/documentation that explains more.

Adam Stoller

The IWHOME/local/config/wft/available_templates.cfg file - in which you need to use:

<command value="tt_data" include="yes"/>

relative to the workflow that you wish to run in this context (perhaps one that is already there, or more likely one that you may end up creating specifically for this purpose)

There is documentation in the Workflow Developer's Guide (p. 66, 104) and the TeamSite Templating Developer's Guide (p. 34) - at least looking at the 5.5.2 versions of the manuals.

Note - the workflow will be instantiated when you *Close* or *Save and Close* the Edit DCR window - not on *Save* by itself - and it will only prompt you to run the job if the DCR is *not* already part of another active job.

As for the workflow itself - I believe some of the OOTB examples and/or solution workflow templates contain code that you could use for creating your own workflow - though if you've never developed a workflow before I'd recommend either getting someone who has or investing the time/money to go through the Advanced Workflow training course that Interwoven Education offers.

--fish
(Interwoven, Curriculum Development)

conmgmt

Assuming the dcr is in edit mode and saved .. can I have a callout on the DCT that reads like this....

<cgi-callout url="/iw-bin/iwmetadata.cgi"/>

I tried it, but comes up with a Metadata Capture form with just the header info and no capture fields. What info do I need to pass and how ?

Note: The metadata capture works using File -> Set Metadata. In other words, /local/config/metadata-rules.cfg and /local/config/datacapture.cfg are set correctly.

amalia

HEllo, I'm still learning about how to create templates in Interwoven, so my question is simple but as I didn't really have to use it YET, I'm a bit mixed. Is it correct if I say that to create a Template...first you have to create a DCT and when you save it you will have the DCR. But then you want to see the Presentation Template (TPL). With this I don't know exactly which files I have to create or modify first. I mean in the creation of general templates. Thanks in advance.

Adam Stoller

You've got the basics down right - you should probably spend some time with the TeamSite Templating Developer's Guide and/or sign up for one (or both) of the Templating tranining courses offered by Interwoven Education.

In short: the DCT is the configuration file that specifies the prompts for information that the user will provide (data capture template).

When saved, you get a DCR (data content record).

You can then use PT's (presentation templates) which are a mixture of HTML, XML, scripting languages (most usually Perl, but not limited to such) - that is used to process the contents of the DCR to generate something (most usually an HTML page, but basically anything you can figure out how to generate - ascii or binary - can be done via the PT).

As one of the developers' put it (paraphrased I believe): The presentation template (PT) is an abritrary program that process abritrary data (DCR) and generates arbitrary output

Again - the manuals, and the training courses are the best way to go if you are trying to get a better grasp on what you can do with templating and how to do it.

--fish
(Interwoven, Curriculum Development)

amalia

THanks. But for example, for creating the templates, you need to modify some files as Datacapture.cfg and Templating.cfg. the first one is it the one where you have to add a category you have created; and the other one, Templating.cfg, is it the one that I have to modify if I want to visualize the DCT (Datacapture), gives a reference to all categories created?

LooseCannon

The following is in the TeamSite Templating Dev's Guide

TeamSite Templating uses the following configuration files:

• templating.cfg: The main TeamSite Templating configuration file. It is an XML file that resides
outside of the TeamSite file system in iw-home/local/config and specifies:
– Which data categories and types are available for use with TeamSite Templating.
– Which presentation templates can generate HTML files on which TeamSite branches or
directories.
– Which presentation templates can be used with a specific data type.
– Which users or roles are allowed to create or edit data content records for a specific data type.
– The location of the presentation template used for previewing generated HTML files.
See Chapter 5, “Mapping Users, Templates, and Content Records,” for details about customizing
templating.cfg.

• datacapture.cfg: An XML file that defines a data capture template and defines the data capture
form for a specific data type. It defines the data type itself (such as what information the data type
will contain and parameters that define what type of data is legal in any input field). A
datacapture.cfg file also specifies the look and feel of the data capture form displayed in the
TeamSite GUI. Each data type has a datacapture.cfg file. A TeamSite Templating environment
can contain any number of datacapture.cfg files, differentiated by where they reside in the
directory structure. See “Data Storage Hierarchy” on page 23 for information about where
datacapture.cfg files reside. See Chapter 3, “Setting Up Data Capture Templates,” for
information about customizing datacapture.cfg.

Adam Stoller

Again - I suggest reading the manual and/or the training course(s)
- templating.cfg defines what DCTs are available and what PTs are available [through the GUI] for each of the DCTs

- datacapture.cfg files exist in two [general] locations - iw-home/local/config/ (for metadata capture) and iw-mount/branch/AREA/templatedata/category/data-type/ (for Templating DCTs).

--fish
(Interwoven, Curriculum Development)