Hi Rupert,
Am 12.03.2015 um 12:11 schrieb Rupert Westenthaler:
>
> you can enable the "executionmetadata=true" option when sending requests.
thanks for this hint.
>
> from the documentation [1]
>
> - - -
>
> executionmetadata=true/false: Allows the include of execution metadata
> in the enhancement metadata of the response. Such data include also
> the execution plan used to enhance the parsed content. This
> information is typically only useful to clients that want to know how
> the parsed content was processed by the enhancer. NOTE that the
> execution metadata can also be requested by using the multi-part
> content item API described below.
>
> - - -
>
> The documentation of the Execution Metadata can be found at [2]
Would it be negative to say, that the output IMHO is not very useful.
I am sure the maintainer is able to use it.
Let me explain with an example,
I query the stanbol with "Germany" /1/ and "Deutschland" /2/, I would
expect nearly same results, as e.g. dpedia is aware of
http://dbpedia.org/page/Germany and http://dbpedia.org/page/Deutschland.
/1/
curl -X POST -H "Accept: application/json" -H "Content-type: text/plain"
--data "Germany"
"http://127.0.0.1:8080/enhancer/chain/default?uri=urn:fise-example-content-item&executionmetadata=true";
> 1
/2/
curl -X POST -H "Accept: application/json" -H "Content-type: text/plain"
--data "Deutschland"
"http://127.0.0.1:8080/enhancer/chain/default?uri=urn:fise-example-content-item&executionmetadata=true";
> 2
If I diff 1 and 2 I see a lot of
"...BNode@7bcd397" but not the human readable content which I can
understand.
So in this example, I would like to have an debug stage, which shows
what content was sent to enhancer and what it did return.
To stay in the context of the example, I guess the opennlp does not tag
the german word.
>
> Hope this answers your question
> best
> Rupert
>
> [1] http://stanbol.apache.org/docs/trunk/components/enhancer/enhancerrest.html
> [2]
> http://stanbol.apache.org/docs/trunk/components/enhancer/executionmetadata.html
Thanks a lot
Patrick
>
>
> On Thu, Mar 12, 2015 at 11:08 AM, Patrick Kirsch <[email protected]> wrote:
>> Hey list,
>>
>> is there any debugging/development best practices for debugging a enhancer
>> chain available?
>>
>> Here is my current situation:
>> - I have enabled geonames enhancer engine, it is configured within
>> chain 'default' and 'all active'. Geonames 'mvn test' passes and a valid
>> api.geonames.org account is configured and known working.
>>
>> - Now if I use the enhancer chain e.g. via webfrontend geonames
>> with query "New Zealand" geonames.impl.LocationEnhancementEngine gets
>> executed.
>>
>> - But if I try "Bad Düben" /1/ the
>> geonames.impl.LocationEnhancementEngine is not executed.
>>
>>
>> So my question is, what is the best way to debug the enhancer chain, to
>> check why certain enhancers do not get executed?
>>
>>
>> /1/ Small town in Germany with German Umlaute.
>>
>> Thanks
>> Patrick
>>
>
>
>
