hi tobias,
thanks for the reply!
On 17/12/12 17:44, Tobias Wunden wrote:
we are using a distributed install of matterhorn 1.3.1.
i'm trying to make sure that only necessary files are left behind so as not to
fill up our disks too quickly! i think the only files we want to keep are the
original ingested files (such as the avi uploaded by our epiphan capture agents
for example).
you also want to keep the original dublin core catalogs.
ah yes, good point.
i'm assuming that files left behind in the shared work directory are not used
at all and everything is served from the distribution directories?
If everything is configured in the right way, then that assumption is true. If
you want to make sure, just go to your media module (Engage) and use the REST
endpoint at /search/docs to take a look at a random MediaPackage XML. If the
XML does not include any URLs pointing to the working file repository (that
would be /files/...), then you are free to delete whatever you deem unnecessary.
the only thing that points to /files is the acl. but this doesn't seem
to get cleaned up anyway.
the archive operation of the workflow doesn't appear to do anything (other than
add a message in the log saying the media package is archived) but i can't find
any documentation saying what it is supposed to do so i'm not sure what is
supposed to happen. can anybody explain it's purpose?
In 1.3, the archive operation simply adds the mediapackage to to the archive's
search index. Be sure to realize that in most configurations, using the archive
will require you to keep archived files in the working file repository or use
the archive operation in a way to only archive files that are reachable through
the distribution channels.
1.4 will bring a much enhanced archive that is storing its own copies of the
content you decide to archive, so the working file repositoy is back to what it
should be: a repository for keeping working files during processing time.
ok i think i understand. so there is really no need to use the archive
operation for now? if we do include it should it be placed after the
cleanup?
is there an operation you can add to the workflow to delete all the files from
the shared workspace?
The "cleanup" operation is what you want to look at.
aha! that does the trick!
i added the following to our (epiphan specific) workflow and it seems to
be working nicely:
<operation
id="cleanup"
fail-on-error="false"
description="Cleaning up">
<configurations>
<configuration
key="preserve-flavors">multitrack/source,dublincore/*</configuration>
</configurations>
</operation>
many thanks,
paul.
--
Paul Pettit
Multimedia Development
University of Sussex
+44 (0) 1273 87 3223
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
