Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ClinEpi: add “Avg time to decision (days)” statistic to all studies table #36

Open
danicahelb opened this issue Mar 2, 2022 · 0 comments

Comments

@danicahelb
Copy link
Contributor

see https://redmine.apidb.org/issues/43222

“Avg time to decision (days)” → amount of time between submission and decision to provide access or reject

decision was made to calculate the "avg time" statistic based on history logs (there is no need to take into account information from access requests made prior to the history log system being in place)

The data will come from the end_users table and the new history table.
Initially we thought of a new service endpoint but given that this information will be shown in existing pages:

  • All Studies results table
  • Study page
    Im hoping these will be new attributes/table in the study record xml (SQL)

More details:
avg_time_request_response_days:
1- is days enough granularity? YES (danica slack Jan 31 2021)
2- are we only considering transitions from request to another state? YES (danica slack Jan 31 2021)
----We may also want to consider time to 1st response as an additional stat

@danicahelb danicahelb added b57 and removed b57 labels Mar 2, 2022
@dmfalke dmfalke transferred this issue from VEuPathDB/EdaNewIssues Apr 12, 2022
@danicahelb danicahelb added enhancement New feature or request b58 labels Apr 12, 2022
@danicahelb danicahelb removed enhancement New feature or request b58 medium cost labels May 19, 2022
@aurreco-uga aurreco-uga changed the title add “Avg time to decision (days)” statistic to all studies table ClinEpi: add “Avg time to decision (days)” statistic to all studies table May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants