You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2014/10/30 07:49:33 UTC
[jira] [Created] (STANBOL-1399) Allow target fields for wildcard
field mappings
Rupert Westenthaler created STANBOL-1399:
--------------------------------------------
Summary: Allow target fields for wildcard field mappings
Key: STANBOL-1399
URL: https://issues.apache.org/jira/browse/STANBOL-1399
Project: Stanbol
Issue Type: Improvement
Components: Entityhub
Affects Versions: 0.12.0
Reporter: Rupert Westenthaler
Assignee: Rupert Westenthaler
Priority: Minor
Fix For: 1.0.0, 0.12.1
Currently FieldMappings the do use a wildcard are not allowed to be mapped to an target field.
The main reason for this is that things like the following example
{code}
dc:* > dct:*
{code}
that would copy all fields from the dc elements namespace to the dc terms namespace are not implemented.
However copying multiple fields to a single one are already supported but not accepted by the FieldMappings constructor. A possible usage scenario is to collect all references or literal values to create an disambiguation context. See the following listing for an example.
{code}
* | d=entityhub:text > dis:textContext
* | d=entityhub:reference > dis:refContext
{code}
The change is really trivial as one needs only comment the check in the constructor of FieldMapping that explicitly disallows those things.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)