marker naming standard #3485
ClayBirkett
started this conversation in
General
Replies: 1 comment
-
This seems like it would be useful. Would it make sense to have a separate variant ID and then marker IDs, which are specific to a given platform/protocol? Essentially variant ID is like the accession name and marker IDs are synonyms for a given variant ID. Then marker groups could be defined for subsetting, which are lists of marker IDs that define a QTL or whatever else a user wants. I think GOBii has a concept like this in their GDM. Having some way to subset data across protocols would be nice. My current work around is to define new protocols that represent an intersection of one or more other protocols. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Find method to identify identical markers in nd_protocolprop table. For GBS markers we have many identical markers across protocols
create materialized view of nd_protocolprop table that uses a standard naming method for markers or
add new entry to nd_protocolprop table with new type_id
species + assembly + chromosome + position + ref + alt
benifits
Beta Was this translation helpful? Give feedback.
All reactions