splitkeycoffee / split-key-roast Goto Github PK

There's a lot of additional fields that could be added to the inventory form. These should be added now, so they are tracked within the model.

• Tags
• Organic
• Direct Trade

Using the Flask development server is not ideal for production. Whatever technology choice is picked, there needs to be a packaged, easy way to deploy the code. Ideally, this would be created to run at boot on something like a Raspberry Pi.

Areas that need to be explored:

• Generating services on various OS
• Packaged VM that auto-runs
• Container services (likely not)?

This application will run locally, but there's a future to sync this with a remote platform. In order to support this concept, the user model needs to be updated.

• Add in a username field
• Keep a first_seen and last_seen time
• Potential data stub of order information?

Twitter is a good match for roasting where there's a lot of small updates in a brief period of time. Allowing a user to associate their API credentials and specify when to auto-tweet would make the roasting process social.

• Add an integration section to the account dropdown
• Allow users to enable/disable Twitter
• Save the user API credentials
• Allow users to check when to auto-tweet
• Configure events with a decorator to run post-processing
• Execute twitter calls on friendly events
• Test with a live account

Brewing is a less-robust way to collect feedback about the cup of coffee without a full cupping session. This should cover tasting notes for daily drinking.

Roast profiles are often geared towards a brewing process. Users should be able to check which brewing process the roast tastes best with.

Brewing methods to display:
Pourover, French Press, Espresso, Siphon, Cold Brew

After a roast is complete, a user should be able to email the results to themselves or someone else. This should include some basic roast summary and an attachment of the image.

• Add button to the historic roast
• Ask for the user email address
• Generate email summary
• Auto-save roast graphs
• Send email out

Roasts have several tracking points that can be derived from data. These should be added to the graph as a flag.

• Charge (ET)
• Turning point (BT)
• Drop (ET)
• Rate over rise

Cupping is a standard process after roasting. This should be added into the application following the SCAA guidelines.

Reference:
http://www.scaa.org/?page=resources&d=cupping-protocols
https://roastlog.files.wordpress.com/2010/08/scaa-form.gif