If a contributor identified by 'john.doe@somewhere.org' is created by a DMP, the record is created with their current affiliation (assuming one was supplied).
If a subsequent DMP is created and a contributor identified by 'john.doe@somewhere.org', but with a different affiliation, then the system picks up the one from before and does not update the affiliation.
We need to decide on one of the following:
Stop recording the contributor's affiliation. That piece of information is variable (as is their give/sur name). We are capturing the 'Funded affiliation(s)' which may be enough.
Update the uniqueness validation so that the key is on affiliation_id + email/orcid so that we would have 2 separate contributor records in the above example.
Update the affiliation. This would mean however that when someone views the first DMP in the above example they would see the user's affiliation from the second DMP.
@mariapraetzellis do you have a preference? We need to weigh out the pros and cons
If a contributor identified by 'john.doe@somewhere.org' is created by a DMP, the record is created with their current affiliation (assuming one was supplied).
If a subsequent DMP is created and a contributor identified by 'john.doe@somewhere.org', but with a different affiliation, then the system picks up the one from before and does not update the affiliation.
We need to decide on one of the following:
@mariapraetzellis do you have a preference? We need to weigh out the pros and cons