[
http://opencast.jira.com/browse/MH-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26217#comment-26217
]
Christoph E. Driessen commented on MH-7415:
-------------------------------------------
Tobias,
I've already taken into account that dublin core is just one possible metadata
container, or in general, that the used storage should be an implementation
detail.
What I am interested in is if we can define a stable interface for the extended
set of metadata. Stable means, a set that is unlikely to need customization for
each and every installation. If so, the service based approach of extracting
metadata seems suitable to me. If not I would not recommend to put any effort
in creating a decent abstraction (interface) but leave the knowledge of how to
access metadata in the search & index service like it is done now.
Another question is why there exist two means of getting the basic set of
metadata: one by asking the media package object itself, the other by asking a
service which returns exactly the same data, at least right now (please see my
previous post).
As I outlined in my previous post, search & index depends on the kind of
metadata used. Do you think we should put any effort into creating a generic
search & index service that is able to deal with different metadata
sets/interfaces, maybe through the configuration of metadata readers and an
index schema? Or should there be a different implementation for each set of
metadata?
> 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]
_______________________________________________
