In short
The RUŌOD Lab app holds a material library as records grouped in collections, with typed fields for what every material needs, custom fields for what you add, and Formula Hub for values calculated from other fields. Set it up the way the data-model lesson describes — one record per material and grade, values with their sources, nothing derived typed in by hand — and the app's formula arithmetic will rest on records you can trust.
What you will learn
- Map the data model of the previous lessons onto the app's material records, collections and fields
- Decide when a value belongs in a typed field, a permanent custom field or a per-material field
- Use Formula Hub for calculated material fields and collection-wide aggregates
- Know what the app records and what it leaves to you
Before this lesson: A Data Model for Formulas and Materials, Build a Training Material Library
Before you start
This assumes the data model lesson and a training library. RUŌOD Lab is an Android application with no cloud sync and no AI; everything here happens on your device. What each plan includes is set out in the pricing section, and this tutorial says when a step depends on it.
Records
+ Material opens the editor. A record needs a name, a collection, a Primary Family and a Fragrance Pyramid position before it can be saved; everything else is optional. The typed fields include CAS number, botanical name, supplier, date acquired, quantity, cost, an IFRA limit, a Treat as Solvent switch, dilutions and a user custom code, plus a description.
- One record per grade. If you keep Hedione and Hedione HC, or an expressed and an FCF bergamot, make two records. A formula refers to one record; it cannot know which grade you meant otherwise.
- The IFRA limit is yours. The app ships no IFRA data. Record the limit for your product category from the current Standard, with the amendment and date in the description; the formula editor flags a line whose relative percentage exceeds it. A flag, or its absence, is not a compliance decision.
- Treat as Solvent marks a material (ethanol, DPG, a carrier) whose weight carries no fragrance; the calculations then exclude it from pure material.
- Usage is derived. A material's profile shows which formulas use it, worked out from the formulas themselves, so it cannot go stale.
Collections
Collection creates a named, colored group. Collections are how the list is organized and filtered, and how exports and reports group materials. A sensible scheme for research is one collection per supplier range or per study, not one per family: the Primary Family field already carries the family, and the list can be filtered by it and by pyramid position, and sorted by name, date, IFRA limit or quantity.
Fields
| The value | Put it in |
|---|---|
| Something every material has a value for, such as refractive index or flash point from the SDS | A permanent field: Tools → Material Fields |
| Something only one material needs, such as a natural's origin note | A per-material field: that material's Custom Fields → Add Field |
| Something calculated from other fields, such as cost per gram | A Formula Hub calculated field |
| A count, sum or average across the library | A Formula Hub aggregate |
Material Layout (Tools) arranges the sections a material is shown in: add, rename, reorder and hide sections, and move fields between them. It changes presentation only, never the data.
Formula Hub has three scopes. At material level it computes arithmetic over one material's fields ([Cost] / [Pack size]); an empty source makes the result unavailable rather than zero, which is the honest answer. Aggregates compute SUM, AVERAGE, MIN, MAX and COUNT across every material, where COUNT reports how many actually hold a value. Derived calculations build on saved aggregates. Disabling a calculation hides it from material views without removing it; deleting one is blocked while another depends on it.
What the app does not do
- It does not verify CAS numbers or identities; that is your record-keeping.
- It does not split naturals into constituents for allergen or restriction arithmetic.
- It does not track stock solutions as separate entities with their own dates; record a dilution as its own material if you need its history, or keep a stocks table outside the app.
Practical exercise: Rebuild your library in the app, then audit it
- Enter at least twenty materials in two or more collections, one record per grade, every IFRA limit with its source and date.
- Add one permanent custom field that matters to your work, and fill it for every material.
- Create one material-level Formula Hub field (cost per gram, for example) and one aggregate. Check three results by hand.
- Compare the app's records with the tables you built in the data-model lesson. List anything your tables hold that the app does not, and decide where it will live.
You have done this well if no two records share a grade ambiguity, every external value has a source, your Formula Hub results match your hand checks, and your audit note names the gaps between the app and your data model with a decision for each.
Common mistakes
- One record for two grades. Every formula using it becomes ambiguous.
- Typing a calculated value into a custom field. It will not update; use Formula Hub.
- Treating a missing limit flag as safety. It only reflects what you recorded.
Key terms
- Material collection
- In the RUŌOD Lab app, a named, colored group of materials, such as a supplier's range or a family. A material belongs to one collection.
- Permanent custom field
- In the app, a field defined in Tools → Material Fields that every material has, with its value stored on each material.
- Per-material field
- In the app, a field added from one material's Custom Fields section that only that material has.
- Formula Hub
- The app's tool for calculated fields: arithmetic over one material's own fields, aggregates over every material, and calculations derived from saved aggregates.
Knowledge check
Written and reviewed by the RUŌOD Lab team. This is general education, not legal, regulatory, medical or safety advice. Example dilutions and exercises are for learning, are not validated products, and have not been safety-assessed. Completing a lesson confers no qualification. How we check these lessons.