Hi,

I'm trying to work out how to thread two eprints so that I can merge the Accepted Manuscript record with Final published version, given that I have two separate systems feeding into the repository -  one feeding Manuscripts, one harvesting published metadata from PubMed etc.  I've looked at what happens when you create a linked new version of a record, with the <succeeds> set on the new record, and <metadata_visibility> set to no-search  on the old one. I'm in the slightly different position of wanting to merge two records once they are in the repository, but it seems like those are the fields I need to tweak.  I've looked at the code in https://github.com/eprints/eprints/blob/3.3/perl_lib/EPrints/DataObj/EPrint.pm 

to see the various in_thread manipulation functions, and can just about follow them. 

What I can't find is an admin utility that says 'Merge these two records, making this one the version of record, and retaining that one as an earlier version.'  Am I not looking hard enough?

What I might also want to do is to trigger this from the external systems, via SWORD, sending a couple of minimal XML packages to modify each of the records:

<eprints xmlns="http://eprints.org/ep2/data/2.0"><eprint id="http://blah.ac.uk/id/eprint/991329"><eprintid>991329</eprintid><succeeds>         991328</succeeds></eprint></eprints>
and likewise for the <metadata-visiblility> on the old record**
Does that seem like it ought to work?  It seems too easy.  Am I missing deeper layers of subtlety that are going to get corrupted by my naive approach.
Also, the eprint id is given twice in a standard eprint XML export, as per the edited code above.  Is it necessary to have both to trigger an update correctly?
Andy Reid
** (I say 'old record' but in reality the published versions may arrive before the manuscript versions, which depend on the authors sending them and us having the resources to process them ;-/ )