Hi Manuel,
Are you using the bundle that is resulting from the indexing process? In
that case, you need to check if the bundle is activated in the Felix
Admin Console
Hope that helps.
Regards,
Rafa
El 28/01/14 14:12, Manuel Holtz escribió:
Hey Rafa,
yes, I've tried that repeatedly - not the EntityHub Indexing Tool part, but
the Managed Site approach (since the Managed Site seems to be working fine,
I assume that wouldn't make a difference). Also, the instructions for
setting up the configuration are very similar.
The documentation there is a little bit confusing, btw... e.g. there are
two sections titled "Configuring Named Entity Linking" that actually refer
to different approaches, and it partly refers to the deprecated Keyword
Linking process rather than Entity Linking.
But in the end, I run into the same problem: The EntityHub Linking engine
is "currently not active" and I cannot find information about the cause.
Again, if I configure a Keyword Linking engine instead, all is fine.
Manuel
On 28 January 2014 13:50, Rafa Haro <rh...@apache.org> wrote:
Hi Manuel,
Have you tried following this guide https://stanbol.apache.org/
docs/trunk/customvocabulary.html instead of the one you sent in your
previous email?
Regards,
Rafa
El 28/01/14 01:56, Manuel Holtz escribió:
Hey Everyone,
thanks so much for working on this awesome project! I just got started
with Stanbol and find it very promising for some entity recognition tasks
at hand.
Here's one issue that you might be able to help me with:
I set up an EntityHub Linking Engine to detect entities defined in a
custom vocabulary, as described at https://stanbol.apache.org/
docs/trunk/components/enhancer/engines/entityhublinking. But in the
enhancer list chain I added it to, the enhancer always shows as "currently
not available".
Inline images 3
Even in DEBUG mode, this seems to be the only relevant entry in the logs:
*INFO* [Thread-857]
org.apache.stanbol.enhancer.jobmanager.event.impl.EnhancementJobHandler
Error Message: Enhancement Chain failed because of required Engine
'testEntityExtraction' failed with Message: Unable to process ContentItem
'<urn:content-item-sha1-5b9e4c679944c06ed3bb3fe042e01839aa51c050>' with
Enhancement Engine 'testEntityExtraction' because the engine is currently
not active!
A little bit more background: Because I could not get the EntityHub
Linking Engine to run, I set up a (deprecated) Keyword Linking Engine
instead, pointing to the same Referenced Site - a Managed Site holding my
custom vocabulary. This works: I uploaded entities and they are correctly
recognised by the enhancer chain. So, I'm rather sure the Managed Site /
Solr index with the vocabulary are set up correctly. The configurations of
the two engines are almost identical... just that the Keyword Linking
Engine is active, and the EntityHub Linking Engine is not. Here's a
screenshot of the latter:
Inline images 5
Any idea how to further debug this problem?
Thanks,
Manuel
