Bulk data upload

[mihai-sysbio]

User story
As a Training coordinator, I want to upload metrics for a given course, so that it shows up in the aggregated metrics in way that I save time.
As a Training coordinator, I want the TMD to validate the data that I’m putting into the system, so that the TMD can aggregate it without me having to work out what the problem is.
As a Training coordinator, I want to be able to adjust uploaded data in case there was an error or a mistake not caught by the content validation

• These metrics are: Quality metrics, Demographics metrics and Impact metrics.
• There are some nodes who collect and upload Quality and Demographic metrics together in one go and others do it separately. In Tango, this will not be possible - only one type of metrics at a time.s
• There is no requirement that this needs to use a CSV file.
• One way to handle this would be to parse the data in the frontend and rely on the API to send the data to the TMD, with the data validation happening in the backend.
• The bulk data set should only be accepted if all entries are valid

Sub-stories

• As a user, I can log in with username/email and password.
• I am recognized as an authorized user (such as Training Coordinator) for my node.
• I can add a new event for my node manually thought the UI.
• I can see if there are any issues while adding the event, such as incomplete fields, wrong field formats etc.
• I can see a confirmation that the event has been added successfully.
• I can edit an existing event of my node.
• I can see the course identifier created by Tango for the course I just added.
• I can upload bulk metrics data individually, for any type, in any order, at any time (as long as the associated event exists in Tango).
• I am notified of any errors in the data I provide before it is inserted into the database.
• I see a confirmation that the data has been added successfully.
• I can delete each survey data row, one or multiple at a time, for any metrics type.
• Tango will alert me if there are more metrics rows than event participants.

[pdmnyberg]

It might be a good idea to have a look at the current functionality and reevaluate this issue. Or we keep it as is.