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

Suport File Uploads: Front-end Element #29

Open
7 tasks
andrewstec opened this issue Aug 12, 2020 · 3 comments
Open
7 tasks

Suport File Uploads: Front-end Element #29

andrewstec opened this issue Aug 12, 2020 · 3 comments

Comments

@andrewstec
Copy link

andrewstec commented Aug 12, 2020

As an instructor, I want to be able to select S3 for large file storage on the pl-file-upload element instead of having files automatically saved to the database, so that students can effectively submit large file(s).

Requirements:

  • If file is over a particular size, make sure front-end passes information to back-end to store in S3.
  • Have option flag in HTML element to enable S3 storage upload
  • If a file is successfully selected, display a new HTML element to the user so that the user may upload another file
  • Put an option to limit the amount of files
  • Create a default limit to the number of files that may be uploaded (5 max.)
  • Additional file upload slots are not displayed once they hit their set or default max. limit
  • Put a front-end max file-size limit before sending file to the back-end.
@andrewstec
Copy link
Author

Notes:

  • pl-file-upload.py property appends the unique _file_upload_ string to any filename uploaded through the element. Thus, any pl-file-upload upload can be detected through the index match of the string.

@andrewstec
Copy link
Author

Uncertainties:

  • Do we want to upload an array of files for each UUID file partition? A file name and contents is already uploaded in an array for some reason. I am guessing this is the approach to go, as we can do one database query to look-up the appropriate files.

@andrewstec
Copy link
Author

Note:

  • A raw_submitted_answer and submitted_answer are both part of a submission file upload. Both currently get saved to the database. Both raw and submitted versions should either be saved or deleted. At the moment, I will save both of them. We can remove this after if we would like. I am not too sure how likely it would be for an instructor to want both of these files if one of them is modified, but it could happen.

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

No branches or pull requests

1 participant