New API Guides: Passport Data and Trait Data
If you are building applications that work with plant genetic resources, you will be glad to hear that we have expanded our API documentation with two detailed guides.
If you are building applications that work with plant genetic resources, you will be glad to hear that we have expanded our API documentation with two detailed guides.
Are you a genebank data manager who wants to publish your accession-level data online for users and researchers?
Rather than managing your own database, paying for hosting, and setting up a separate website, you can embed your data directly into your existing institutional site with Embedded Genesys.
When you browse Genesys and download data from genebanks around the world, you are using that data under a legal agreement called the Terms and Conditions of Use. You do not need to sign anything. By accessing the portal, you accept the terms automatically.
If that sounds a bit vague, this post is here to clear things up. We will walk through what the Terms actually say in plain language, so you know exactly what you can and cannot do with the data you find on Genesys.
If you have ever hesitated to join Genesys because the word "agreement" made you nervous, you are not alone. Legal documents can feel intimidating, especially when they involve your institute's valuable data. The Data Provider Agreement (DPA) is simpler than it sounds, and it exists to protect you as much as it protects the platform.
The DPA is a one-time, standard agreement between your institute and the Crop Trust. It authorizes us to publish your genebank's accession data on Genesys. Without it, your data cannot go live on the portal. But here is the good news: you can still register an account, browse Genesys, and test uploads in the Sandbox without a signed DPA. You only need it when you are ready to publish.
We have all been there, staring at thousands of records and wondering where to start. Cleaning data can often feel like a task that never ends, especially when you are juggling missing dates and coordinates. If that sounds familiar, you are not alone.
That is where the Passport Data Completeness Index (PDCI) can help.
FAO's e-learning Academy has released a four-course series on data management for plant genetic resources for food and agriculture (PGRFA). The series is completely free and self-paced, and it covers everything from the basic concepts of documenting PGRFA to the tools you need to manage, publish, and use that data in practice. If you work with genebanks, manage germplasm data, or simply want to understand how PGRFA data flows through the global system, this series is an excellent place to start.
When we talk about plant genetic resources for food and agriculture (PGRFA), the word "data" can feel a bit overwhelming because it means different things to different people. For one person, "Collection Site" might be the go-to term, while someone else prefers "Origin." Without a shared language, sharing information between genebanks can easily become a confusing tangle of spreadsheets and guesswork.
That is where the Multi-Crop Passport Descriptors (MCPD) 2.1 come in.
How do we decide which features to build next? And how do we make sure Genesys works just as well for a small national genebank as for a large international center?
That's where our Advisory Committee) comes in.
What keeps us motivated at Genesys is a simple but important goal: we want to make sure the world's plant genetic resources for food and agriculture (PGRFA) are not just tucked away in quiet vaults. We want them to be easy to find and accessible to everyone working to improve food security and sustainability.