Ensure provenance of phenotypes recommended are given to the user
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 7
- Avg merge
- 2m
- Merged PRs (30d)
- 12
Description
It is important to make clear that the Study Agent is building off of other things, and not just wrapping it in an LLM. For phenotypes, the definitions are touchable and the phenotype recommendation service should help coordinate selection. There should be links to best practices and, if a phenotype, the link to where it was generated.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the Study Agent presents phenotype recommendations and where the phenotype recommendation service exposes definitions. Determine how provenance, best-practice links, and the link to the phenotype's generation source should be represented, then verify that recommended phenotypes show this information to users.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100