lookit / lookit/lookit-api

Expand access to recruitment dashboard

Open
#604 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Medium Researcher
Dominant language
Python
Stars
12
Forks
21
Avg merge
5d 19h
Merged PRs (30d)
5

Description

# TL;DR
Allow researchers to access the participant analytics / recruitment dashboard view.

# Narrative
As a researcher, I would like to be able to evaluate the success of my recruitment strategies over time.

# Acceptance Criteria
A precise description of how/when this issue will be considered closed, e.g.:

- [ ] Researchers with access to participant data can see that data in the analytics view
- [ ] Participant analytics permission is preserved for Lookit staff who should be able to see all data in analytics

# Implementation Notes
Note that the analytics view is currently rather resource-intensive; it may need to be streamlined to allow for many researchers using it instead of just occasional use by staff. Carefully review DB calls and server-side processing.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the participant analytics view and the permission checks governing participant data, then review the database calls and server-side processing used by that view. Done means authorized researchers can see participant analytics while Lookit staff retain appropriate access, with the view usable for many researchers.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
analytics, api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.