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

2 Projects share MetaTagger

Aleks

Hi everyone,

Currently we already have a project to use MT to do its job for helping tag metadata from incoming assets.
We are rising another project now, and try to use MT too.
My question is: Can we use the same MT to share 2 different projects? For sure, the terms, rules, ... will be different.
If yes, how does MT know which project need to tag for? Where/What condition need to be set?

Thanks,

MT4.1.0

Find more posts tagged with

Comments

Migrateduser

It all depends on how you implemented the Content Processors.

MT can handle tagging content from a variety of sources. Use the CP and field definitions to create the different md records. (Naming conventions can help here.)

Migrateduser

Hi everyone,

Currently we already have a project to use MT to do its job for helping tag metadata from incoming assets.
We are rising another project now, and try to use MT too.
My question is: Can we use the same MT to share 2 different projects? For sure, the terms, rules, ... will be different.
If yes, how does MT know which project need to tag for? Where/What condition need to be set?

Thanks,

MT4.1.0

You can have as many projects as you like in Metatagger. I assume you are using the TagUI in teamsite to tag your DCR with the tags in Metatagger.
If this is the case, you can use Interwoven\TeamSite\local\config\datacapture.cfg to define MT projects needed on different DCT's

Aleks

You can have as many projects as you like in Metatagger. I assume you are using the TagUI in teamsite to tag your DCR with the tags in Metatagger.
If this is the case, you can use Interwoven\TeamSite\local\config\datacapture.cfg to define MT projects needed on different DCT's

That is a good one. Thank you very much.
Actually we even don't use TS, using MT only as a metadata generated server.
Now different applications will connect to it and ask for metadata. And this is what i am facing and try to figure out for generating metadata to different application through MT.

thanks again for your reply.

Migrateduser

The your best bet will be to develop a ost processor that IDs the unique metadata needed per path and modifies the field names or values based on those rules.