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

External attributes

khyati

If I have created a DCT, for this DCT where can I specify external attributes ? if I include metadata included for a DCR , is that an external attribute ?

Going thru PDF is not helping understand External Attributes

Find more posts tagged with

Comments

moonkhanna

If I have created a DCT, for this DCT where can I specify external attributes ? if I include metadata included for a DCR , is that an external attribute ?

Going thru PDF is not helping understand External Attributes

For your understanding, Extended Attributes are similar to your OS File attributes except that they are only recognisable by Teamsite and not by your OS. As the name suggests, these are "extended" "Attributes" --> Extension of the General attributes provided by the OS. You can have custom extended attributes as well as those applied by the TS Metadata mechanism.

Try reading more about File Attrubutes and then come back to TS Manuals and search for iwextattr.. Try the command on a couple of files and you will be able to understand extended attributes then

khyati

Thanks for the answer. I am going thru PDFs first and then I am asking where I am confused.

So I can capture metadata for a DCR, with "TAG". where do I mention or configure Extended Attributes, is it in the DCR or in some other file ?

In the Teamsite Search, there is a FieldMapping,xml file. Is this the file where I configure Extended Attributes ? or at some other place ?

Whats the difference between metadata and Extended attributes ?

Thanks

moonkhanna

Thanks for the answer. I am going thru PDFs first and then I am asking where I am confused.

So I can capture metadata for a DCR, with "TAG". where do I mention or configure Extended Attributes, is it in the DCR or in some other file ?

In the Teamsite Search, there is a FieldMapping,xml file. Is this the file where I configure Extended Attributes ? or at some other place ?

Whats the difference between metadata and Extended attributes ?

Thanks

Basically, Metadata is applied to your files in form of Extended attributes. Metadata is a separate mechanism in itself.

If you would have read about iwextattr, you would not have asked me the other questions

ISCBorisB

Where do I [...] configure Extended Attributes?

iwhome/local/config/datacapture.cfg and iwhome/local/config/metadata-rules.cfg.
Refer to TeamSite® Administration Guide, Chapter "Configuring Metadata Capture".

What's the difference between metadata and Extended attributes

TS Metadata entries are saved as Extended Attributes, see some explanations [post=111775]here[/post]

khyati

I read PDf again. I am getting to understand it little by little.

datacapture.cfg, being setup for metadata in iw-home\local\config folder is different than datacapture.cfg being setup in forms publisher, right ?
Can we rename this datacapture.cfg by other name or is it hardcoded. There was a line in PDF which read that you can rename your actual datacapture.cfg. This datacapture.cfg is based on "metadatacapture6.0.dtd" , so I think it will be different from the datacapture.cfg in FormsPublisher. I have taken that rename excerpt below

Pls explain

Following excerpt is from PDF

"The TeamSite installation program installs a sample file called datacapture.cfg.example in the iw-home\local\config\ directory.You can copy, rename, and edit the example file to create your actual datacapture.cfg file. Use the following DTD and annotated examples as a reference to create your own site-specific configuration"

Thanks

gzevin

I read PDf again. I am getting to understand it little by little.

datacapture.cfg, being setup for metadata in iw-home\local\config folder is different than datacapture.cfg being setup in forms publisher, right ?
Can we rename this datacapture.cfg by other name or is it hardcoded. There was a line in PDF which read that you can rename your actual datacapture.cfg. This datacapture.cfg is based on "metadatacapture6.0.dtd" , so I think it will be different from the datacapture.cfg in FormsPublisher. I have taken that rename excerpt below

Pls explain

Following excerpt is from PDF

"The TeamSite installation program installs a sample file called datacapture.cfg.example in the iw-home\local\config\ directory.You can copy, rename, and edit the example file to create your actual datacapture.cfg file. Use the following DTD and annotated examples as a reference to create your own site-specific configuration"

Thanks

you cannot rename this file. I mean the metadata capture file HAS to be called like that. It is similar to DCT, but not 100%. However formAPI is now compatible for single file tagging for both metadata tagging screen and DCTs.

on the other hand, have you asked your management to send you for Interwoven training? The manuals are somewhat obfuscated for the beginners.

khyati

Thanks, I got it. I read the PDF further below and I figured that out and your answer confirmed my understanding.

Question is, how do you invoke this datacapture.cfg (metadata). datacapture.cfg in FormsPublisher can be invoked by configuring it in templating.cfg. where do we configure this datacapture.cfg for metadata to invoke it ? I was reading PDf but could not figure this out.

what about metadata-rules.cfg, do we need to configure this file anywhere ?

Thanks.

gzevin

Thanks, I got it. I read the PDF further below and I figured that out and your answer confirmed my understanding.

Question is, how do you invoke this datacapture.cfg (metadata). datacapture.cfg in FormsPublisher can be invoked by configuring it in templating.cfg. where do we configure this datacapture.cfg for metadata to invoke it ? I was reading PDf but could not figure this out.

what about metadata-rules.cfg, do we need to configure this file anywhere ?

Thanks.

Tick on the file, than File->Tag. Or Tag from Properties. You configure datacapture.cfg 'in situ'. Right where it is. Same story with metadata-rules.cfg.