@Mattists kindly notified me of the following entities in package 2023_Penske_EarlyContact that refer to non-existent IDs in their Related_To fields:
YUN003 refers to identical YUN049, which is non-existentYUN006 refers to identical YUN031, which is non-existentPIE010 refers to 2nd-degree relative PIE009, which is non-existentPIE06061 refers to identical PIE061, which is non-existent. I suppose this is a merged sample, so perhaps we should just move the entry to the Alternative_IDs column?PIE071631 refers to identical PIE016, PIE031, which are both non-existent. I suppose this is again a merge, so I suggest to again move the two IDs to the Alternative_IDs field.
Sandra Penske and @AyGhal can you advise here, please? I am happy to make a PR for this
@Mattists kindly notified me of the following entities in package
2023_Penske_EarlyContactthat refer to non-existent IDs in theirRelated_Tofields:YUN003refers to identicalYUN049, which is non-existentYUN006refers to identicalYUN031, which is non-existentPIE010refers to 2nd-degree relativePIE009, which is non-existentPIE06061refers to identicalPIE061, which is non-existent. I suppose this is a merged sample, so perhaps we should just move the entry to theAlternative_IDscolumn?PIE071631refers to identicalPIE016, PIE031, which are both non-existent. I suppose this is again a merge, so I suggest to again move the two IDs to theAlternative_IDsfield.Sandra Penske and @AyGhal can you advise here, please? I am happy to make a PR for this