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

SecretHen

Some fields on my Tagger GUI have a regenerate button displayed next to them and some do not. I cannot figure out how this is controlled. Can anyone explain?
Thanks in advance
Secret Hen

Find more posts tagged with

Comments

Migrateduser

Only the fields that have are "MetaTagger enabled" have regenerate buttons, which cause MT to try to suggest values. The MT enabled fields are the <item> names in datacapture.cfg that have matching <category> tags in metatagger.cfg.

Example datacapture.cfg:
...
<item name="foo">
...
</item>

Example metatagger.cfg:
...
<category>
<tag>foo</tag>
...
</category>

"foo" appears in both, so it is Metatagger enabled and will have a regenerate button.

SecretHen

so can a field exist within Tagger GUI, but be purely manually entered? Is this the case (is it legitimate?) for fields with a metatagger.cfg category entry, but no datacapture.cfg item entry?

Migrateduser

Yes, these fields can, and often in practice do, exist. For example, you can have a content expiration field that does not appear in metatagger.cfg but does appear in the datacapture.cfg.

Adam Stoller

for fields with a metatagger.cfg category entry, but no datacapture.cfg item entry?
I think you want that the other way around:
for fields with a datacapture.cfg category entry, but no metatagger.cfg item entry?
The datacapture.cfg file controls what fields you see when collecting the metadata. The metatagger.cfg file controls what fields MetaTagger generates and/or provides assistance with filling in.

--fish
(Interwoven Senior Technical Consultant)