[ 
http://opencast.jira.com/browse/MH-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26151#comment-26151
 ] 

Christoph E. Driessen commented on MH-7415:
-------------------------------------------

Tobias, since I'm new to the architecture I need to get some things clear by 
trying to repeat your comment in my own words.

First, I suppose you meant "MediaPackageMetadataService" since I cannot find a 
MediaPackageMetadataProvider. Am I right here or do I miss something?

Then, as MediaPackageMetadata is not part of a MediaPackage but is returned by 
a service, it has to be constructed in dependency of the MediaPackage. It seems 
natural that for this process the MediaPackages ingredients will be used, i.e. 
the attached catalogs. But maybe there will be other means of gathering the 
metadata, e.g. by querying external entities. 

So we have two types of metadata, internally provided, i.e. contained in the 
media package as a catalog or whatever and externally provided metadata, 
returned by the MediaPackageMetadataService. 

Right now the externally provided is supplied by the internal catalogs, but 
this is hidden to the client.

So to build the index both types of metadata should be used. That's what you 
meant by "[...] get a reference to all mediapackage metadata providers and ask 
all of them [...]", right?

So besides having a addStandardDublincCoreFields(SolrUpdateableInputDocument, 
...) method there should be 
addMediaPackageMetadataFields(SolrUpdateableInputDocument, ...). And as no 
language information is provided alongside the MediaPackageMetadata these 
values are treated as language_undefined.

But filling the SolrUpdateableInputDocument directly by multiple methods may 
lead to duplicate entries. Maybe it's better to use an intermediate object to 
gather all information, then discard duplicates, before writing to the index. 
Probably this can be handled by solr also. I'll have a look.


> Add support for multiple field values in search index
> -----------------------------------------------------
>
>                 Key: MH-7415
>                 URL: http://opencast.jira.com/browse/MH-7415
>             Project: Matterhorn Project
>          Issue Type: Task
>          Components: Architecture & Services
>    Affects Versions: 1.1 
>            Reporter: Tobias Wunden
>            Assignee: Christoph E. Driessen
>             Fix For: 1.2
>
>         Attachments: 0001-made-DCMIPeriod-immutable.patch, 
> bugfix_SolrUtils.patch
>
>
> Right now, only the first value of multiple possible values of dublin core 
> documents make it into the search index. This needs to be fixed by adding all 
> available field values, eventually by turning the respective fields either 
> into indexed fields (title_en, title_de) or multivalue fields (or both).

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to