Fields to show user

[amp5]

How do we feel about returning the following bits of info to the user per plant:

• common_name - could be multiple names separated by | <- maybe get first one?
• image_url
• edible_part
• is_edible - is_vegetable - maybe not necessary if we have is edible?
• flower_img
• leaf_img
• habit_img - don't know what this image is yet. TBD
• fruit_img
• bark_img
• other_img
• fruit_color - in case they don't know fruit color
• toxicity

Let me know if you think we should get additional info

@devyboy @gideontong

[gideontong]

I like these. Let's build an API for this. I'll get started tonight. Expect some code contribution before standup tomorrow.

[devyboy]

I think we can toss the is_vegetable since that seems a little out of place? Everything else seems good to me, great work.

[gideontong]

Sounds good. Everything except is_vegetable

[amp5]

Not sure if we want all the images for each plant. It would depend on the f/e format. refer to #5 for current json format for f/e

[gideontong]

Can return n number of random images or all if not specified. Decreases size of return object.