Ah, yes. I'd have to look into it, but I believe this doesn't impact that bug either way. When we write the xml exporter for split mongo, we'll need to ensure we handle this correctly.

My hunch is that a current xml export of, for example, a parent whose children are [live-only1, both-live-draft, private-only, live-only2] results in the xml saying parent has [live-only1, both-live-draft, live-only2] but when we import private-only we know we need to attach it to parent, just not where.