Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Same Record As to Relationship options? #8414

Closed
campmlc opened this issue Jan 9, 2025 · 3 comments
Closed

Add Same Record As to Relationship options? #8414

campmlc opened this issue Jan 9, 2025 · 3 comments
Assignees
Labels
CodeTableCleanup Our bad data leads to more bad data. Fix it! Function-Relationship

Comments

@campmlc
Copy link

campmlc commented Jan 9, 2025

          'same collection as' for UAM:Herb (3486 cases): this is an error on my part. I should have used 'same lot as'. The intention was to link a specimen at UAM with a duplicate (same Record Number) at another institution.  I will fix this.

As an aside, maybe we need a new 'same record number as' option? While 'same lot as' is correct ("individuals of the same taxon sharing the same collecting event"), it fails to capture the important and common relationship (for plants) that specimen A @ inst. X and specimen B @ inst. Y are 'duplicate' collections, and share the same dwc:RecordNumber. 'same record number as' would be a subproperty of 'same lot as'.

Originally posted by @camwebb in #8355 (comment)

@campmlc campmlc added Function-Relationship CodeTableCleanup Our bad data leads to more bad data. Fix it! labels Jan 9, 2025
@campmlc
Copy link
Author

campmlc commented Jan 9, 2025

@camwebb I've been wondering how plant collections deal with multiple herbarium sheets taken from the same plant and same collecting event but shared among different institutions. Is that what you are using "same record number as"? We've been using same lot as or same individaul as for similar situations. The latter would be used if parts of the same individual are distributed across collections or institutions, or in some cases, if the same individual was cataloged in both places but physically resides only in one. From a genomics perspective, it seems important to clarify when duplicate records reflect mulitple samples of the same individual. Otherwise, researchers may not realize these are not independent samples, and may include duplicates in loan requests to different institutions without realizing they are not sequencing unique individuals.

@campmlc campmlc changed the title 'same collection as' for UAM:Herb (3486 cases): this is an error on my part. I should have used 'same lot as'. The intention was to link a specimen at UAM with a duplicate (same Record Number) at another institution. I will fix this. Add Same Record As to Relationship options? Jan 9, 2025
@camwebb
Copy link

camwebb commented Jan 9, 2025

Dang, I just made a Discussion item on this 😄. There or here?

@campmlc
Copy link
Author

campmlc commented Jan 9, 2025

Let's go with your discussion.

@campmlc campmlc closed this as completed Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CodeTableCleanup Our bad data leads to more bad data. Fix it! Function-Relationship
Projects
None yet
Development

No branches or pull requests

2 participants