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

Re-Tag button not working

ShovelFace

MT 4.11
TeamSite 6.7.1
Windows 2003
OD 6.10

I am dealing with two languages and need to use a single EA per attribute. For example, using EA keyword, I have fields keyword, keyword_en and keyword_sp in MT. Once MT finished running, results from either keyword_en (if in English) or keyword_sp (Spanish) merged into "keyword" via .pl file.

Issue is that the initial population works great. Retag-all also works great. However, Retag on "keyword" does not work.

I've attached the metatagger.cfg file, as well as the logs from the "Re-tag all" and "Re-tag field" log files.

Any idea why the re-tag all is not working?

Find more posts tagged with

Comments

Migrateduser

the re-tag request as per: mtserver_9095-retag-description.txt


1179842428 lvl5 thread1: Request: 

  process_content

    dc.description
    <metadata>




        TeamSite/Metadata/keyword_sp
        string



        TeamSite/Metadata/keyword_en
        string



        TeamSite/Metadata/keyword
        string
        game, tigers, period, goals, whalers


        TeamSite/Metadata/dc.description
        string



        TeamSite/Metadata/description_sp
        string



        TeamSite/Metadata/description_en
        string





  Y:/default/main/NSAA/Internet/Zone/WORKAREA/Zone/templatedata/comm/ABC/data/a_en

The request is to run dc.description. dc.description is not retuning any metadata.


1179842429 lvl5 thread1: Response: 

  result

    <metadata>

        english
        utf-8
        Y:/default/main/NSAA/Internet/Zone/WORKAREA/Zone/templatedata/comm/ABC/data/a_en


            title
            string
            The Tigers take a bite out of Whalers




        TeamSite/Metadata/keyword_sp
        string


        TeamSite/Metadata/keyword
        string
        game, tigers, period, goals, whalers


        TeamSite/Metadata/description_sp
        string


        TeamSite/Metadata/dc.description
        string

I don't see any request to run keyword, keyword_sp or keyword_en, which you are saying is not working?

ShovelFace

Both keyword and description are not working and are exhibiting the same behaviour. My mistake that I posted "keyword" but put up the "description" log file. In any event, the same applies for both.

Suggestions?

Migrateduser

For the file that was handled by dc.description project, it has not generated any metadata. In the 're-tag-all' log file I see values for dc.description but not in the 're-tag' file. I'm trying to understand whats going on:

1) With re-tag-all, you get the values to display in the UI, For example:game, tigers, period, goals, whalers in 'Keyword'
2) When you click on 're-tag' against the keyword the values get cleared?

ShovelFace

Hope the following description clarifies:

On a document that has not been tagged:
- Fields in question (keyword and description summarization fields) are blank.
- When you hit Tag, these fields are populated.
- When you save and close, you can see the values in the Properties
- Going to the TaggerGUI on the document again will display the contents of the EAs (will not invoke MT)
- Re-Tag buttons are active near both summarization fields
- Delete content of fields, then save and close
- Values no longer exist in EA Properties
- Going to the TaggerGUI on the document again will display the blank fields
- Re-Tag button still active near both summarization fields
- Hitting Re-Tag button beside either field does not repopulate the field.
- Hitting Re-Tag all populate boths fields

Hope this clarifies.

Migrateduser

Could you look at the behavior of your postprocessor 'NSAAPostProcessor' with iwmtbatch by running:


iwmtbatch -suggest -dump Y:/default/main/NSAA/Internet/Zone/WORKAREA/Zone/templatedata/comm/ABC/data/a_en

and


iwmtbatch -suggest_by_tag keyword -dump Y:/default/main/NSAA/Internet/Zone/WORKAREA/Zone/templatedata/comm/ABC/data/a_en

ShovelFace

From iwmtbatch -suggest -dump Y:/default/main/NSAA/Internet/Zone/WORKAREA/Zone/templatedata/comm/ABC/data/a_en

Old metadata&colon;
<metadata>

keyword
string

dc.description
string

New metadata&colon;
<metadata>

Y:\default\main\NSAA\Internet\Zone\WORKA
REA\Zone\templatedata\comm\ABC\data\a_en

From iwmtbatch -suggest_by_tag keyword -dump Y:/default/main/NSAA/Internet/Zone/WORKAREA/Zone/templatedata/comm/ABC/data/a_en

Old metadata&colon;
<metadata>

keyword
string

dc.description
string

New metadata&colon;
<metadata>

Y:\default\main\NSAA\Internet\Zone\WORKA
REA\Zone\templatedata\comm\ABC\data\a_en

dc.description
string

keyword
string
null

ShovelFace

Any thoughts/Comments?

Migrateduser

It's somewhat complicated but here's the skinny:

- retag field uses a different call to MT than retag all.
- when retagging a field in MT 4.0 - 4.1.1, MT would only run the named analysis model in a single matching content processor. This creates two problems: a) if the field is populated by two separate CP's, then the results are incomplete and b) if the field is populated by a plug-in processor (pre/post), then it returns an error to tagui.

MT 4.1.2 fixes the limit to a single CP and the error on not matching a rack-field, but still does not know how to run plug-ins on a limited retag.

The remedy is as follows:
- move all your content analysis to a different CP that has a wierd filter
- add a final processor that runs content through the real CP using the retag-all API. (need to add logic to prevent infinite loops though).
- merge the results.

Let me know if I've explained this sufficiently.

Cheers,
Clark
MT 4.1.2. changes behavior to remove the bugs.