Cookbook¶
AgrEGG includes a feature called Cookbook for saving reusable analysis configurations. A cookbook entry acts like a stored recipe made of filters, Business Units, and period settings that can be reused later.
What a cookbook stores¶
The codebase shows that a cookbook can contain:
a name;
one or more filter items;
one or more Business Units;
a period type;
a period frequency;
a number of years;
an ordering value;
sharing settings with users or Business Units.
Why users would use it¶
Cookbooks are useful when the same analytical view is rebuilt repeatedly.
Typical use cases are:
storing a recurring analysis setup;
standardizing the filter set used by a team;
sharing a predefined analysis perspective with other users;
quickly recreating a dashboard context without manually selecting all filters again.
Creating a cookbook¶
The expected creation flow is:
start from an existing analysis context or create a new one;
choose the relevant Business Units and filter items;
define the time structure to reuse later;
save the configuration with a meaningful name;
optionally share it with selected users or Business Units.
The code also indicates that cookbook creation can be pre-populated from an existing context, which means users may be able to save the current selection as a recipe instead of starting from scratch.
Permissions¶
The implementation distinguishes between users who can view cookbook entries and users who can edit them.
In general:
some users may only browse cookbook entries available to them;
editing is typically limited to the creator or privileged users;
deleting a cookbook entry is also permission-based.