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

Selecting germplasm during import: how to handle KP:GERM[stockID] as the uniquename? #12

Open
laceysanderson opened this issue Feb 9, 2024 · 0 comments
Labels
Group 0 - General Only for tasks that do not fit in another category. Group 2 - Data Importing Any issue relating to importing of biological data into either Chado or any other database.

Comments

@laceysanderson
Copy link
Member

laceysanderson commented Feb 9, 2024

This came up in review of the accession importer. I'm creating an issue to remind us to discuss it :-)

Recap / Brain dump from PR

Currently our uniquename/accession is KP:GERM[stock_id] which we cannot fill into the import template ahead of time since we do not know the stock_id until after insert. We have discussed that perhaps we should keep the primary accession as the original accession for that germplasm (i.e. genebank accession, cross number, RIL number) but what if we do not have an existing accession to apply (i.e. random seed from the grocery store)? Also, what about other sites which may want to stick with giving all germplasm their own unique accession? We'll want to walk through an example of how to get around this or test it to see what happens.

@laceysanderson laceysanderson added Group 0 - General Only for tasks that do not fit in another category. Group 2 - Data Importing Any issue relating to importing of biological data into either Chado or any other database. labels Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Group 0 - General Only for tasks that do not fit in another category. Group 2 - Data Importing Any issue relating to importing of biological data into either Chado or any other database.
Projects
None yet
Development

No branches or pull requests

1 participant