Design Session Notes 09/23/2022
Miro Board Link
https://miro.com/app/board/uXjVPUWq7ps=/
Team Approval
Team approved of general architecture
Team approved of Trevor’s DB schemas
Team approved of shared CC observer pattern
DBs
We want dummy data in dev environment with the same seed as prod so that it’s obvious when testing that you’re on the dev site
Azure flex managed DBs instead of DB in kubernetes
Non CC Shared Data
Will determine at a later date
Languages
Mostly Spanish but could be others, 1 year timeline for Spanish
APIs
We want to avoid many nested calls, but having one or maybe two levels of nesting is fine
We want to get data on the front end and pass to the API to put the load on the user instead of the server whenever possible
Exporting Data
CSVs not needed
PDFs are needed, will need to revisit automated system for generating them at a later date
No other export needs
Ricks note about the PDF generation is below
I may be demonstrating this at today's meeting, but I need to document how I created the PDFs for the selector. I previously documented it at the original repo here: https://github.com/ag-informatics/covercrops/issues/146 Attached is a Windows batch file that creates the PDFs. It contains the species and zones at the time I created it.It assumes the program is running at http://localhost:3000/. After running the batch file, you would copy the files to *public/pdf*.This is my original hack for automatically showing crop details: https://github.com/precision-sustainable-ag/dst-selector/blob/main/src/App.js#L157-L167 At the time, the link was an anchor (
a
). It's now adiv
, but it still has the target attribute. So the hack can be:o.querySelector('[target=_blank]').click();
Since we're now using Redux, adispatch
would probably make more sense than my hack.
Action Items
See miro board for table of all action items
One additional it for Brian + Mikah:
Meet with Victoria
multiple root architectures?
root arch different between zones
Any other questions