Does anyone know, off the top of their head, if the Recording/Episode
dcterms:identifier needs to match the Workflow Id after the ingest job
has completed?
Thanks,
Karen
On 7/19/2012 9:19 AM, Karen Dolan wrote:
Regarding: Recording metadata Dublin Core term identifier
(dcterms:identifier),
The recording item's dcterms:identifier field is ignored during MH
schedule request. The dcterms:identifier is during Matterhorn
Scheduling Service create to be of type long and maps to the
Matterhorn Job Id/Workflow Id. The ingest, and other workflow steps,
require this dependency.
Would it be Ok to clarify the recording's dcterms:identifier
restriction on the "Matterhorn metadata scheme work in progress page".
http://opencast.jira.com/wiki/display/MH/Matterhorn+metadata+scheme+%28work+in+progress%29#
It's not clear if type ITEM is the equivalent or a super type of a
type Matterhorn Recording/Episode. If it's a super type, how do people
feel about adding a child page to clarify metadata constraints for
type Matterhorn Recording/Episode.
Cheers,
Karen
Karen Dolan
Harvard University, DCE
617-998-8439
[email protected]
--
Karen Dolan
Harvard University, DCE
617-998-8439
[email protected]
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
