lookit / lookit/lookit-api

Study 'exit page' - "Report" button and study rating button

Open
#1,057 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

TL;DR

At the end of a study, participants should see a screen that explains that the individual study is over, and they are interacting with Lookit/CHS again. Participants should be given the option here to 'report this study' if something has gone badly wrong.

Note: Need to sort out how this interacts with exit URLs, particularly for labs that use it to redirect to the second half of a survey!

Narrative

As the platform moves away from exhaustive centralized reviewing, we want to give participants easy ways to communicate when things are going well or poorly.

Feature Request fields

**With this `details` wrapper, you can just use this ticket to record your findings. When you're ready to turn this into an implementation request, delete the scoping label and this wrapper, leaving only the filled out information.**

Acceptance Criteria

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

  • Tests for new feature
  • QA on new feature
  • Sign off from Kim

Implementation Notes

Leave important notes/suggestions here for implementation (important files, suggested approaches, etc.)

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

No implementation files, tests, or entry points are named. First clarify the exit-URL behavior and define the screen, report action, rating action, tests, and QA needed; the issue is done when those acceptance criteria are explicit and implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.