Effect of Storage Conditions on the Quality of Arbequina Extra Virgin Olive Oil and the Impact on the Composition of Flavor-related Compounds (Phenols and Volatiles)
Bibliographic record
Abstract
Abstract: Commercialization of extra virgin olive oil (EVOO) requires a best before date recom-mended at up to 24 months after bottling, stored under specific conditions. Thus, it is expected that the product retains its chemical properties and preserves its ‘extra virgin’ category. However, in-adequate storage conditions could alter the properties of EVOO. In this study, Arbequina EVOO was exposed to five storage conditions for up to one year to study the effects on the quality of the oil and the compounds responsible for flavor. Every 15 or 30 days, samples from each storage condition were analyzed determining physicochemical parameters, the profiles of phenols, volatile compounds, α-tocopherol and antioxidant capacity. Principal component analysis was utilized to better elucidate the relationships between composition of EVOOs and the storage conditions. EVOOs stored at -23 and 23 °C in darkness and 23 °C with light, differed from the oils stored at 30 and 40 °C in darkness. The former were associated with higher quantity of non-oxidized phenolic compounds and the latter with higher elenolic acid, oxidized oleuropein and ligstroside derivatives, which also increased with storage time. E-2-Nonenal (detected at trace levels in fresh oil) was selected as a marker of the degradation of Arbequina EVOO quality over time, with significant linear regressions identified for the storage conditions at 30 and 40 °C. Therefore, early oxidation in EVOO could be monitored by measuring E2-Nonenal levels.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".