Download project data

[DerekCaelin]

Once data collectors have gathered information about project sites and selected the correct site ID, allow the user to download the data about all the sites and incorporate into other proecess

References

• Spec - Project management
• Terraso web client download page

Designs

Figma

Design as of 4/23/2024 - please see figma for most up-to-date version

Legacy issues to review, edit/delete:

• https://github.com/techmatters/terraso-backend/issues/1105
• https://github.com/techmatters/terraso-backend/issues/1036
• https://github.com/techmatters/terraso-web-client/issues/1345

Process

### Issues
- [ ] Product task - write spec
- [ ] Product task - Write QA Tests using [template](https://docs.google.com/spreadsheets/d/1VDGNS5-xIaskU9lA5wreJkZ20P-G0qqfaJ3PsAIri04/edit#gid=2004954072)
- [x] Design feature
- [ ] Copy edut feature
- [ ] Engineering research - export CSV
- [ ] Engineering task - implement design
- [ ] QA
- [ ] Translation
- [ ] Usability testing
- [ ] Web Documentation

Acceptance Criteria

• [ ] As a project manager, I can click on a link others can click on to download site data
• [ ] The download will be a CSV file
• [ ] The CSV file will contain one row for each site. The columns will be:
  • [ ] Name of site
  • [ ] Latitude
  • [ ] Longitude
  • [ ] Elevation
  • [ ] Project name
  • [ ] Data Privacy
  • [ ] Best Match Soil ID
  • [ ] Best Match Ecological Site Name
  • [ ] Selected Soil ID (if available)
  • [ ] Selected Ecological Site (if available)
  • [ ] Slope
  • [ ] {each depth interval} cm <- repeat this for each depth interval
    • [ ] Texture
    • [ ] Rock Fragmentation
    • [ ] Color
  • [ ] Notes <- combine all notes, author, timestamp into a single field

[DerekCaelin]

Comment from Garo on 4/16:

• we haven't really started implementing (besides the existence of this button). i think it's worth talking over this again to get on the same page about expectations before proceeding with implementation, and it maybe won't fit into capri. some things that come to mind immediately:
• imo just having the small helper text saying "anyone with this link can view all assets" is not enough of a warning to users that want their data to be private that they're about to make it public.
• do we want the link generated to be obfuscated or canonical? (if it's canonical, the button can work offline, but not otherwise).
• the issue seems to imply that we cache this zip file, but it might be lower effort to generate it on demand