Many enhancements listed here are actions to be triggered on a past shot selected on DYE (re-upload to visualizer, export the data, delete the shot...) Nevertheless, that page is already crowded, so some UI must be added that does not gets in the way for standard usage but allows to increase the actions performed on shots.

My current idea is to put a "menu" icon on the top-left area that opens either a contextual or a full-page menu with all these options.

Having this working would be required for all those other enhancements.

I want to format date in "European way": dd.mm.yyyy but the field for date won't accept dot (.) input. I can tap it on the keyboard as many times as I want but it won't show up. Slash (/) however, does work.

Is it something with my tablet settings or did something change with the plugin?

Add tasting metadata to shots and the database. Departure point will be the score tasting sheets by James Hoffmann, with some additional dimensions.

Add UI page to manage this data.

The idea here would be to select any past shot in the Filter Shot History page and have the option to recover that shot parameters for the next shot. This would retrieve the profile that was actually used in the past shot, the bean and drink weights, and the shot metadata (beans, grinder, etc.).

So it would be easy to get some beans you already dialed in last year, search for the best shots you did with them (by enjoyment, EY...) and easily replicate them.

Use this new field in profiles and shots to:

• Filter profiles by beverage_type in the Filter Shot History page.
• Change the metadata propagation system so that data from last to next shot must match the beverage type (i.e. for an "espresso" shot, propagate from the last "espresso" shot, jumping intermediate shots if they are e.g. "tea portafilter" or "pour over" shots).
• Automatically interrumpt propagation (make all description values empty) for "cleaning", "calibration" and "testing" profiles.

Show an on-screen textual description of the profile used in any past shot. Integrated with the History Viewer or the Filter Shot History pages.

The idea would be to show something like in John Weiss' Python scripts, but from within the DE1 app.

Each user wants to fill different data fields. It would be good to have the possibility of personalizing the main DYE page so that those fields that are most interesting to each user can be put there, while others are relegated to secondary pages.

Of course, this would be a lot of work to implement. Some of my ideas is to go to a fully parametrized system for metadata entering, which would allow this type of customization and other things, but this is just an emerging idea that I have to really work out. Maybe some day...

Once the main additional metadata is added to DYE, I'm thinking of enabling some setting option to restrict the available input data to sets or fixed categories so that metadata can be used for data analysis. This will likely take a while, though. See Diaspora's Bayesian Bears' project.

The raw temperature data collected by DYE doesn't yet convert between Fahrenheit and Celsius, and since users can either set C or F in their machine, the raw data collected are not on the same scale and will cause issues in data analysis.

I found this looking at the histogram of the maximum espresso_temperature_mix series in Visualizer.coffee shots data, it shows that there's a bimodal distribution centered around 90 and 192, indicating that the former is temperature data points in Celsius and the latter in Fahrenheit.

@ebengoechea Could you convert all espresso_temperature_mix, espresso_temperature_basket, espresso_temperature_goal to Celsius if the machine data was set to Fahrenheit, especially before it automatically uploads to Visualizer.Coffee?

Add new beans metadata in shot files and in the database.

• Country, region, variety, producer. Multi-valued for blends.
• Bean batch: buy date, price, freeze/unfreeze dates, quality score, enjoyment.

Add UI pages to manage the new metadata.

Give the option to export individual shot data description and series (to, say CSV files). Or export the whole database to a CSV file.

Add "other equipment" metadata in shot files and in the database.

• New user-defined equipment items classified by type (tamper, basket, filter, etc.), each one with an optional setting.

Add UI pages to manage the new metadata.

Migrate from a DSx plugin to a (or several?) DE1app plugin(s), without losing any DSx functionallity.

To do that, first try to isolate and decouple DSx-specific functionallity. The objective is to have a skin-independent plugin. The idea is to use simple pages (single-color background, fontawesome icons and as little images as possible) that can easily adapt their general aspect (background, font & colors) to the skin in use.

Several users have requested auto-upload to Visualizer as soon as the shot is done.

This is already available on @Mimoja 's Visualizer extension, and I want to directly invoke her extension instead of having the upload functions inside DYE, but this will be done only when the extension goes out of beta and into the stable branch.

Also, for me to do auto-upload it is imperative that DYE allows to re-upload the shot to Visualizer when you change its metadata. Given the current UI, I don't see a clear way of including it in an already crowded page, so I'm waiting till I implement some way of triggering additional actions on shots (see issue #12).

@Damian-AU wanted to be able to search/filter past shots by barista. Given that screen real estate is limited and that page is already full, my idea is to make the two current category search listboxes assigned to "Profile" and "Beans" to be customized with a "dropdown arrow" so that any category field from the shots metadata (bean brand, grinder name, barista, drinker, etc.) can be used as a search criterium.

Capitalize on the fact than we now have a shot database to create a page that shows summary statistics by user-defined criteria.

Examples:

• Number of shots, total coffee beans used, total coffee consumed...
• By time period / profile / roaster / barista ...

Other ideas?