Changes between Version 2 and Version 3 of Ticket #77, comment 2


Ignore:
Timestamp:
Sep 28, 2019, 12:59:59 PM (5 years ago)
Author:
borja
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #77, comment 2

    v2 v3  
    331. 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.
    44
    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!'''
     52. 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'''
    66
    773. 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.