Hi Adam,
Thanks for any clarification. I'm not sure which release notes you referenced
below.
I'm trying to get familiar with this product from the point of view and
administrator, installer and end user, and I don't want to start reading java
source code just yet.
For example, I made a number of test submittals using the Admin recording upload
facility, and decided I wanted to clean up unwanted recordings from the system.
Surprisingly, with the 1.1 Admin tool there is still no way (that I saw) to
delete or edit (e.g. change the Title) of a submitted recording, pretty basic
admin functionality supported on most other video portals.
The Wiki said there would be some additional detail about doing this, but I was
unable to find it. So I tried to do the cleanup myself.
Using the REST forms I was able to "retract" the download and streaming files,
and "unpublish" the entries for Engage.
But there doesn't seem to be any REST call to delete a mediapackage. There is
a "/discardMediaPackage" under Ingest, but I could never get it to work. In
fact, there does not appear to be any Admin page or REST call to list all
mediapackages (or all downloadable files or stream files either) in the system
(please correct me, as I might be wrong or misinformed on all of these points). Surprisingly, there is no table in the
database, it appears, that lists mediapackages. They must be somewhere else.
Well, I found mediapackage links under the "files" and "workspace", so I just
deleted them all. That would be the end to all those unwanted recordings, I
thought.
Not so. The "Recordings" that are listed do not seem to be mediapackages at all,
but "workflow instances". I found entries in the "jobs" database table and
deleted those workflow jobs, and thought that that would be the end of all those
unwanted recordings.
Not so. It looks like "workflow instances" are kept in yet another index managed
by "lucene" and totally separate from filesystem mediapackages or the database.
I could find no REST call to delete a workflow instance. Is a "workflow
instance" just an expanded mediapackage by another name? Does it own the files
in the download and streaming directories too, or are those files separately
accounted for by some other index?
So as you can see by all these questions and my confusion about what really is a
mediapackage, why is it not the same as a recording, and what about other files
in the system that there needs to be some additional documentation and
information available to help new admins understand this system. A few
wiki pages on the directories used by Matterhorn, the indexes and databases used
by the various services, the main objects (mediapackages, workflow instances,
etc.) used by Matterhorn, ... , to reduce the learning time needed by an
incoming admin to get a handle on this system and figure out how to tailor it to
best fit the needs of his/her client base.
You already have some really nice overview tutorials on the site. I need the
next level.
Thanks for the support and feedback,
Hank
On Mon, 25 Apr 2011, Adam Hochman wrote:
Hi Hank,
I'll update the 1.1 FAQ to explain some of the issues you encountered.
Please note that there are known issues stated in the release notes that may
impact your 1.1 installation. There is also a blurb about storage in the
distribution installation notes that goes into more details about
Matterhorn's storage configuration. You may find it informative.
~ Adam
On 4/23/11 8:31 AM, Hank Magnuski wrote:
Thank you, I missed the fact that these were hard links (they are on the
same filesystem).
Hank
On Sat, 23 Apr 2011, Josh Holtzman wrote:
> If those two paths are from a single physical volume, those are two hard
> links pointing to the same file. So even though it looks like you have
> four
> files, they are really only taking up the space of two.
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
