Possible idea for handling legacy sampleID<->determination

[kyule]

I could harvest them all and manually change just the occurrence relationship to something like "mayContain" "may originateFrom" or just "associatedWith" whatever makes the most sense for the problem samples and have the harvester only change relationships that were created by itself.

And then add relationships between the samples arising from the same parent (which I'd like to do anyways)
It doesn't solve the issue of duplicate records BUT it at least signals to the CMs that if someone is asking for a specific taxon you have to send both slides/vials to ensure they get it.

It would be a step in the right direction that I could implement without any major overhauls

And is forward compatible with when they start publishing the data correctly and the fact that the contractors were inconsistent, etc. without just shutting down reharvesting for the bad samples.