You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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-existent
YUN006 refers to identical YUN031, which is non-existent
PIE010 refers to 2nd-degree relative PIE009, which is non-existent
PIE06061 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
The text was updated successfully, but these errors were encountered:
@Mattists kindly notified me of the following entities in package
2023_Penske_EarlyContact
that refer to non-existent IDs in theirRelated_To
fields:YUN003
refers to identicalYUN049
, which is non-existentYUN006
refers to identicalYUN031
, which is non-existentPIE010
refers to 2nd-degree relativePIE009
, which is non-existentPIE06061
refers to identicalPIE061
, which is non-existent. I suppose this is a merged sample, so perhaps we should just move the entry to theAlternative_IDs
column?PIE071631
refers 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_IDs
field.Sandra Penske and @AyGhal can you advise here, please? I am happy to make a PR for this
The text was updated successfully, but these errors were encountered: