lookit / lookit/lookit-api

Upload tabular data corresponding to a Lookit Response object

Open
#792 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

Make it possible for researchers who collect or code data subsequent to a Lookit response to re-upload that data back to Lookit

# Narrative
What is the user story for this feature? the format should be as follows, e.g.:

As a Researcher, I can access data from a response that is both pre- or during-study (e.g. demographic, other in-Lookit response data) and post-study (e.g. coded looking time data, external study data)

As another Researcher, if a response's video data is available to me, post-study data is also available to me.

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 files, tests, or entry points are named. First clarify the upload format, permissions, relationship to Lookit Response objects, and how post-study data should be exposed; then define implementation locations and tests. Done should satisfy the agreed acceptance criteria, including feature tests, QA, and Kim's sign-off.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.