Hi All,
I couldn't see a clear resolution on the discussion of strategy related
to Capture Agent Catalog Ingesting from last June.
http://lists.opencastproject.org/pipermail/matterhorn/2012-June/019940.html
Current Matterhorn behavior seems to be overwrite existing catalog
within inbound catalog. For instance, most of the series catalog
metadata is missing after an ingest from Galicaster. Galicaster
series.xml contains two pieces of series metadata: identifier and
title. Its not clear if just a partial set of series.xml was sent in
the iCal or if the full set had been sent but was truncated in Galicaster.
If the Merge versus Overwrite proposal is still open for input. I vote
with merge on ingest: within a catalog: if a tag is not sent, keep the
existing value; if the tag is sent and empty, update existing value to
empty; if the tag is sent and it contains a value, update existing value
to the new value.
Pros: Only the significant identifying tags and tags to update within
the catalog need to be set by an agent. This protects removal of custom
namespace attributes that the capture agent might not know how to process.
Cons: If the whole catalog needs to be swapped out, i.e. to ensure
removal of outdated tags and values, a different endpoint or flag needs
to be used.
Best Regards,
Karen
--
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]
_______________________________________________
