Changes between Version 1 and Version 2 of Ticket #77, comment 2
- Timestamp:
- Sep 28, 2019, 12:59:36 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #77, comment 2
v1 v2 3 3 1. Add a view to handle compressed files upload. Those files should be saved somewhere on the filesystem, associated with the user that uploaded them. Once uploaded, a message is shown to the user, telling him that workouts will be loaded soon. 4 4 5 2. Add a task to look for (new) compressed files, for any file found, uncompress it in a temporary directory, then call our load_workouts code on that directory. This task will have to be aware of who uploaded that compressed file, to add the workouts to the proper user. 5 2. Add a task to look for (new) compressed files, for any file found, uncompress it in a temporary directory, then call our load_workouts code on that directory. This task will have to be aware of who uploaded that compressed file, to add the workouts to the proper user. '''Important: load_workouts should take care of duplicated uploads too!''' 6 6 7 3. Add some code to the load_workouts module that saves some kind of a "report" with information about which workouts have been added from the load of that compressed file. That report should be kept around somewhere, so the user can go back and check which workouts were added when loading that compressed file (maybe we can have a button in the user profile page ``bulk upload reports``which loads a view showing the names of those compressed files uploaded and the relation with the uploaded workouts.7 3. Add some code to the load_workouts module that saves some kind of a "report" with information about which workouts have been added from the load of that compressed file. That report should be kept around somewhere, so the user can go back and check which workouts were added when loading that compressed file (maybe we can have a button in the user profile page ''bulk upload reports'' which loads a view showing the names of those compressed files uploaded and the relation with the uploaded workouts. 8 8 9 4. (enhancement) While the user has workouts pending to be added from that bulk upload, show in the UI (header? alert-like visible everywhere? we need a good idea here) telling him/her something like ```workouts loading: 3/10```or even a small progress bar.9 4. (enhancement) While the user has workouts pending to be added from that bulk upload, show in the UI (header? alert-like visible everywhere? we need a good idea here) telling him/her something like '''workouts loading: 3/10''' or even a small progress bar. 10 10 11 11 5. (enhancement) For now, we will pick up only fit/gpx files from the compressed file. This has the "drawback" that users cannot provide title/description/etc for each workout. Which is ok, as they can edit them afterwards, but we could accept a ``metadata`` file in the compressed file, where users could tell us basic info like title/descr for each workout. Then our code from load_workouts should look for that file and use it when adding those workouts.
