[
https://issues.apache.org/jira/browse/STANBOL-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler resolved STANBOL-1411.
------------------------------------------
Resolution: Fixed
fixed with http://svn.apache.org/r1702947 in trunk and merged to 0.12 with
http://svn.apache.org/r1703119.
I use the provided patch but modified it so that {{Suggestion#getSite()}}
considers both {{entityhub:site}} and {{fise:orign}} values.
> Make the MLT disambiguation engine work with the FST linking engine
> -------------------------------------------------------------------
>
> Key: STANBOL-1411
> URL: https://issues.apache.org/jira/browse/STANBOL-1411
> Project: Stanbol
> Issue Type: New Feature
> Components: Enhancer
> Affects Versions: 0.12.0, 1.0.0
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Fix For: 1.0.0, 0.12.1
>
> Attachments: fst_disamb.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The Solr MLT disambiguation engine uses the {{entityhub:site}} property to
> check if a suggested Entity originates from the Entityhub Site that is
> disambiguated.
> This {{entityhub:site}} is written by the EntityhubLinkingEngine, but not by
> the FST linking engine as this engine directly uses a SolrCore and does -
> strictly speaking - not know from (depend on) any Entityhub site.
> However STANBOL-1391 added the feature to the FST linking engine to provide
> origin information for annotations. Those do use the {{fise:origin}} property.
> This issue is about extending the MLT disambiguation engine to consider
> {{fise:origin}} as a fallback to {{entityhub:site}}. This will allow users
> that want to use MLT disambiguation together with FST linking by configuring
> the name of the Entityhub site as value of the
> {{enhancer.engines.linking.lucenefst.origin}} property for the FST linking
> engine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
