The NPGS after Beltsville

The USDA has decided to close its iconic flagship site, the Beltsville Agricultural Research Center (BARC) in Maryland. Everyone in plant genetic resources knows what “Beltsville” means. Cost is apparently to blame: the agency says modernizing just 11 of BARC’s 400-plus buildings and carrying out deferred maintenance would require a $500 million one-time investment plus $40 million a year ongoing, which it calls financially unsustainable. That’s about 3 hours of US defence spending.

What does this mean for the National Plant Germplasm System (NPGS)?

The NPGS’s actual seed and other collections are already distributed across the country, and USDA is using the closure to invest in new infrastructure elsewhere, including a centralized germplasm distribution centre in Ames, Iowa. Which is good.

But what happens to the National Germplasm Resources Laboratory, a key denizen of BARC? The NGRL is not a genebank. It’s a team of people who, from Beltsville, “facilitates the acquisition, exchange, and documentation of crop genetic resources important to world food security.” In other words, it provides some of the connective tissue that turns a bunch of genebanks spread around the country into a national system.

The USDA announcement is not clear about the NGRL. It does says that research projects at Beltsville will be redistributed among other USDA locations, but not what will happen to NGRL staff and its system-wide functions. Ames will gain an important new distribution facility, but that’s not the same as the NGRL as a whole.

It will be interesting to see whether USDA moves the NGRL’s expertise and functions intact, or divides them among different locations: dispersion runs the danger of weakening the institutional knowledge of how acquisition, documentation, quarantine, distribution and international exchange fit together. For the NPGS, that may ultimately be the most important consequence of the Beltsville reorganization. Stay tuned.

LATER: Some people don’t like what’s happening.

Brainfood: Opportunity crops, meet your constraints

The case for a case manager

In an earlier post I argued that the crop diversity conservation and use system has a missing middle: someone whose job it is to get the whole way from an agricultural problem to a diversity-based solution.

That would address the perceived problem of “underuse” of genebanks collections better, I think, than making more data on collections available, or easier to search. I know we now have cheap genome sequencing and high-throughput phenotyping and powerful databases and AI on our phones, for pity’s sake. But we’ve been counting on the latest technological leap for quite a while now, and I figured it was time to look elsewhere for a solution.

I compared this missing role or function to that of an insurance broker.

I still think there’s a missing middle; but that was the wrong analogy. Insurance brokers navigate a liquid market of interchangeable, price-comparable products with a client who already knows they want insurance. That’s not like working with genebanks, if you think it through better than I originally did. I think I was seduced by the notion that crop diversity is a form of insurance.

There’s a better fit: medical case manager.

That’s the person who follows the patient through the maze of the health system. They don’t do the surgery or prescribe the drugs. They make sure the referrals happens, the test results gets chased, the specialists talk to each other, and nobody quietly drops the ball because, well, their particular bit of the system is working perfectly well.

Sound familiar?

A breeding programme can have a perfectly good reason for aiming for a particular combination of traits. A genebank can have exactly the right diversity to test. The accessions can be sequenced, well characterized, searchable through a beautifully designed database, and readily available. The breeders might be excellent breeders.

And still nothing might happen. Not because anyone screwed up necessarily, but because nobody owned the process as a whole, and thus put the entire package together.

That, I think, is the missing middle.

And this better analogy points to something else that the insurance-broker metaphor rather conveniently (for me) glossed over: independence.

Independence as a structural necessity. Someone sitting inside Genebank A, however well-intentioned, is going to have a harder time saying “actually, the stuff you need is in Genebank B,” because their salary, mandate and incentives all live inside Genebank A.

A case manager, on the other hand, is supposed to follow the patient, not defend the department.

The starting point should be the agricultural problem. The answer might be in a genebank. It might be in another genebank. It might be on a farm, in a community seed bank, in a breeding programme, or nowhere in the genetic-resources system at all. The case manager needs to be positioned so that they have no stake in which collection, programme or database ends up being the answer.

There is another useful thing about the case-manager analogy: it is not hypothetical. Health systems have been paying people to do this for decades. And they have had to work out some fairly prosaic questions that we tend to skip when talking about “unlocking” genebank diversity.

Who pays? What counts as success? How do you stop the navigator becoming a glorified administrator? What happens when whoever pays the salary starts deciding where the patients should go?

These are not trivial details. Getting them right is what turns a nice metaphor into an institution that might just work.

Start with the problem. Find the relevant expertise and diversity, wherever it happens to be. Get the handoffs made. Notice when things stall. Keep going until there is an outcome, including, if necessary, the conclusion that crop diversity wasn’t the answer.

We’ve gotten better at opening the door to genebanks over the years. We have lots of data, fancy databases and AI. What we’re still missing is the person who walks through that door with you, the user, and is knowledgeable and independent enough to help you figure out whether the answer lies inside, elsewhere in the system, or somewhere else altogether. Call it a broker or a case manager, or whatever else you like, but that’s what I believe we need.

Again, this is just me thinking out loud here. Maybe I’m the patient who has been sent home with a stack of test results, a list of specialists and a phone number for the hospital switchboard, and is trying to work out what to do next. Help me out.

Nibbles: Frafra, Seed multiplication, Quality seeds, Balearic genebank, Indigenous trees double, Bruno cart, Belgian wild yeast

  1. Frafra potato is having a moment: an indigenous West African tuber, adored locally and mostly ignored by science, out looking for its big commercial break.
  2. Speaking of breakthroughs, this bus driver found his own, swapping the wheel for seed multiplication and turning five acres into a livelihood, proof that sometimes the missing link in a seed system is just someone willing to do the unglamorous middle bit well.
  3. Which is, per Farming First, precisely Africa’s problem at scale: only 2.5% of smallholder seed in Sub-Saharan Africa comes from formal seed companies, so a few million more bus-driver-style multipliers wouldn’t hurt.
  4. Meanwhile in the Balearics, the opposite direction of travel: the local seed bank is expanding to rescue tomatoes, onions and broad beans, and is looking for farmers willing to take them back.
  5. Indigenous fruit trees in Malawi turn out to fight malnutrition and biodiversity loss at once. Happy coincidence?
  6. Getting those trees into the ground well needs the same unglamorous groundwork as any good crop seed system: a Mongabay commentary argues that restoration campaigns skipping Indigenous and local seed knowledge are optimising for trees planted, not trees that survive.
  7. And once you’ve got the saplings in the ground, you might want to monitor how they’re doing: enter Bruno, a pushcart rigged with mobile phones that can collect field data. And not just for breeders.
  8. Finally, proof that not all genetic-resource hunting needs a genebank: Brussels brewers are getting people to comb the city for wild yeast, because the raw materials for a proper lambic turns is hanging around in urban trees.

Missing use, or missing middle?

Genebank data seems to be in the air. Just in the past few days, I pontificated about descriptors, Mike Jackson has reminisced about the early days of rice molecular markers and CGIAR announced a big new initiative.

More data is always good to have, I’m sure. But, but, but… Genebanks are underused and more data will solve the problem? We’ve been saying something much like this for a long time now. Leave aside for the moment the question of whether CGIAR genebanks really are “underused.” Underused by whom, according to what metric, compared to what? But let’s just assume for the sake of argument that they are, indeed, underused. What if… Hear me out: what if that problem cannot be solved just by making genebank databases bigger, deeper and easier to search?

Ok, that will need some unpacking. But remember as you read this that I’m not saying that genebanks working with others to generate and share more data on nutritional quality or disease resistance is a bad thing. Just that it’s not enough. Never has been. Probably never will be.

Continue reading “Missing use, or missing middle?”