Tobias,
Here is the question:
Is it a bug if the eventCatalog event_id is not separate from the
recording dcterms:identifier?
At what point could the recording dterms:identifier be safely set?
This is not urgent for us because we are using another dcterms field
that sort of fits.
It's the metadata-in-work page that bothers me more that the code.
As asked in the first email of this thread, how do you feel about a
child page to list implementation restrictions to the metadata?
Thank you,
Karen
On 7/20/2012 11:16 AM, Karen Dolan wrote:
Tobias,
Unrelated philosophically, but married in implementation?
Line 415, SchedulerServiceImpl.addEvent():
"eventCatalog.set(DublinCore.PROPERTY_IDENTIFIER,
Long.toString(workflow.getId()));"
The schedule-recording-request dublincore taken over as the
"eventCatalog" ends up in the episode.xml.
So, the episode dcterms:identifier inherits eventCatalog
dcterms:identifier.
The event_id is a long integer ([0-9]+
Here is a second point the eventCatalog dcterms:identifier is tied to
event_id:
SchedulerServiceImpl.updateEvent()...
public void updateEvent(final DublinCoreCatalog eventCatalog)
626:
if
(StringUtils.isBlank(eventCatalog.getFirst(DublinCore.PROPERTY_IDENTIFIER)))
{
logger.error("Dublin core does not contain identifier, so event
update is not possible.");
throw new SchedulerException("Missing event identifier");
}
631: final long eventID =
Long.parseLong(eventCatalog.getFirst(DublinCore.PROPERTY_IDENTIFIER));
.....
---------------------------
An example of input dublincore sent to the Scheduler Service REST
endpoint POST:
<dublincore xmlns="http://www.opencastproject.org/xsd/1.0/dublincore/";
xmlns:dcterms="http://purl.org/dc/terms/";>
<dcterms:creator>Jaylo Smith</dcterms:creator>
<dcterms:isPartOf>20120334444</dcterms:isPartOf>
<dcterms:temporal>start=2012-07-17T19:15:00Z;
end=2012-07-17T22:15:00Z;
scheme=W3C-DTF;</dcterms:temporal>
<dcterms:subject>CSCI S-101</dcterms:subject>
<dcterms:spatial xmlns="">ncast_pr720</dcterms:spatial>
<dcterms:identifier>PUB0013223639</dcterms:identifier>
<dcterms:title>Lecture 4</dcterms:title>
</dublincore>
How it ends up in the episode.xml ( 90582 is the initial job
id==workflow id==event id)
<dublincore xmlns="http://www.opencastproject.org/xsd/1.0/dublincore/";
xmlns:dcterms="http://purl.org/dc/terms/";>
<dcterms:creator>Jaylo Smith</dcterms:creator>
<dcterms:isPartOf>20120334444</dcterms:isPartOf>
<dcterms:temporal>start=2012-07-17T19:15:00Z;
end=2012-07-17T22:15:00Z;
scheme=W3C-DTF;</dcterms:temporal>
<dcterms:subject>CSCI S-101</dcterms:subject>
<dcterms:spatial>ncast_pr720</dcterms:spatial>
<dcterms:identifier>90582</dcterms:identifier>
<dcterms:title>Lecture 4</dcterms:title>
</dublincore>
On 7/20/2012 4:43 AM, Tobias Wunden wrote:
Hi Karen,
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?
the dcterms:identifier identifies the recording in a bibliographic sense, while
the workflow id is an interal id to Matterhorn. Therefore these two ids are
unrelated.
Tobias
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
--
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]
_______________________________________________
