v3.2.0

[MAKOMO]

Artisan v3.2.0 adds the Batch Manager supporting the brand new Acaia COSMO roaster scales, a tear-off slider widget, and smaller bug fixes.

See the detailed release history for a complete list of changes and fixes

---

PLEASE FOLLOW AND TAG US!
                

---

This discussion was created from the release v3.2.0.

[beanoccio]

Does the Batch Manager only support the new Acaia Cosmo scales or other Acaia models?
I just tested it with Perl. It works perfectly. A great new feature!

I just tested it with Perl. It works perfectly. A great new feature.

I would like Artisan+ to have a consistent hierarchical data structure. I prefer a relational top-down architecture:

In this case, the data structure is consistent, flexible, and forms a consistent and infinitely scalable structure:
If I want to produce 100 units of Product 1 at 500g, I have a better overview of the inventory of roasted beans and the raw beans I need to procure.

[MAKOMO]

artisan.plus does not cover the inventory of roasted beans (yet) and thus does not cover post roast blends.

[beanoccio]

I think that, in terms of database structure, the distinction between pre- and post-blend is not necessary. (As can be seen in the example)

1 product consists of 1 ton of n roasts in percentages.
1 roast consists of 1 ton of n raw beans in percentages.

Whether the product is a post-blend or a pre-blend is determined by the number of records in the Roast Profiles subtable, or the number of roast profiles a product contains.

I think that as long as there is no table for products, it is not even necessary to distinguish between post- and pre-blend.

Only when you mix a product from different roasts does a post- or pre-blend arise. The product can contain roast profiles from 1 to n roasts. Roast profiles with 1 to n raw beans.

I hope that in the distant future, Artisan+ will also have a table for products. This way, you can create your products from different roasts. So, if you have to produce per month:
100 * Product A 500g
70 * Product A 1000g
30 * Product B 500g
70 * Product A 1000g
Then the database can immediately announce the required procurement of raw beans, labels, and packaging.

I understand my comment as an input for a brilliant product designer in Artisan + I'll create an example using an Access database using 3 Objects of TreeView.

[beanoccio]

In fact, it would be very convenient if Artisan+ had a Products table.
The product would then consist of one or more blends (roast profiles). The distinction between pre-blend and post-blend is no longer necessary. This is determined by the product composition.

My example is a solution with tree views. An excellent way to display such structures, provide a good overview, and facilitate efficient searches. It also provides quick navigation and a popular dashboard.

Just for inspiration!!!

TreeView.mp4