Skip to content
This repository has been archived by the owner on Jun 24, 2024. It is now read-only.

Move adding students in a Roster to a background job #2210

Open
shaunakpp opened this issue Aug 8, 2019 · 0 comments · May be fixed by #2233
Open

Move adding students in a Roster to a background job #2210

shaunakpp opened this issue Aug 8, 2019 · 0 comments · May be fixed by #2233
Assignees

Comments

@shaunakpp
Copy link
Contributor

shaunakpp commented Aug 8, 2019

Feature request ✨

Currently, we when add students to an existing Roster, we do it within the request-response cycle. So if someone uploads a large .csv file or adds a large list of students, it takes a long time for the upload to happen. Also if there's a timeout or an error in adding those entries, we rollback all of them, which also takes a lot of time.

Moving this process to a background job would be a much better UX for the user and also reduce response times.

The steps involved in doing so would be:

  1. Move .create_entries to a background job.
  2. Setup ActionCable channel for sending progress report to the user.
  3. Handle invalid entries.

In the first iteration, we could move the process to a background job and just send a flash message on the lines of "We are adding students to your roster, please check in sometime".

And in the future iterations we can add the ActionCable support.

cc: @andrewbredow @d12

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

Successfully merging a pull request may close this issue.

1 participant