[
http://opencast.jira.com/browse/MH-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25343#comment-25343
]
Josh Holtzman commented on MH-6909:
-----------------------------------
> Why change the default cleanup operation to remove everything?
Because the working file repository is for storage of recordings being "worked"
on. Once the recording has been published, there's no need to keep the files
on fast (expensive) disks.
> I had thought that the clean up operation had already provided a basic
> archive of a recording as a zip
No, only failed recordings are zipped.
> How would the service store these episodes?
The first impl can be on disk, but other options might include a fedora or
dspace archive.
> download urls is an important requirement
I disagree. This is what DNS is for.
> It looks like the current search service doesn't support posting multiple
> mediapackages back to the search service. If this were supported, sys admins
> could simply find and replace server urls.
Multiple mediapackages can be posted via multiple calls to the service. This
doesn't seem like a problem.
> This story seems more useful for mass migration from one Matterhorn instance
> to another.
That's not the intent. I think you are focused on one particular use case
that, with proper planning, should not even be a problem. The episode service
is a repository that allows for, among other things, reprocessing of
mediapackages and rebuilding of distribution channels.
A reprocessing example: Matterhorn version 1.n adds speech recognition. With
the episode service, we can select mediapackages one-by-one, run a workflow
that performs speech recognition, and republishes the mediapackages to each of
the distribution channels.
A rebuilding of a distribution channel: we add some new feature to the search
index (e.g. search by spoken vs. written word). Lucene indexes are not like
SQL databases... there's no "update table" DDL to run, we need to rebuild the
search index. The episode service provides the repository from which we can
rebuild the lucene index for the Matterhorn media module.
> As an administrator, I want to see and manage (sort, order, search) all the
> track files ingested in order to re-ingest them
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: MH-6909
> URL: http://opencast.jira.com/browse/MH-6909
> Project: Matterhorn Project
> Issue Type: Story Card
> Components: Architecture & Services
> Affects Versions: 1.2
> Reporter: Olaf A. Schulte
> Assignee: Tobias Wunden
> Fix For: 1.2
>
>
--
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]
_______________________________________________
