Thanks Karen, sounds like we're doing the same kind of thing. We'll work
out exactly what data it is that we need to store and report back..as
you said, trying to standardise this would be very sensible!
Paul
On 18/10/12 16:07, Karen Dolan wrote:
Paul,
We got some expert guidance from Entwine about this this summer, but
haven't yet tried to implement it yet. If architecture hasn't changed
since then, adding new metadata fields requires extending the code, as
you saw in
http://opencast.jira.com/wiki/display/MH/Customizing+Dublin+Core+Catalogs.
Also, if you want to add those fields to the search index, you need to
extend the solr index schema, SearchQuery, solr query builder, solr
result object and related rest endpoint.
We have temporarily avoided developing and hard coding new metadata
namespace/catalog by stretching the intent of the existing Dublin Core
fields. For instance, course web site home page URL goes into the Series
dcterms:description. Course numbers , i.e. "CSCI-S 201" (Computer
science- Summer school- level 201), "ECON-E 101" (Economics-Extension
school- level 101), goes into dcterms:subject. The dcterms:subject of
the Recording is a presentation type tag with increment (i.e. the first
Lecture is L01, the third section is S03). This is likely to cause
headaches if a catalog is taken from or given to another system that
stretches the values differently.
If you think your recording metadata topics are remotely applicable to
other schools or media processes, please post those topics! You may find
colleagues here to help you standardize needed catalogs across schools.
Best of luck,
Karen
On 10/18/2012 8:56 AM, [email protected] wrote:
Date: Wed, 17 Oct 2012 14:30:58 +0100
From: Paul Gration <[email protected]>
To: <[email protected]>
Subject: [Matterhorn-users] Adding extra metadata and searching for it
Message-ID: <[email protected]>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Hi all,
Using 1.3.1 we're looking at adding some extra metadata to media
packages that contain information about our recordings (stuff that isn't
in the standard Dublin Core metadata set). What is the best way forward
to do this?
I've found the following online which look interesting:
http://lists.opencastproject.org/pipermail/matterhorn/2011-September/017138.html
http://opencast.jira.com/wiki/display/MH/Customizing+Dublin+Core+Catalogs
Following on from that we then need to be able to search specifically
for the additional metadata..Looking through the documentation / testing
facilities for matterhorn there is a search within the Episode and
Search REST APIs. Both of which seem to have a free text field search
and the search one also has a lucene search to target specific DC
fields. However the searches seem to target specific data tags to
search, if we're adding additional metadata tags, how can we ensure
these get included in the search as well?
Thanks,
Paul
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
--
Paul Gration
Multimedia Development
University of Sussex
+44 (0) 1273 873269
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
