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

Post Processor Worked Fine Until TeamSite 6.7.2 Upgrade?

Tim__D

I'm running TeamSite 6.7.2(Solaris) and MT 4.1(Windows)

I have done the following steps on our development servier which we just upgraded to TeamSite 6.7.2

1). Upgrade metadata screen to TagUI.
2). Created a new ruleset in the rulesets directory.
3). Created my mapping file.

I am able to 'suggest' for fields that were metatagger enabled prior to the upgrade. I am also able to browse and select from Taxonomies.

What is not working is my post processor.

"iwmtresolveuids -implicit_add Products -implicit_add ContentTopics -implicit_add ContentTypes -grab alt"

I am only getting the labels and Taxonomy selections. It is not doing the -implicit_add or the grap alt at all?

Is this because of the version I am using?

Note on TeamSite 6.7.1 (no service pack) and MT 4.1 everything works as expected. Any help is appreciated.

Find more posts tagged with

Comments

Migrateduser

- What version of TS were you using before?
- Which TagUI?
- What version of MT?
- Do you get the same problem with "Tag" and "Tag All"?

That will help isolate the issue.
Clark

Tim__D

- What version of TS were you using before?
- Which TagUI?
- What version of MT?
- Do you get the same problem with "Tag" and "Tag All"?

That will help isolate the issue.
Clark

Hey Clark,

Previously I was using the old TaggerGUI using TeamSite 6.7.1(Solaris 10 - No Service Pack)

I was also using MetaTagger 4.1(Windows 2000).

The behavior is the same for Tag or Tag All. As recommended by the documentation, I have turned off 'suggest' in the new TagUI. If you enable it and click it your selections are removed.

My new platform is TeamSite 6.7.2 (Solaris 10) and MetaTagger 4.1(Windows 2000)

I have migrated all the rulesets to the new format, created a mapping file etc.. The alternate terms are still not going through?

- Tim

srinivasarao

Hi,

In MetaTagger 4.1, try the following

- Use the CIViewer Application (http://localhost:9080/civiewer/)
- Try the sample file and click the suggest button
- Click on the MetaData XML and observe whether it included the Nodes, Alternatives terms which you specified in the iwmtresolveuids post processors.

I am pretty much sure it will include the alternative terms and the other nodes which you want. if so, this shows that MetaTagger side no issues and there must be problem in the TagUI side, so check with the Support team and raise support ticket, so that we will look into the issue.

- Srinivas

srinivasarao

It looks like a bug in the Tag UI. Can you try with iwmtbatch CLT if possible?

Try with the following CLT

"iwmtbatch -suggest -dump -save filename” - See whether alternative terms are included in the "subjectMetadata0". It should include the alternative terms in the subjectMetadata0.

--Srinivas

Tim__D

Hi,

In MetaTagger 4.1, try the following

- Use the CIViewer Application (http://localhost:9080/civiewer/)
- Try the sample file and click the suggest button
- Click on the MetaData XML and observe whether it included the Nodes, Alternatives terms which you specified in the iwmtresolveuids post processors.

I am pretty much sure it will include the alternative terms and the other nodes which you want. if so, this shows that MetaTagger side no issues and there must be problem in the TagUI side, so check with the Support team and raise support ticket, so that we will look into the issue.

- Srinivas

Is this tool aware of TeamSite EA subjectmetadata0. Since this is not the TagUI how does this help me?

Migrateduser

Is this tool aware of TeamSite EA subjectmetadata0. Since this is not the TagUI how does this help me?

Tim, the output civiewer or iwgenmetadata are tools that will show metadata as generated by MetaTagger. TagUI or iwmtbatch will show how TeamSite interpreted the MetaTagger generated metadata. We are simply trying to establish where the problem might be, at the source(MetaTagger) or at the client(TeamSite/TagUI)

So if MetaTagger is the problem, using civiewer/iwgenmetadata also will not return you any implicit adds or Alts. But if you get them, the TagUI/iwmtbatch are failing to set them correctly in SubjectMetadata0

Migrateduser

Tim - If you set MT log level to 5 and restart the MT server, you will be able to see every transition of the metadata record. Hopefully this will help us isolate if the subjectMetadataX information is not coming in correctly or if there is a different issue in the auto-population.

Tim__D

Tim - If you set MT log level to 5 and restart the MT server, you will be able to see every transition of the metadata record. Hopefully this will help us isolate if the subjectMetadataX information is not coming in correctly or if there is a different issue in the auto-population.

After trying some of the above approaches I opened a support ticket with IWOV. They recommended that upgrading to the newest version was the solution to this issue. Thanks for all the help.

yanSi

My environment is TS 6.7.2 SP1 and MT 4.1.3. I believe I have the latest versions but I'm still seeing a problem with iwmtresolveuids -all.

In TS, subjectMetadata0 xml doesn't have the alt information. I checked the logs on MT and the logs indicate that the alt information was extracted.

TS EAs:

MTS
KHSOSOIVK
Investisseurs
0.246098
MTS::KHSOSOIVK

MT log:

MTS
KHSOSOIVK
Investisseurs
0.246098
MTS::KHSOSOIVK
alt term for investors
4
<_tc>1239805446
<_root>$$ROOT
english equivalent for investors
MTS::KHSOSOIVK

Which version did the support people say the fix was in?

Migrateduser

Descriptor properties are not automatically pushed into subjectMetadata0. If you want additional properties to push into extended attributes, the best approach is to use a post processor to populate an EA-bound attribute. TagUI can then be configured to include that attribute as hidden in the form.

yanSi

Hi Clark,

Using your suggestion, I have a post processor that gets the values I want and I have a textfield in my Tagger UI that saves to the EA: "TeamSite/Metadata/temp"

My output from MT contains:

TeamSite/Metadata/temp
string
abc

temp
string
abc

but the value "abc" is not saved anywhere. I also tried outputting the facet element which didn't work either. What should the value of the name element be?

yanSi

By the way, I'm using the next gen tagger ui. After re-reading the 6.7.2 Supplement, I found a statement that says we must provide a mapping entry for each MT field otherwise TagUI makes no attempt to search the MetaTagger provided metadata.

By providing an entry for a textfield in my mapping file, my textfield cannot be hidden anymore. I must also specify a metatagger project in the mapping file which means I can't just pass any string value; I must pass a valid SVterm from the specified MT project. The extracted value returned by MT must then be facets not attributes.

Now I'm wondering how the sample CLTs (filePath.pl, dateProcessor.pl) can work at all with TeamSite since they return attributes not facets. For that matter, how can any custom MT program that extract content and emit attributes work with TeamSite?

Migrateduser

That shouldn't be the case - there are both taxonomy projects and attributes. If you add a mapping to the attribute you should be fine.