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

Add completeness counts to subject sets #3450

Closed
eatyourgreens opened this issue Aug 18, 2020 · 3 comments · Fixed by #3649
Closed

Add completeness counts to subject sets #3450

eatyourgreens opened this issue Aug 18, 2020 · 3 comments · Fixed by #3649

Comments

@eatyourgreens
Copy link
Contributor

eatyourgreens commented Aug 18, 2020

For Engaging Crowds, we'd like to display subject set completeness when giving volunteers a choice of subject sets to work on for a particular workflow. It would be useful to have completeness, or number of completed subjects, recorded per subject set, if that's possible.

Here's a design for the project home page, showing how completeness will be listed for each subject set.
Screenshot of the project home page, showing a list of workflow subject sets with a percentage completeness for each one.

@eatyourgreens
Copy link
Contributor Author

One possible complication here: a subject set can be linked to multiple workflows, and will have different completeness counts for each workflow that uses it.

@eatyourgreens
Copy link
Contributor Author

There's also conversation on zooniverse/front-end-monorepo#1884, around how we'll want to list individual subjects from a set and show workflow status for each one, for the current user.

@camallen
Copy link
Contributor

Linking zooniverse/front-end-monorepo#1884 (comment)

One naive approach could be to do this when doing the project completion counts on the hourly schedule? https://github.com/zooniverse/panoptes/blob/e4dcb068ad39bddd960423ef6e794f9917e940ca/app/workers/calculate_completeness_worker.rb

I'm not sure what kind of load the above would add to the system, it might be more prudent to modify the set counts on each retirement event?

WorkflowRetiredCountWorker.perform_async(status.workflow_id)

Once those counts are on the SubjectSet resource we can serialize them via the API on the subject set resource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants