Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
MetaTagger and EA naming
ShovelFace
MT 4.12
In order to tie in an MT Studio project to an EA, the project name used to have to match the EA. For example, an EA as follows
=> TeamSite/Metadata/descriptive/dc.abc
would have a related MT Studio project dc.abc. Once tied into MetaTagger and the values saved, an additional EA is created, namely
=> TeamSite/Metadata/descriptive/dc.abc_codes
This implied that all EA suffixes be uniquely defined.
Question:
Can an EA, such as
=> TeamSite/Metadata/descriptive/dc.abc/0/content
be tied into MetaTagger/MT Studio project if the other EAs are named similarly, such as
=> TeamSite/Metadata/descriptive/dc.def/0/content
If so, is the best way to do it via the MetaTagger Mappings file? Has anyone attempted this?
Find more posts tagged with
Comments
Migrateduser
Yes, the metataggerMapping way is the best.
You can have your EAs defined in a ruleset under the ruleset60 dir
and you can map those EAs to any MTProject using the MTMappings file.
Your metataggerMappings file can look something like this:
As you can see, two EAs with the same label are mapped to the same MTProject. But, both of them are under different tabs.
Hope this helps!
ShovelFace
Is there a way to do this when not using the next generation taggergui?