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

Tagger GUI and workflow process

krasteleva

Hi everyone,

We are using Tagger GUI to capture metadata fields associated with each file. Some metadata fields are mandatory (title, keywords) and must be filled by the user. Currently we are calling Tagger GUI screen during the workflow process.

But is it possible to capture those metadata when the file is saved to TeamSite?

Client concern is that during workflow process he has a workflow task with 20 files attached and he must fill in mandatory fields for all 20 files. It would be much more convenient if metadata were asked at the file creation (import or save) step.

Is it possible to accomplish in Interwoven?

Thank you!!
Irina

Find more posts tagged with

Comments

Pawan

Yes, it is.
You can enter the value of the mandatory items in your dcr onsave using formapi or, in your workflow before showing the Tagger UI screen to the user.

Adam Stoller

Hi everyone,

We are using Tagger GUI to capture metadata fields associated with each file. Some metadata fields are mandatory (title, keywords) and must be filled by the user. Currently we are calling Tagger GUI screen during the workflow process.

But is it possible to capture those metadata when the file is saved to TeamSite?

Client concern is that during workflow process he has a workflow task with 20 files attached and he must fill in mandatory fields for all 20 files. It would be much more convenient if metadata were asked at the file creation (import or save) step.

Is it possible to accomplish in Interwoven?

Thank you!!
Irina

What version of TS are you using?
Which GUI (CCPro, CCStd, or custom)?

It is certainly possible to provide a means of setting metadata before initiating the workflow - but that is largely one of user-training. Development can only go so-far in terms of leading the users towards setting the metadata, after that it's more an issue of user training and peer-pressure.

krasteleva

Yes, it is.
You can enter the value of the mandatory items in your dcr onsave using formapi or, in your workflow before showing the Tagger UI screen to the user.

Thanks Pawan, this is a good idea and we will be using it for content managed via DCTs. But most content of the site (as crazy as it sounds) is not managed via DCTs. Editors are creating site pages in Dreamweaver and uploading HTML files to TeamSite for version control and for workflows.

Thanks!!
Irina

krasteleva

What version of TS are you using?
Which GUI (CCPro, CCStd, or custom)?

It is certainly possible to provide a means of setting metadata before initiating the workflow - but that is largely one of user-training. Development can only go so-far in terms of leading the users towards setting the metadata, after that it's more an issue of user training and peer-pressure.

We are using TeamSite 6.7.1 with Service Pack 1, all editors are working in CCPro interface.

I agree about user training, it definitely will be part of the training process, but is there any way to force metadata creation?

thank you!!!
Irina

Adam Stoller

We are using TeamSite 6.7.1 with Service Pack 1, all editors are working in CCPro interface.

I agree about user training, it definitely will be part of the training process, but is there any way to force metadata creation?

thank you!!!
Irina

You could look into purchasing / using MetaTagger and configuring it / training it to automatically attache metadata to your assets. Other than that - you can't really "force" anything - you can make it available, and if people don't fill it in, you can make it more and more annoying to proceed through whatever their process is until they do fill in the metadata - but ultimately it comes down to user training.

If you're using CCPro - then generally what I advocate is to create a "Tag" button on the DCT form - which would help for tagging DCRs (tagging must be preceded by saving the DCR) - and add a step in your workflow that checks all [applicable] assets to verify that they do have metadata - otherwise you transition to a task where they fill in the metadata and then push it back into the main stream process