If you’re a winemaker, a vineyard manager or viticulturist, or in a similar role, and if you have ten minutes to help a PhD student gather some data (and improve the state of research communication in the wine industry), I’d be most grateful for your response to this survey on your feelings about winemaking and growing information and where you go to find it. Find the completely anonymous survey here: http://fluidsurveys.com/s/winescienceinformation/
The Australian Wine Research Institute (AWRI) has launched a new winery service. Winemakers can now submit samples from natural/wild/native/non-inoculated ferments (or, conceivably, from an inoculated one if they wanted to) and, courtesy of “next-generation DNA sequencing*,” receive a profile of the yeast species present along with approximate percentages. An additional step can give them more specific strain information, and the AWRI can also isolate, freeze down, and store the main yeasts from your sample as “insurance” if you need them in future vintages.
This sounds like marvelous geekery. Winemakers who don’t inoculate probably wonder about what’s going on in there at least occasionally. What I’m unsure of is whether this yeast profile is a useful management tool beyond a fun way to satisfy your curiosity (or give even more detailed information to very well-heeled consumers). I imagine the following scenarios:
Good natural ferment — You like what’s happening with your uninoculated wine. You’re going to keep making it even if you learn that some generally undesirable bug has part of the action because you know you like the results. Maybe having a yeast profile sets you a benchmark so that if the ferment stops working in some future vintage you can send in a sample for comparison and see if the microbial blend changed, but how does that information then change what you do?
Bad natural ferment – You’ve tried not inoculating a wine and it isn’t working for you for whatever reason. You send in a sample from one that didn’t work (too slow, undesirable flavors, or didn’t finish fermentation). Maybe you’ll learn that some toxic bug is out-competing the yeasts you need to grow, or you’ll identify the source of that high volatile acidity you’ve been combatting. What then? The natural ferment still doesn’t work. Can you tweak pH or how much sulfur dioxide you use or your oxygen management to encourage more favorable microbes against the enemy? I don’t know how likely someone is to successfully adjust or amend a natural ferment to work better at that level — from the perspective of philosophy as well as how likely it is to work — but if you’re going to try these strategies, you’ll likely know to try them without knowing which yeast species are involved.
Planning a natural ferment – Maybe you run a test natural ferment to see whether you like what it does, and you want to “double-check” that it’s okay. The primary information you need stays the same: does it ferment to dryness? does it move fast enough to satisfy your economic needs and peace of mind? does it taste good? These will remain the primary drivers of your decision to move ahead or not, independent of what you learn from that yeast profile.
This service can help answer that perennial question of whether the yeasts in your “wild” ferment are really wild or just commercial yeast strains that have colonized your winery, and to some extent (especially if you go down to that extra strain level sequencing) the degree to which your ferment is different from some other winery’s. But the question — the AU $275 question for running a single sample, or AU $792 for the recommended panel of three samples per ferment — is this: will the extra information change what you do?
Nevertheless, forward-thinking actionability isn’t everything. Even if a winery never tries to replicate a previous successful wine by inoculating with its bespoke mix of strains banked through the system (that seems unlikely to succeed simply given the enormous variability in other parameters affecting wine quality directly and indirectly via influencing yeast growth), a retrospective look at yeast mixes in multiple vintages of the same natural ferment could be interesting. Did a change in viticultural management practices, or source of grapes, or fermenting conditions correlate with a clear change in microbial populations? That prospect makes me hope for two things. First, that a winery (or a dozen or two) will use this as a tool for looking back at the path they’ve taken and not just down at where they’re standing. Second, that when they do, they’ll share.
*Next-generation DNA sequencing (this introduction from Nature is dated and technical, but it’s also open-access; the article on Wikipedia is also quite good) is a collection of methods so called because they rely on new strategies for sequencing DNA — not just tweaks of the old traditional way, but really new ways of solving the problem — that let us do things differently, faster, and more efficiently. The most important things to know about next-generation sequencing are that, 1) it’s not a method, but a general term for a whole bunch of methods; 2) the idea has been around since 2008, which doesn’t mean that any of those methods can’t be cutting edge but which does mean that they’ve “trickled down” to the general market by now; and 3) they allow for pulling many sequences from many different organisms out of a single small sample. Old sequencing methods required a relatively large sample of (preferably) a single pure target sequence or else the signals would get so jumbled up that the whole instrument read-out would just look like soup (as I recall well from my first sequencing experiments as an undergrad in 2002-3). Now, we can sequence even single stretches of DNA, and even many different single stretches all hanging out in the same sample from some real-life microbe-rich setting: soil, seawater, or an active ferment. And we can do it quickly and inexpensively enough, now, to offer it as a commercial service. Remember those predictions about what genomics would bring us back around 2000, when sequencing genomes really hit the news? We’re getting there.
A few years back, a group of Auckland-based researchers established that machine-harvested Marlborough sauvignon blanc has higher aromatic thiol concentrations = tastes more intensely Marlborough sauv blanc-y = is better than wine from hand-harvested grapes. I don’t know how widely that logic is known amongst wine consumers, in New Zealand or elsewhere. Reading back labels in my local wine shop makes it clear that the hand-picked grapes = superior wine logic rules in the minds of marketers and, if they’re any bellwether (a worthwhile question), at least some consumers.
Marlborough sauvignon blanc aside, is that prejudice justified? My January piece for Palate Press addresses that question. The short answer is that hand-harvested grapes are in many settings more about feeling good about purchasing genuine artisan wine than about quality or flavor. The longer answer is here.
Saying that hand vs. machine harvesting is becoming less and less of a quality issue, with better equipment in the field and in the winery, isn’t the same as saying that the difference doesn’t matter. It does, to our perceptions of what we drink. But it’s also impossible not to see this as one more instance of Robots Will Take Our Jobs, and a particularly hard-hitting one with wine such a cultural icon. A lot of vacuous dithering takes place in the media around this topic (even in outlets like The Atlantic, though this piece from The Economist might be an exception) and, to be honest, I’m not sure that I have anything worthwhile to add. We’re headed, I think, for a major shift in how people work, earn money/obtain necessary resources, and spend their time. That shift may come in the form of an organized political (maybe governmental, maybe by large companies) decision to redefine work and money, or it may come as a necessary post-degenerate organic movement after the fall of Rome. Either way, being human, we’ll continue to find meaning in our work whether that means choosing to harvest grapes by hand because it’s meaningful to do so, even when a machine/robot can do a better job, by redefining wine quality such that the robot can’t do the job as well, or by understanding human winemaking as a conceptual art independent of the physical work of our hands.
Cold soaking seems to be an especially divisive winemaking technique, at least in the Pacific Northwest, and that’s saying something in an industry full of strong personalities. Cold soakers say that allowing crushed red grapes to rest for one to several days in an environment too cold for Saccharomyces activity, before warming everything up to yeast-pleasing temperatures and allowing fermentation to begin in earnest, deepens color and augments flavor and tannin extraction. The anti-cold soak camp claims that these benefits aren’t real and sometimes adds that cold soaks allow for the dangerous possibility — dangerous, that is, if you’re also in the anti-spontaneous ferment camp — of illicit microbial growth before winemakers inoculate commercial yeast strains at the soak’s end.
Research to date has been unhelpfully mixed. Some studies show increased phenolic (color and/or tannin) extraction, some don’t, some even show lower phenolics following cold soak, and the variables responsible for the differences haven’t yet been worked out. Adding to the confusion is the inevitable mess that follows pro-spontaneous from anti-spontaneous fermenters, since the non-Saccharomyces activity that might occur during cold soaks is a source of desirable complexity to some and unconscionable spoilage to others.
I would love to say “until now” and herald the arrival of a brilliant, conclusive paper outlining a robust explanation for how and why and where and when cold soak works. My inability to do so isn’t likely to come as a surprise. Nevertheless, there is new research and, while far from once-and-for-all conclusive, it helps, if perhaps not in the expected way. A new study from an Argentinian team* tested cold soak on cabernet sauvignon, merlot, syrah, pinot noir, malbec, and barbera d’asti, looking for differences both when the wines were pressed and after a year of bottle aging. Cold-soaked wines saw four days of 6.5-11.5ºC (44-52ºF) courtesy of periodic dry ice additions, then 10-day fermentations at 21.5-26.5ºC (71-80ºF); control wines went straight to 14-day fermentations. All varieties were made in the same way: same full twice-daily pump-overs, same twice-daily punch downs. All were inoculated with the same commercial yeast strain five hours after crush. Regrettably, the study didn’t include multiple variations on the cold soak theme — different times, temperatures, or techniques — that might have helped to suss out where any cold soak differences are happening and given much more information to winemakers. In particular, it’s important to emphasize that chilling with dry ice meant as much as a 10ºC (18ºF) difference in temperature between different parts of the tank because the dry ice clumped. Jacketed tanks would have applied a more uniform treatment.
The agglomerated results were straightforward enough. Cold soaks increased color density, but didn’t increase phenol or tannin concentrations. Cold soaking also didn’t make a statistical difference to any basic wine chemistry parameters: ethanol concentration, pH, acids, glycerol, and residual sugar. Tasters found that the most important difference between all of the wines was driven by grape variety, though that’s hardly meaningful and says nothing about cold soak. That’s the big picture.
The details in the supplemental data attached to the main paper show something more interesting. Each variety responded a bit differently to the cold soak treatment. In the barbera and the syrah, tannin concentrations actually were higher in the cold-soaked wines. The opposite was true for the pinot noir, where cold-soaked wines measured tannin concentrations statistically significantly lower than the control. Cold soaking related to increased total phenols in cabernet, decreased in pinot noir.
What this says to me is that we’re measuring the wrong construct at the wrong level of detail. Asking whether “cold soak” works seems to be the wrong question. Instead, we need to be testing out different potential cold soaking parameters in specific grape varieties to identify what precisely makes a difference and what is moot. This is the kind of data that could really help winemakers who through the lens of their communal experience are saying that cold soak sometimes makes a noticeable positive difference and sometimes doesn’t, and who might reasonably look to science to help them figure out what features separate the worthwhile instances from the useless ones. Unfortunately, if the research question continues to be “Does cold soak increase phenol concentrations?” instead of “Under what conditions does cold soak make a difference to phenol concentrations?” we’re likely to continue seeing confused yes-no-or-maybe reports instead of useful, applicable explanations of what winemakers seem to observe.
My Palate Press piece for this month (which I really wish was entitled something involving “water” to make the subject more clear) is a bit about Waiheke Island, just off the coast of Auckland, and a bit about water footprints in the wine industry. The relationship between the two is that Waiheke — shockingly, for a North American accustomed to consistent public amenities like central heating and easy wi-fi (both unlikely propositions in New Zealand) — has no public water supply. In good years, residents and businesses and wineries meet their individual needs either by collecting and filtering rainwater (most folk) or with a “water bore” into the under-island aquifer (large and/or resource-full folk). In bad years, all of the above buy water from private companies with private water bores, and do laundry less often.
Waiheke is a good reminder, though, that whether water comes out of a tap or off the cistern parked next to your car, it’s always coming from the same two places: the sky, or underground (which isn’t to say that the two aren’t connected, but only that it’s helpful to think of the two compartments). Tap water is a bit like packaged boneless skinless chicken breasts from the grocery store. Someone else has done all of the hard work for us. Both distance us from the hows and wheres of the stuff we use. Butchering chickens is a pain*. It makes endless sense to divide labor, specialize, and let someone else with better equipment and skills and economy of do it for you. And bake your bread, change your car’s oil, and collect and filter your water. Still, all of these things make it easier to abuse the system. We don’t pay as much attention to our dinner’s living conditions when it didn’t live with us before it appeared on the table, nor to how it died if we didn’t kill it. I’d never really thought about water that way before wandering around on Waiheke; I try to conserve it, but I don’t usually think so graphically about what my convenient kitchen faucet implies. I’d never wish drought on anyone (and California and its people have my sympathy). But maybe it’s no bad thing to look for a drinking fountain in a place with no public water and find none, and remember that I should be just as conscientious about my water as I am about my free-range, local, organic Sunday supper.
More about my Waiheke visit, and about water, is on Palate Press.
*As I know from recent experience. The Great Chicken Experiment is, regrettably, over. The first two hand-me-down hens lived happily with us until the neighbor’s rooster discovered them and decided that they were his, after which they lived happily with the neighbor until she decided she was done with poultry and she invited me to dispatch the lot of them (after which they lived in my freezer and my stockpot). Save the (charming, darling) several month-old chicks, who we adopted. Unfortunately, having been raised entirely outside in our mostly fenceless environs, they’d learned to be very freely free-range. A trip through someone’s spinach was more than anyone was willing to tolerate (save, maybe, the chickens) and we handed them on to someone else. We miss them, though my garden does not.
Scenario #1 – You’re sitting next to your fire after dinner, relaxed, with a few ounces of fine Canadian or German icewine, maybe a few slices of blue cheese and a ripe comice pear, and the current evening reading book. You enjoy all three for an hour or so and retire, happy and sleepy, to bed.
Scenario #2 – You’re sitting next to your fire after dinner with a few ounces of icewine and an active mind in search of a target, maybe two active minds if you have a companion. Conversation turns to the wine, how desperate those first Germans must have been to salvage their inadvertently frozen grapes and how arduous and expensive repeating the process on purpose now is. You speculate that cutting real icewine with something else must be mighty tempting, and the gaze you cast on your glass turns wary. And then you cast your gaze on Google and find this new article in the American Journal of Enology and Viticulture on a new strategy for testing the authenticity of icewine.
Icewine production is very expensive and no International Body of Icewine Authenticators polices producers to ensure that they’re doing it right or in good faith. Canada produces the bulk of the world’s stock (though I also enjoyed some fine examples in the Finger Lakes, not too far south of Ontario), and the Canadian Vintner’s Quality Alliance (VQA) legislates use of the term: a Canadian bottle with “icewine” or “ice wine” on the label must be made from approved varieties, from grapes harvested during “sustained” temps of at least -8°C, naturally frozen on the vine, coming in at at least 35°Brix, with no added sugar or alcohol, all overseen by a VQA representative. European producers employ similar standards, but the Asian sweet wine market is apparently well-populated with “Iced wine” and other unauthorized and fraudulent variations on the theme. Having a reliable means to verify that an “icewine” is really icewine made from frozen grapes seems prudent.
Per Armin Hermann’s new research, tracking oxygen isotopes could be that way. The idea is clever and conceptually simple. When grapes freeze, water partitions unequally between the part that turns to ice and the part that remains liquid. That’s the point of icewine: more water freezes, leaving sugars and other dissolved molecules concentrated in the syrupy liquid that remains. The naturally occurring isotope 18O, present in the water, will also distribute into the frozen and the unfrozen parts unequally. Since the frozen ice is more or less excluded from what ends up in a bottle of true icewine, then, icewines will contain a characteristic amount of 18O. All we need to do is determine — theoretically, using mathematical equations, and empirically, by measuring a bunch of icewines — what the “icewine” versus the “not icewine” 18O ranges are. Simple, elegant, and probably effective.
The plots of 18O measurements Hermann created show what looks like reasonably convincing separation between the ice- and non-icewine samples (understanding that judging how convincing is outside my expertise). BUT, there are two important caveats. First, the comparison was lab-frozen grape musts against the unfrozen originals. Again, it’s simple: “Frozen grapes, when pressed, will produce a must that is always depleted in 18O relative to its marc and also to their unfrozen counterparts.” The study didn’t include creating a database of icewine samples from various regions to establish reasonable 18O ranges. That’s solvable in theory, though the success of the whole method still depends on finding good, clear separation between real live ice and non-icewines.
Second, the method provides no way of determining how the wine was frozen. The 18O-depleted wine could have just as easily been frozen after harvest, in the winery, illegally. So, no matter how successful that empirical database is, the method won’t perfectly solve the how-do-we-detect-fakery problem. It is, as Hermann notes, an “additional” means giving a “strong indication” of authenticity. I wonder: is there a detectable chemical difference between the kind of slow freezing that would happen naturally on a grapevine in a cold Ontario winter and fast winery cryofreezing? Until then, looking for the Canadian VQA mark on the bottle — and avoiding anything labeled “iced wine” — remains the safest option, North American privilege notwithstanding.
My favorite Thanksgiving pairings are pinot noir with Burgundian leanings and sparkling brut rosé. (I’m not aiming for points on originality here). Since I’m a member of the drink-American-on-Thanksgiving club, the pinot noir is likely to lean Burgundy without actually being so in the form of an Oregon pinot noir that remembers that Oregon isn’t California. The sparkling is likely to be Schramsberg if I can get it and Ch. Ste. Michelle if I have to share. That being out of the way, my favorite Thanksgiving pairings have everything and nothing to do with what’s in the bottle.
Growing up, dinner came in two general forms. “Dinner” was eating. I was sometimes allowed to bring a book to the table (don’t judge), my parents talked about business or watched the evening news, and we didn’t have wine. “Nice dinner” was dining. We lit candles. We had wine. The conversations were longer, more thoughtful and, silly or serious, involved more stories. “Dinner” could be over in 45 minutes. “Nice dinners” sometimes took three hours. I blame the wine.
Thanksgiving (and Christmas) was the paragon “nice dinner:” just the three of us, the nice plates, and a meal that took most of the day and a spreadsheet to prepare — because what is Thanksgiving but an excuse for excessively social cooking for a family that doesn’t watch football and does own three mortar-and-pestle sets? And definitely wine. We sometimes thought about a movie afterwards, but as often as not we just talked and listened to music until everyone was warm and sleepy and full of pumpkin pie and single malt and ready for bed. Again, I blame the wine. And the single malt, but mostly the wine.
Thanksgiving and nice dinners have everything to do with science and science communication. I remember the evening when my father first explained color spaces (a fundamental element of color theory) to me. I was somewhere in the second half of my teens and I’m pretty sure the bottle on the table was a Dr. Frank merlot from New York’s Finger Lakes, because that was our house red at the time. We talked about F-stops or the zone system, how sub-woofers work, the finer points of gardening or birdwatching. Later, we talked about my research and I practiced science communication on my father, for whom “cell” was more likely to refer to a battery than a bacterium. Sometimes we were mundane and just rehashed old stories. We always talked about the wine at least a little.
I’m sure that I would have been interested in science and communication and maybe even in wine without those dinners. But “nice dinners,” and holidays especially, were the crystalline form of the stuff that taught me to be inquisitive, to value good conversation (and to hold up my end), and to understand why wine isn’t just about flavor and definitely doesn’t need to be about prestige. Good wine meant good conversation, and good conversation means everything.
I’m all in favor of thoughtful wine and food pairings that reveal exquisite and otherwise-unseen elements of each, or even simply pairings that taste good. But the absolute best pairing with Thanksgiving is just wine, whatever wine makes space for conversation, whether at a quiet table for three or a potluck affair for thirty. Because that, not an exquisite flavor experience, is the wine’s real job.
Having a spare two days in Auckland last week, I paid an all-too-short visit to Waiheke island which — thankfully, if you’re like me and are always looking for an excuse to get out of a big, crowded city — is only a pleasant 40-minute ferry ride from downtown. While the island is still best known for Bordeaux-style blends, syrah has of late become the island’s new darling. So, as it will when wine science geek meets winemakers in a spicy red zone, rotundone came up.
Rotundone is, quite fairly, one of the better known contributors to wine aroma. Unlike so many other more or less mysterious molecules, rotundone produces a specific, distinct, and very characteristic aroma: the black peppery note we associate strongly with Syrah (or Shiraz, if you’re speaking Aussie). We’ve only had specific evidence of that rotundone-pepper-syrah correlation since 2008, when an Australian group identified the compound, showed it to be the heretofore most powerful wine aroma compound (i.e. the one with the strongest impact at the lowest concentration), and demonstrated that 20% of their experimental syrah-drinkers couldn’t smell it at all even while the other 80% were being overwhelmed. In 2008, it was “an obscure sesquiterpene.” Six years later, I had a winemaker ask me whether there was really anything more to learn about rotundone.
Two articles have been published on how rotundone develops in the vineyard in 2014, both from Australia (including researchers involved in the original rotundone research), both confirming that viticultural practices and vineyard conditions generally can affect rotundone concentrations. One, working from a precision viticulture stance, gave evidence that rotundone concentrations vary across a vineyard in ways that might be related to how soil differences and topography affect temperature. The other showed that rotundone concentrations decreased with leaf pulling (which increases grape sunlight exposure and therefore temperature) and increased with irrigation; dropping unripe clusters (as growers do to control yields and even out ripening) didn’t have an effect.
The winemaker’s point was: “Um, duh? We knew that already.” Whether or not he could, in fact, have predicted all of the details of these experimental results matters less, I think, than that he perceived the research as useless. Vineyards on Waiheke aren’t irrigated. The estate vineyards with which he deals are small enough and local enough for him to walk and taste regularly, observe when and where the peppery flavors he wants (or doesn’t) are happening, and give picking orders accordingly. None of this rotundone research changes what he’s going to do in his vineyard so, to him, it’s pointless.
His comment highlighted a question increasingly on my mind of late. Who is wine research for? It’s obviously for scientists, and there’s nothing wrong with that: knowing about the world is a worthwhile goal on its own merit apart from any specific practical outcomes that knowledge might have, and long live basic research. Scientists and the community at large say that it’s for the benefit of “the wine industry” and, in part, that’s true. For a large operation manufacturing a specific wine style calling for a “dialed in” level of pepperiness and relying on fruit from many vineyards, that rotundone research might change things. Maybe they think about calling for a different leaf plucking regime on some of their syrah vineyards that aren’t quite meeting quality targets. But is the research for small producers, like this skeptical Waiheke winemaker? Call him provincial or even selfish for thinking that research doesn’t continue to help “us” understand more about rotundone, but he still knows what he needs to do to make a syrah that, by all indications, sells like roses on Valentine’s Day, out his cellar door, at prices that folks without the million-dollar views find hard to justify.
The syrahs I tried, at Mudbrick and Obsidian, were pretty convincing. Both relied more on freshness than power to make their case and certainly didn’t lack for rotundone, even minus irrigation and with leaf plucking common across the island. Obsidian’s 2013, carrying enough fruit and tannin for its lightness and brightness to be delightful and refreshing (and a pleasant alternative to the overpowered, clumsy or pretentious syrahs too easy to find in many New World climes), would accompany a sweaty Waiheke summer afternoon as nicely as a grilled lamb chop.
Is there anything more to learn about rotundone? Unquestionably. But, maybe, the more pertinent question for a Waiheke winemaker is whether there’s anything more to be learned about making well-balanced, pleasantly but not overpoweringly peppery syrah. Realizing that those two questions are in fact different is key, I think, to furthering both goals.
My piece for Palate Press this month asks what California (proto-Davis) wine researchers were doing in the era before mass spectrophotometers and DNA sequencers and even automated pH meters and all the other fancy stuff wine scientists consider essential today. The short story is that they were trying to figure out what grows best where, and how, which is fundamentally what we’re still trying to do. The long story is on Palate Press.
The long story didn’t have space for me to really geek out over the fun of reading old research articles. I think it’s fair to say that science writing — of the by scientists, for scientists variety — wasn’t as dry then as it is now, not just because antiquated language is quaint but because the distance between normal-talk and science-talk was shorter then than it is now. It’s pretty accessible and often entertaining. There’s the simple, voyeuristic pleasure of being astonished at just how backward they sometimes were, and sometimes at realizing that they weren’t as backward as we tend to assume. And then there’s the higher-order pleasure of making stories by connecting what they were doing to what we’re doing and finding new meaning in both the historical and the modern.
But reading about someone else geeking out over light archival wine reading isn’t near as fun as doing it yourself, and the archives of Hilgardia: a Journal of Agricultural Science from the University of California, including much about wine, are freely available via the University of California Agriculture and Natural Resources Respository. When so much is pay-walled and protected, free access to land grant university resources — not just for subscribers, not just for local winemakers, and not just for the taxpayers of California or even the United States — seems increasingly meaningful, and a good reminder of this massive, excellent, egalitarian knowledge-sharing project we practice through land-grant universities and agricultural extensions. I won’t ask you to excuse my unfashionable patriotism.
I’ve recently been reading piles of wine science communication texts: viticulture and enology extension newsletters, research articles in Wine Business Monthly and Wines and Vines, and university press releases and news items, among others. Many, many of them exhibit the same dysfunctions: the data sandwich, the shape-shifting audience, and inconsistency in rhetorical framing.
Those are three different ways of referring to the same problem, but each addresses a different audience. “The data sandwich” takes the point of view of the reader. The shape-shifting audience speaks to the author. Inconsistency in rhetorical framing appeals to the researcher. If I wanted to exemplify the problem, I’d now define “data,” “audience,” and “rhetoric.” And then I’d launch into a number- and jargon-laden discussion of how my data illustrate that many science writers (scientists in particular, though by no means scientists alone) don’t hold on to a single picture of who their readers are and what those readers know while writing a piece from beginning to end. And then I might conclude by saying that my data suggest that this is a concern of which it’s worth being aware.
Many science-focused articles begin with big, broad, contextualizing statements about wine. The rest of the first paragraph or two introduces concepts and defines terms with which someone who’s been working in the wine industry for a while — or who took a chemistry or microbiology class in their V&E associates’ program, or who read Wine Business Monthly on and off last year — probably feels pretty comfortable. Having set the scene, the author, somewhere around the third paragraph, begins describing their recent research project as though they’re talking to the guy in the lab down the hall instead of the person they were talking to a paragraph ago who’d never taken Wine Chem 101.* Two to ten paragraphs later, when the details of that project have been exhausted, the author concludes with a paragraph or two about how it all means that we should be aware of something, or that whatever-it-is is more complicated than previously thought and very important.
Let’s say we’re writing about new research on anthocyanin development in the vineyard. In the first paragraph, I’d describe why red grape color is important in winemaking. In the second paragraph, I’d define “anthocyanin” as one type of a class of molecules called phenols and describe how anthocyanins are mostly responsible for red wine’s color. In the third paragraph, I’d begin talking about how empirical evidence has recently demonstrated that deficit irrigation may intensify color density in Australian Shiraz not only by upregulating anthocyanin synthesis via unknown mechanisms but also by stabilizing the flavilium form of specific anthocyanins via hydrogen bonding with flavanols whose biosynthesis is also upregulated**, and I’d keep that up for a while. I’d finish either with a short paragraph about how the role of anthocyanins in wine color development is very complex and it is necessary for scientists to understand these relationships in order to more accurately model wine color, or suggesting that deficit irrigation might help winemakers reach stylistic color goals.
Anyone who was actually well-served by the first two paragraphs is floundering in deep water for the middle part of that data sandwich. Anyone who could follow the middle bit was bored or insulted or at least skimmed or skipped the first two paragraphs. And anyone who stuck with it to the end might be wondering why they bothered.
We’re used to this. We see it a lot. Because it’s so common, it’s easy to ignore and not remember that there are better ways.
There are. The solution is even relatively easy. First, envision who’s most likely to read what you’re writing, what they do with their days, and what they probably already know about your topic. Next, decide what you hope they’ll get out of reading your piece. Write with those ideas in your head. Then, crucially, revise. Go back through the whole thing and after reading each sentence ask yourself: did I slip up and use a word/reference a concept my reader won’t understand, or explain something they surely already know? Did I end having told them what I wanted them to get out of this, and preferably finishing on that note?
You may or may not have to guess a bit to get started, depending on whether you’re writing for a publication with a pretty well-defined readership (a newsletter that goes out to regional growers and winemakers, for instance) or a broader one (Wine Business Monthly, where you can still guess most folk are familiar with intermediate-level wine terms, or the local newspaper, where you can’t). But if you make a decision and stick with it, you’re less likely to confuse your readers even if you’ve guessed wrong.
Regardless, you’ll have avoided creating an indigestible data sandwich, or asking your audience to shape-shift as they read, or been inconsistent in your rhetorical framing. However you’d like to put it, you may have saved your well-intentioned reader from toughing it out only to find that they’re not sure how all this is relevant…
*Or, if a non-scientist writer/reporter is doing the talking, they describe the research on which they’re supposed to be reporting using the terms the scientist used when they talked last week or in the peer-reviewed research article that just came out.
**Cortell, J. M., Halbleib, M., Gallagher, A. V., Righetti, T. L, J. A. Kennedy. 2005 “Influence of vine vigor on grape (Vitis vinifera L. Cv. Pinot Noir) and wine proanthocyanidins.” J. Agric. Food Chem. 53 (14): 5798-808.
If you already know what I’m talking about, the good news is that the California DWR plans to preserve the Jose vineyard when it renovates the surrounding marshland. If that didn’t make sense to you, keep reading.
This past March, a small hullaballoo arose in response to a California Department of Water Resources plan to reconstruct a tidal marsh in Eastern Contra Costa County in the general, Sacramento-San Joaquin Delta area. The project, while an otherwise lovely effort to protect and maintain verdant wetland habitat, would have destroyed a historic and utterly irreplaceable 14-acre Carignane vineyard (“the Jose vineyard”) originally planted in the 1880’s. I wrote about the project and reasons for saving the vineyard here: Let’s stop a bad thing from happening for a good reason: saving a historic California vineyard.
This morning, the Dept. of Water Resources released their final plan and recommendations for the project, revised after a comment period during which 115 people (including me), and the city of Oakland, voiced concerns about losing the vineyard and supported changing the project to preserve it. The good news: the revised plan keeps the vineyard in place, along with a perimeter access road and an adjoining “buffer area.”
The original plan read: “The proposed project will result in the removal of the Jose Vineyard in order to achieve proper elevation and vegetation consistent with the tidal marsh restoration, which would be considered a substantial adverse change to the property under CEQA. Project redesign in order to avoid this impact while still meeting restoration goals has been determined infeasible.” Well, somehow they found the will to make it feasible, mostly by looking for soil fill elsewhere.
.6 acres of obviously newer, replanted vines at the vineyard’s edge will be ripped out and replanted with native dune vegetation, but the remaining 13.4 acres will stay put. This seems entirely sensible. While I think an argument could be made for keeping the whole vineyard intact as a historic site, the old vines are the most important concern here. It’s hard for me to argue for why we should value .6 acres of newish vines over .6 acres of good native habitat without intimately knowing the vineyard.
The project report recommends restrictions on what vineyard management techniques can be used in the interest of protecting the surrounding flora and fauna which, again, seems entirely sensible unless and until some deadly disease threatens the whole vineyard with salvation available only by drastic chemical means. I don’t know how significant the restriction is for this specific vineyard or if it changes anything about the way the vineyard is currently managed. But, again, it’s hard for me to argue in favor of using environmentally-damaging chemicals in agriculture ever, period.
In short, I feel comfortable calling this good news: for the herons and frogs, for the wine industry, and for however we represent the general interests of California history. And if you need to spend more time thinking about good news today, or if dense legislative language gives you thrills, you can find the full revised report here along with a summary of comments and the Department’s replies here.