[
http://opencast.jira.com/browse/MH-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26198#comment-26198
]
Tobias Wunden commented on MH-7415:
-----------------------------------
The observation that the search index is currently relying on the fact that the
static metadata is present in the form of dublin core catalogs is correct and
not ideal. We always mandated the idea that this kind of metadata could be
present in other catalog formats such as mpeg-7 or scorm (or any other
standardized or proprietary format).
This is why the concept of the MediapackageMetadataService had been introduced
when we were lookinf for possibilities to add management metadata (just what
you need to display a mediapackage in a management ui) to the mediapackage
directly to prevent the need for constant catalog lookups. If you were to
introduce a new form of metadata, you would simply add a new implementation of
the mediapackagemetadataservice that would know how to access the metadata and
return it.
This means that a) the api only provides access to a subset of the metadata
that might be available (since it's display is not needed in any ui). It also
means that the metadata found in the mediapackage is originates from one or
more of the attached catalogs and therefore doesn't needto bewritten to the
search index as long as we make sure the metadata from the relevant individual
catalogs is added.
The mediapackagemetadata concept seems to be working just fine and fullfills
its needs, I would therefore suggest not to touch it. In addition, I propose to
use the same pattern to collect metadata thatis to be added to the search
index. Two interfaces, StaticMetetadataService and IsochronicMetadataService
need to be created. Our initial implementations would know how to provide hat
metadata from DublinCore or MPEG-7, respectively.
The main differences to the existing mediapackagemetadataservice would be that
the new one returns more metadata (everything that's needed to create an entry
in the search index) and adds support for languages. Of course, some metadata
items are contained in the mediapackage only (e.g. Mediapackage xml) and not in
catalogs and thus should be taken from there directly.
> 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]
_______________________________________________
