The juicy Marshall strawberry was once declared “the finest eating strawberry in America”—indeed, legendary gourmand James Beard wrote that it was one of only two strawberries allowed in his mother’s house. Discovered in Massachusetts and introduced to the public in 1893, the Marshall was commercially popular for more than a half century—especially in the Pacific Northwest. But despite its flavorful virtues, it was delicate and susceptible to disease. As farmers transitioned to more robust varieties, the Marshall fell out of favor and become unavailable through large commercial nurseries. When artist Leah Gauthier heard about the berry, she launched a mission to preserve the fragile varietal. She now raises her own strawberries and also ships the plants to growers all over the country. Science Friday recently chatted with Gauthier about the berry’s signature flavor, her art, and how she cares for the plant.
Science Friday: I’ve never had a Marshall strawberry.
Leah Gauthier: You have to taste it! It’s really spectacular—very juicy and intensely strawberry. It bursts with flavor, even frozen. It was savored on the West Coast back in its day for its superior flavor. People who have only experienced the grocery store strawberry will have the strongest reaction. It’s a very different berry, for sure.
Why isn’t it commercially available?
The berry doesn’t ship well except for frozen, and that’s what people once did. It’s one of those strawberries you have to eat right off the vine because it’s too juicy and too fragile for transport. That’s part of the problem. Food’s grown for travel, not for taste.
How did you learn about the Marshall?
I’m an artist, and my medium is food. I did a lot of research on industrial agriculture. I was just overwhelmed by the magnitude of monocultures and pesticides. In the 20th century, we lost some 75 percent of our agricultural genetic heritage. That’s huge! I thought, for my next project, I’ll take one thing that’s going away and try to revive it. I found the Marshall on Slow Food USA’s [a grassroots organization dedicated to preserving food traditions] most endangered food list, and I tracked the plants down at the USDA’s National Clonal Germplasm Repository in Oregon.* They sent me runners cut from those plants, and my project took off from there.
So, reviving the Marshall is an art project?
I consider the whole thing a ‘relational art piece.’ That means I, as the artist, put forward a situation, and it takes a viewer to complete the task. I can’t revive the strawberry alone—it’s going to take a lot of people in a lot of places. A gentleman from Washington contacted me out of the blue in September. His family had a history with the Marshall. He asked to buy some plants from me. I sent them to him, and it wasn’t as big a process as I thought it would be. So, I decided to invite a bunch more people to join. That got the ball rolling. I’ve placed about 280 plants across the country so far. My hope is that in five years I won’t be necessary to the project anymore. People will look to each other for plants, and the Marshall will have a strong enough hold that it will be back. It will be revived. And, it will be a work of art.
How do you keep in touch with everyone who has a Marshall plant?
I have a Facebook page [EDITOR’S NOTE: This page is no longer available]. I post pictures people send, and people post on the page. Each plant has a specific number, so somebody will post, for example, that 181 and 182 are now reproducing. On the Marshall website, there’s a map of everywhere the plant has gone[EDITOR’S NOTE: This map is no longer available at this link]. I’ve gotten requests from people who looked at the map and said, ‘I see there’s one near Atlanta, and I live near Atlanta. Is there a way to save the shipping fee and contact that person directly?’ So, slowly but surely, it’s happening.
How do people react to the plant?
I get these wonderful letters from people who have memories of the berry and from people who want to make a difference in the food supply, and that’s why they’re growing the strawberry. They know they’re getting this plant in the mail. They know it’s quite uncommon. They know they’re charged with caring for it. You can talk about it all you like, but until somebody gets to experience that—it’s impossible to replicate that emotion.
You and your family recently moved from Indiana to Maine. How did you transport your plants?
The Marshalls traveled in the back of our Penske truck, and a few in the car. All 400 plants arrived safe and sound despite the heat wave.
Are the plants difficult to care for?
It’s been said the Marshall is prone to disease, but I haven’t experienced that. I had been growing it in Indiana the last five years. We had drought. We had clay soil and super hot summers. Last year we reached 107 degrees one day and had a long stretch of 100-degree days. Still, it propagated like mad. My crop kept expanding. They’ve been really hardy berries for me. I did have a big problem with aphids. But I used an organic spray recipe, and it worked really well. I’m a big tea drinker, so I’ll often put my tea grounds in the pot, and the plants seem to like it. Otherwise I use an organic liquid fertilizer and worm casings. That’s pretty much it.
What have you learned from this project?
I think I’ve learned that any time I can open up control of something and allow other people to get involved, the idea has a new life beyond anything I could have imagined. Keeping the strawberries alive was one thing, but now that everybody else has joined, it’s lovely. I’m finding out about more and more people who are participating. I just learned that the strawberry crisscrossed with the Japanese immigrant history. It’s really rewarding to see these complex layers of people and history and lives wrapped up in this one strawberry.
*Editor’s Note: Other Marshall strawberry sources exist, and some do not genetically match the clone at the National Clonal Germplasm Repository, which itself has provided runners to a number of nurseries.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
This cookie is used to detect and defend when a client attempt to replay a cookie.This cookie manages the interaction with online bots and takes the appropriate actions.
Issued by Microsoft's ASP.NET Application, this cookie stores session data during a user's website visit.
This cookie is managed by Amazon Web Services and is used for load balancing.
This cookie is set by the provider Akamai Bot Manager. This cookie is used to manage the interaction with the online bots. It also helps in fraud preventions
Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
This cookie is associated with Django web development platform for python. Used to help protect the website against Cross-Site Request Forgery attacks
The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application.
A load balancing cookie set to ensure requests by a client are sent to the same origin server.
This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
The TiPMix cookie is set by Azure to determine which web server the users must be directed to.
SiteLock sets this cookie to provide cloud-based website security services.
This cookie is used for load balancing purposes. The cookie does not store any personally identifiable data.
Azure sets this cookie for routing production traffic by specifying the production slot.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better experience for the visitors. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Cookie used to remember the user's Disqus login credentials across websites that use Disqus.
This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites.
A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to.
AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target.
This cookie is used for storing country code selected from country selector.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide anonymized information on metrics the number of visitors, bounce rate, traffic source, etc. The use of these cookies is strictly limited to measuring the site's audience. These cookies do not allow the tracking of navigation on other websites and the data collected is not combined or shared with third parties.