In your shoes, if the existing command-line utils don't satisfy (namely, because you need to support exporting related objects), I would hack something against the REST API that, say,
1) given a PID
2) finds the appropriately related objects (presumably discoverable via the relationships API)
3) export PID + related objects using the migrate context
4) ingest into the target repo
If you need to do it a lot or the number of related objects is large (enough so that issuing multiple http requests presents unacceptable overhead), I would consider following the method I used in fedora-batch for a client so that more of the work is carried on server-side. Although this approach would require development in Java, the resulting REST end-point would be something you could of course hit with any http client.
On Oct 22, 2012, at 2:04 PM, Hugh Barnard <hugh.barnard@...> wrote:
> Hi Edwin
> Thanks for this. Yes, indeed and I should have read more assiduously/deeply, for others, it's here as a particular syntax of ingest: http://fedora-commons.org/download/2.0/userdocs/client/cmd-line/index.html#d0e164
> The migration style syntax of ingest doesn't seem to have an explicit migrate context, but I guess that's 'understood'.
> The particular thing that they want to move is a compound object [which is why it's a lot of work in the 'initial' repository!], so we'll see how it goes.
> Thanks again Hugh