[ 
http://opencast.jira.com/browse/MH-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25341#comment-25341
 ] 

Adam Hochman commented on MH-6909:
----------------------------------

Why change the default cleanup operation to remove everything?  I had thought 
that the clean up operation had already provided a basic archive of a recording 
as a zip,  How would the service store these episodes?  I think we need to get 
a handle on what are the most pressing use cases.   From what I've seen, 
changing the download urls is an important requirement.  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.  There are also best practices to avoid this situation in 
the first place.  This story seems more useful for mass migration from one 
Matterhorn instance to another.  Is there a more elegant way than a mass 
re-ingest?  Added Ruediger as a watcher to solicit his opinion but perhaps we 
should bring this to list.

> 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]
_______________________________________________

Reply via email to