Thanks.  I'll think about all of this, seeking that ever-elusive "aha!" moment.  :)

One new(?) idea I see in the above is transferring multiple morphs in one run.  That, in itself, is interesting.

Overall, I'm still not sure I see the benefit of merging data for multiple actors into any given datafile.  But I'll keep re-reading what you've posted.

My impulse would be to allow multiple source actor selections, rather than trying to scan the figure looking for appropriate parts.  Then I would just loop through the selections, checking for morphs of the same name, looking up the new datafile for each set of correlated actors.  This would require a bit more attention on the user's end, but would presumably be less code-heavy and less open to various flaws or errors.  And since the user has a choice, it's more flexible than automatically checking all the actors which might be involved.

So I need to think about this.  If I dive into something without having feeling that I have a good reason to be doing it, I'm likely to do a crummy job.  Okay, a crummier job.  :-P  I plan to try to do some cross-figure body morph testing, similar to that you and JoePublic have done, but I don't seem to have great figures to use to approach this readily.  I'll fire some up and see what looks good. 

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.