[Feature Request]: Create the ability for government users to upload AA drought CSV files for integration in PRISM

[wadhwamatic]

Provide a clear and concise description of what you want to happen.

Government partners have requested the ability to independently upload AA drought monitoring data directly to PRISM. We currently manage this at WFP HQ and periodically update CSV files as new precipitation forecasts come in during the monitoring season. Here's an example of an AA drought CSV for Malawi:
https://data.earthobservation.vam.wfp.org/public-share/aa/aa_probabilities_triggers_mwi.csv

I would like to build off of the current admin console work to facilitate this. We'd need to support the following steps (please note anything I missed):

1. Create a user role / permission to upload drought AA data
2. Authenticate user
3. Upload a CSV
4. Validate the CSV
5. Preview it?
6. Store CSV
7. Approve it / publish it
8. Have PRISM read from new CSV

Looking for your thoughts on this @ericboucher @gislawill @c-mac and to consider this use case while we're working on the current dashboard admin feature.

Is there anything else you can add about the proposal? You might want to link to related issues here, if you haven't already.

No response

[c-mac]

Extending our auth / role system to support this will be trivial.

For upload, will this be a feature for admin users, or need to happen in the public frontend as well? Easier if we just expose this through the admin site, but possible to build it in both places.

Do we want to follow the same paradigm as dashboards and support drafts?

Eric mentioned this in Slack, but as far as data versioning goes, do we want to just support having multiple CSV files for a given country, and have the API simply show the most recently updated, published CSV? Or just overwrite / delete the existing CSV?

Nothing in here is particularly hard to implement. The preview is likely to be the hardest part, which could involve custom extensions or views in starlette admin if we want the preview in the backend, or finding some kind of CSV viewing library (or simple data table) for React on the frontend, of which I'm sure there are many.

[wadhwamatic]

Thanks @c-mac for the input. Responses:

• I was expecting this to be in the admin console, not the PRISM UI
• Yes, we should support drafts
• I was originally thinking to just overwrite, but the suggestion to store text in a DB is definitely the better approach and if it doesn't add a lot of dev time, is preferred
• A simple data table preview would be great

[gislawill]

I definitely support the database-driven approach with a new endpoint that prism can use to pull the latest for the deployment.

@ericboucher noted validation in Slack and I want to flag that it will be essential. Validation with clear error messaging will allow gov't partners to find issues in a csv they update and will prevent them from accidentally bringing down the AA drought module.

Based on this, I agree that 2.5 days is a fair estimate.