Open brianwdavis opened 2 years ago
Two components, both should be cards that render a summary instead of a table.
Farmer interview /raw?table=social_sciences_survey endpoint (needs to be activated in API)
/raw?table=social_sciences_survey
Field history /raw?table=farm_history endpoint (already active in API)
/raw?table=farm_history
Example, each card should show an individual page per row returned by the API.
producer_id: 2019AL07 crop_acres: 900 farm_crop_rotation: cotton peanut winter_cover ...
code: NVC previous_cash_crop: null next_cash_crop: null cc_planting_method: Drilled cc_termination_method: Herbicide ... cash_crop_variety: Dekalb 70-27 cash_crop_maturity_group: 120 day growth_stage_grains: Stem Extension growth_stage_legumes: Vegetative growth_stage_brassicas: Vegetative affiliation: VA year: 2021 producer_id: <XXXXXX> protocols_enrolled: null last_name: <XXXXXX> email: <XXXXXX> phone: <XXXXXX> first_name: <XXXXXX>
Putting the fields in the appropriate order is something we'll have to look at a prototype with @saseehav
Put this issue on ice. We think users need to be guided more for data validation
Two components, both should be cards that render a summary instead of a table.
Farmer interview
/raw?table=social_sciences_survey
endpoint (needs to be activated in API)Field history
/raw?table=farm_history
endpoint (already active in API)Example, each card should show an individual page per row returned by the API.