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
This 2 option categorical list is used both in NCBI and GSCID-BRC standards, but has different respective storage values for each option. How to handle this? Easiest way is to annotate the options as hasDbXref:NCBI:pathogen.cl or hasAlternativeId:NCBI:pathogen.cl (for example).
Favouring "hasAlternativeId" as the semantics are that given entity is known by a different identifier (or reference) in other system. hasDbXref semantics seems to be a bit broader - the cross-reference that an entity has in another database might not necessarily focus on the identifier piece of information, though that usually is instrumental to the dbxref reference.
Previously we had associated each option with respective standard via "member of", and supplied a different label/value that way, but want to get rid of "member of" functionality, and just provide one simple way to do this. On the other hand this leaves us with the problem of how to annotate user interface element qualities (label, definition, help info) specific to that standard.
The text was updated successfully, but these errors were encountered:
This 2 option categorical list is used both in NCBI and GSCID-BRC standards, but has different respective storage values for each option. How to handle this? Easiest way is to annotate the options as hasDbXref:NCBI:pathogen.cl or hasAlternativeId:NCBI:pathogen.cl (for example).
Favouring "hasAlternativeId" as the semantics are that given entity is known by a different identifier (or reference) in other system. hasDbXref semantics seems to be a bit broader - the cross-reference that an entity has in another database might not necessarily focus on the identifier piece of information, though that usually is instrumental to the dbxref reference.
Previously we had associated each option with respective standard via "member of", and supplied a different label/value that way, but want to get rid of "member of" functionality, and just provide one simple way to do this. On the other hand this leaves us with the problem of how to annotate user interface element qualities (label, definition, help info) specific to that standard.
The text was updated successfully, but these errors were encountered: