Open lukeforehand opened 10 years ago
Additional field suggestions: Beer style Optimal cellar temp (maybe auto-populate based on chosen beer style value, if discrete) Brewed on (date) Brewed by (self, another user, null if commercial?, free text if non-user friend?) Bottled on (date) ABV Size/volume Container characteristics (basic, like style (standard bottle, growler, carboy, barrel, etc.); and/or details, like glass color and cover type (bottle cap, cork, etc.)... ? Free text field for comments, to record additional non-discrete info (how long to store, concerns about batch, origins, intended use/occasion, etc.)
What about other lower-level metadata, like ingredients (grain type/flavor, hop type, yeast type, etc. plus optionally amounts of each), original/final gravity, IBU, etc.? Also user activity - Date removed, removal reason/occasion (to trade, to gift, to drink, move to fridge (?), submit to tasting/contest, broken bottle, etc.)
good ideas for fields.
I think volume indicates the container well enough, that along with the photo field should be sufficient. I want to optionally include recipe in the cellar item metadata, perhaps only with homebrews to start. Recipe information for commercial items are difficult to come by.
I feel that homebrewers may have a different and more personal use case where they catalog their recipes and review a single batch of beer as it ages over time (verticals).
Cellar item activity should be recorded as much as possible, I think the main activities would be:
initial cellaring trading drink and review (helps to provide verticals)
fields:
fields that are globally unique need to pass validation before being indexed, to ensure the value is either scrubbed to fit into an existing value or is known to be a new value (we will store unique value dictionaries in a persistent cache)