TAGENTRY

The TAGENTRY transformation option extends the functionalities of Transformation, Composition and Scripting—that may be contained in tagging rules—to extraction rules.

The syntax is:

SCOPE scopeOption
{
    IDENTIFY(templateName)
    {
        @field[attribute]|[TAGENTRY]
    }
}

As example, consider this tag definition:

TAGS
{
    @TAG1
}

this tagging rule with composition:

SCOPE SENTENCE
{
    TAGGER()
    {
        @TAG1[LEMMA("developer")]|[#2]
        <1:4>
        @TAG1[LEMMA("product")]|[#1]
    }
}

and this template:

TEMPLATE(PERSONAL_DATA)
{
    @JOB
}

If this extraction rule:

SCOPE SENTENCE
{
    IDENTIFY(PERSONAL_DATA)
    {
        @JOB[TAG(TAG1)]
    }
}

is applied to this text:

Mark is the developer of the product.

you will get as extraction output:

TEMPLATE: PERSONAL_DATA

Field	Value
@JOB	developer of the product

As you can see, the composition in the tagging rule has not been extended to the extraction rule and applied to the extraction output. If you modify the extraction rule like this:

SCOPE SENTENCE
{
    IDENTIFY(PERSONAL_DATA)
    {
        @JOB[TAG(TAG1)]|[TAGENTRY]
    }
}

you will get this extraction output:

TEMPLATE: PERSONAL_DATA

Field	Value
@JOB	product developer

In this case, the composition in the tagging rule has been extended to the extraction rule consequently modifying the output thanks to the TAGENTRY transformation option.