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
C. This is another exception I created while working on study doc conversion, but I realized that there is a search-ability issue. We added the Infusate, Tracer, etc name fields so that users could search using those names in the search field, but I noted that there exist separate records for the same infusates and tracers because a synonym was used in their name, which is "unique" in the model. So I figured, we can accept those names with synonyms, but when loaded, they should be converted to the primary compound name. That way, when they search for something, they get all results for that infusate/tracer, not just the ones with the specific synonym^.
^ I realize that the search interface needs to be able to search where it doesn't matter what synonym you use, but that's a separate issue. So the question is, do we list that as a caveat until that's fixed or convert all the names to use the primary compound - or change the primary compound names to the ones users are using in their infusate/tracer names. For example, palmitate is used in the tracer names, but the primary compound name is something like C:16 or whatever. In that instance, it seems like palmitate should be the primary name...
The text was updated successfully, but these errors were encountered:
hepcat72
changed the title
Make infusate and tracer name searches work regardless of compound synonym or tracer/label order
Make infusate and tracer name advanced searches work regardless of compound synonym or tracer/label order
Aug 5, 2024
C. This is another exception I created while working on study doc conversion, but I realized that there is a search-ability issue. We added the
Infusate
,Tracer
, etcname
fields so that users could search using those names in the search field, but I noted that there exist separate records for the same infusates and tracers because a synonym was used in their name, which is "unique" in the model. So I figured, we can accept those names with synonyms, but when loaded, they should be converted to the primary compound name. That way, when they search for something, they get all results for that infusate/tracer, not just the ones with the specific synonym^.^ I realize that the search interface needs to be able to search where it doesn't matter what synonym you use, but that's a separate issue. So the question is, do we list that as a caveat until that's fixed or convert all the names to use the primary compound - or change the primary compound names to the ones users are using in their infusate/tracer names. For example,
palmitate
is used in the tracer names, but the primary compound name is something likeC:16
or whatever. In that instance, it seems likepalmitate
should be the primary name...Originally posted by @hepcat72 in #1068 (comment)
The text was updated successfully, but these errors were encountered: