[
http://opencast.jira.com/browse/MH-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26179#comment-26179
]
Christoph E. Driessen commented on MH-7415:
-------------------------------------------
Still trying to get things clear. We have:
# Common metadata
There should be a common set of metadata covering basic needs so one is able to
work with the system in a reasonable way. This demand is currently met by the
MediaPackage interface itself and also the MediaPackageMetadata interface.
Please see "API clarification" for some questions about that.
# Specialized metadata
There should be the possibility to provide specialized, installation dependend
metadata. For example ETH needs a different set of metadata than UCB, and they
both decide to store their metadata in different formats. DublinCore may be one
of them.
# Strong coupling between search & index and metadata extraction
The search & index service needs to know precisely which kind of metadata it
should retrieve at which location and how it gets interpreted. The offered
search facilities depend on the amount and type of metadata gathered.
This leads to the conclusion that search & index is strongly coupled to
metadata extraction.
I'd like to discuss the benefit of having the metadata extractors build as a
service rather than just a simple library to be used by the search & index
service. I also want to suggest that the search & index service should also be
responsible for delivering metadata because of the strong dependency mentioned
above. I think, in fact, this naturally belongs together.
In case the extraction facility is really needed as a separate service we can
build one based on the extraction library later.
# API clarification
I found some similarity in the MediaPackage and MediaPackageMetadata interfaces
regarding metadata and would like to learn why they are separated. Looking into
to implementation I found that MediaPackage does not simply delegate to
MediaPackageMetadata but manages its own set of data. What's the reason for
that? When using one of these properties, e.g. to set them in the index, one
currently needs to consider three different locations with probably all
different values.
Maybe MediaPackageMetadata is subject to extension while MediaPackage is not?
MediaPackage
- contributors
- creators
- date
- language
- license
- series (id)
- series title
- subjects
- title
MediaPackageMetadata
- contributors
- creators
- date
- language
- license
- seriesIdentifier
- seriesTitle
- subjects
- title
> 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]
_______________________________________________
