Hey there! I’ve been enjoying playing around with Arabica over the last week and had some suggestions for your lexicons. I didn’t wanna spam your repo with potentially a bunch of issues, so I figured I’d just open one with them as a bulleted list and you can take them or leave them 😅
social.arabica.alpha.bean#
producer: Astringfield where you can put the name of the bean’s producer (e.g., "Rodrigo Sanchez", "Diego Samuel Bermudez”)- I’ve been using the
originfield to get as specific as the farm (e.g. instead of just “Colombia” or even “Huila, Colombia”, I’d put “Finca Monteblanco, Huila, Colombia” if I have that info). However, when you have even more detailed info like the name of the farmer/producer, it’d be cool to share it and it feels weird to do this in the “origin” field since it’s about a person and not a place. Maybe I’m overthinking that tho.
- I’ve been using the
elevation: Anintegerfield where you can specify the elevation at which the plants grew, in meters above sea level (masl). Just another piece of data that more and more roasters are including that it’d be fun to share with fellow coffee nerds.
social.arabica.alpha.brew#
coffeeAmount: This is currently anintegerbut, like a few other brew parameters, I wish it got precision treatment and was considered as tenths of a gram rather than whole grams. For espresso, especially, the difference between whole grams is pretty big!
Hi, thanks for the suggestions!
Starting with the
coffeeAmountissue, that is one that has been previously brought to my attention, but has been somewhat low on my priority to fix, since it is a breaking lexicon change. I think my plan currently is that I will make a change to an increased precision (probably just a tenth of a gram) when we move from the alpha lexicons to the release versions (although I don't have a timeline for this yet).For the bean lexicon, the design around it has been trying to give a lot of control over what can be included, while trying to prevent information overload in the entry form. I'm not really sure what the best balance is here, but I think producer might be getting a bit too specific to include in the form itself. My general thought is that more specific information than what the fields provide can be easily included in the
descriptionfield.(I'm not 100% decided on this though, since it would be cool to include really detailed info like this -- it might be worth exploring "add x" buttons to the form for some of the more specific info like producer, elevation, maybe even variety).