Hi Stephanie,
> I'll have to work with this awhile, because sometimes .../search#DELETE/{id}
> removes the recording from the list and sometimes it does not.
>
> However, I already see that the Working File Repository DELETE mediapackage
> REST call only deletes elements from the media package, like track-1, then
> track-2, etc... It does not have the capability of deleting the entire
> directory. And, it won't let me use * to delete all the elements of a
> mediapackage.
I would consider it a bug if an empty directory is remaining after all
mediapackage elements have been removed. I would welcome if you could create a
ticket that details the calls that you made and the state of the working file
repository after these calls.
> Nor does it delete the workspace files. However, perhaps the workspace files
> are supposed to get deleted during cleanup after a successful ingest?????
That is more or less correct. If a service is accessing a file through the
workspace, it will download it from the workging file repository (It is
considered a best practice for service implementations to not access the
working file repository directly but do this through the workspace, because
then other services that need access to the same file will profit from the
download to a potentially shared filesystem, that just as an aside). The same
is true for removal, so if a service deletes a file from the workspace, it is
deleted from the working file repository as well.
As a consequence, if you find files lying around in the workspace that you
think should have been removed after processing (either successful or
unsuccessful), that should be reported as well.
Tobias
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
