Enhancement: cohortdefinition/info/afterdate GET request
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 151
- Forks
- 183
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
Desired behavior
Simple mechanism to get listing of all cohort definition runs (optionally after a specified date).
This is meant to support operational monitoring and data governance of an Atlas instance - e.g. which cohorts and data sources are in active use.
Actual behavior
If want to know which cohorts were processed for which data sources, one must make repeated calls to:
WebAPI/cohortdefinition/{id}/info
When there are large numbers of cohort definitions, this can take quite some time.
Enhancement request:
- New GET request like WebAPI/cohortdefinition/info that returns all records of runs of all cohorts across all data sources.
- New GET request like WebAPI/cohortdefinition/info/afterdate that just returns the records of runs started after afterdate
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 the existing WebAPI/cohortdefinition/{id}/info endpoint and its response data. Determine how the proposed WebAPI/cohortdefinition/info and WebAPI/cohortdefinition/info/afterdate requests should return runs across all cohorts and data sources, including the afterdate filter. Done means both endpoints provide the requested operational listing without repeated per-cohort calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100