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

tagUI two fields using same taxonomy but saving in different EAs

wexio89

I'm working with TS 6.7.1 sp1 and Metatagger 4.1.2.

My question is how can I use the same taxonomy for 2 different fields and save information in two different EAs say I have:

- Related topic
- Related tags

both fields use the same taxonomy called "universe" so I want to save related topic tags to EA teamsite/metadata/topic and related tags tags to EA teamsite/metadata/tags, is that possible?

Find more posts tagged with

Comments

Migrateduser

Do you need to access the Taxonomy browser for both fields oin the TagUI or do you just need values?

OOTB MetaTager is one taxonomy to one field. You can in a post processor gather all the "related tags" matched in the vocabulary and move them to a new field - "related tags." The issue here is that this new field in the TeamSite tagUI interface is not seen as a taxonomy enabled fields and so will not have an "Add/Edit" button and so there will be no ability to change or modify these values.

A way I might do this is to duplicate the taxonomy with two different names in MT. Manage the values as needed. You may want to look into a Rules Engine to help manage the tag field based on values in the topics field.

wexio89

Hi mkimbrell,

Thank you. So yes in deed I need to have taxonomy browser for both fields, I thought with the new TagUI you were able to have two fields using same taxonomy and assigning a different EA for each one, but I guess I was wrong. I don't like the idea of duplicating taxonomies just to have different EA values but if there is no other way I guess I'll have to follow up with that idea. Anyways I would like to hear more options on this.

wexio89

Hi all,

I was able to do this using new 6.7.1 sp1 tagui easily, mapping different fields in the MT_Rules file to the same taxonomy, without duplicating taxonomies. EAs are saved in corresponding EA and everything is working great.

Migrateduser

Correct - youa re using the new TagUI. Just to be clear since 6.7.1 SP1 teamSite has shipped with two ways to define the TagUI.

The old way is supported: /local/config/datacaprure.cfg & local/config/metadata-rules.cfg. You can continue to use this configuration if it fits all your needs. Also, it needs to be defined if you are going to tag multiple files at a time as the new TagUI does not currently support multiple file tagging.

The other option - is the new TagUI. You still have the local/config/metadata-rules.cfg file for associating rules with path conditions; however, you now define your rules in a single file per rule and you put them allin the /local/config/tagui/ruleset60/ directory. There is also the MT_Rules file. This is described in the appendix for the New TagUI in the TeamSite 6.7.1 SP1 Manual.

Migrateduser

Hi all,

I was able to do this using new 6.7.1 sp1 tagui easily, mapping different fields in the MT_Rules file to the same taxonomy, without duplicating taxonomies. EAs are saved in corresponding EA and everything is working great.

Can you share more details on how you were able to do this?

I tried this and my TAGUI screen is displaying a error.

Here is what I tried within my ruleset60\myrules.cfg

Content Type Tags

<br />

More Content Type Tags

<br />

my MT_TaxonomyMapping file has the following entry

sort problem.jpg

gzevin

Correct - youa re using the new TagUI. Just to be clear since 6.7.1 SP1 teamSite has shipped with two ways to define the TagUI.

The old way is supported: /local/config/datacaprure.cfg & local/config/metadata-rules.cfg. You can continue to use this configuration if it fits all your needs. Also, it needs to be defined if you are going to tag multiple files at a time as the new TagUI does not currently support multiple file tagging.

The other option - is the new TagUI. You still have the local/config/metadata-rules.cfg file for associating rules with path conditions; however, you now define your rules in a single file per rule and you put them allin the /local/config/tagui/ruleset60/ directory. There is also the MT_Rules file. This is described in the appendix for the New TagUI in the TeamSite 6.7.1 SP1 Manual.

what do you mean no multiple file tagging? 6.7.2 is a patch that essentially does that.