<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Genesys PGR  Blog</title>
        <link>https://docs.genesys-pgr.org/blog</link>
        <description>Genesys PGR  Blog</description>
        <lastBuildDate>Thu, 30 Jul 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <item>
            <title><![CDATA[New API Guides: Passport Data and Trait Data]]></title>
            <link>https://docs.genesys-pgr.org/blog/2026/07/30/new-api-guides</link>
            <guid>https://docs.genesys-pgr.org/blog/2026/07/30/new-api-guides</guid>
            <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Two new guides walk you through retrieving passport data and trait observations from the Genesys API.]]></description>
            <content:encoded><![CDATA[<p>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.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="fetching-passport-data">Fetching passport data<a href="https://docs.genesys-pgr.org/blog/2026/07/30/new-api-guides#fetching-passport-data" class="hash-link" aria-label="Direct link to Fetching passport data" title="Direct link to Fetching passport data" translate="no">​</a></h2>
<p>The <a class="" href="https://docs.genesys-pgr.org/docs/api/passport-data">passport data guide</a> covers the two endpoints available for retrieving accession passport data: <code>/acn/query</code> and <code>/acn/filter</code>.</p>
<p>The guide emphasizes that <code>/acn/query</code> is the best choice for bulk exports. It can return up to 1,000,000 records per request as a CSV file, meaning you can download the entire Genesys dataset (over 4.5 million accessions) with just a handful of paginated requests. The <code>/acn/filter</code> endpoint, by contrast, is limited to 1,000 records per request.</p>
<p>Both endpoints accept the same filters, so you can refine your queries by crop, institute, or any of the standard MCPD fields.</p>
<p>When using data retrieved via the API, please remember to <a class="" href="https://docs.genesys-pgr.org/docs/manual/legal/citation">cite the data</a> and review the <a class="" href="https://docs.genesys-pgr.org/docs/manual/legal/terms-and-conditions">terms and conditions</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="fetching-trait-data">Fetching trait data<a href="https://docs.genesys-pgr.org/blog/2026/07/30/new-api-guides#fetching-trait-data" class="hash-link" aria-label="Direct link to Fetching trait data" title="Direct link to Fetching trait data" translate="no">​</a></h2>
<p>The <a class="" href="https://docs.genesys-pgr.org/docs/api/trait-data">trait data guide</a> walks you through a 4-step workflow for retrieving phenotypic observations:</p>
<ol>
<li class="">Find trait datasets associated with accessions matching your filters</li>
<li class="">List the available trait columns (descriptors) in those datasets</li>
<li class="">Fetch the actual trait observations for the columns you need</li>
<li class="">Look up descriptor metadata to understand what each column represents</li>
</ol>
<p>This workflow reflects how trait data is structured in Genesys: datasets contain multiple trait columns, and each column is referenced by a UUID rather than a human-readable name.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="thanks">Thanks!<a href="https://docs.genesys-pgr.org/blog/2026/07/30/new-api-guides#thanks" class="hash-link" aria-label="Direct link to Thanks!" title="Direct link to Thanks!" translate="no">​</a></h2>
<p>These guides were authored by Khadija to support their own work with the API and have generously shared them with the community.</p>
<p>You can find both guides in the <a class="" href="https://docs.genesys-pgr.org/docs/api/">API documentation section</a>.</p>]]></content:encoded>
            <category>api</category>
            <category>developers</category>
            <category>passport</category>
            <category>traits</category>
        </item>
        <item>
            <title><![CDATA[Embedded Genesys]]></title>
            <link>https://docs.genesys-pgr.org/blog/2026/07/29/embedded-genesys</link>
            <guid>https://docs.genesys-pgr.org/blog/2026/07/29/embedded-genesys</guid>
            <pubDate>Wed, 29 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[What is Embedded Genesys and its newest features.]]></description>
            <content:encoded><![CDATA[<p>Are you a genebank data manager who wants to publish your accession-level data online for users and researchers?</p>
<p>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.</p>
<!-- -->
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-is-embedded-genesys">What is Embedded Genesys?<a href="https://docs.genesys-pgr.org/blog/2026/07/29/embedded-genesys#what-is-embedded-genesys" class="hash-link" aria-label="Direct link to What is Embedded Genesys?" title="Direct link to What is Embedded Genesys?" translate="no">​</a></h3>
<p>Embedded Genesys is a JavaScript library that connects your website to the Genesys servers and displays your genebank data to visitors. It gives you everything you need to share your collection online:</p>
<ul>
<li class=""><strong>Browse and search passport data</strong> - Let users explore your collection directly on your site</li>
<li class=""><strong>Display accession details</strong> - Show comprehensive information for each accession</li>
<li class=""><strong>Maps</strong> - Visualize where your accessions were collected</li>
<li class=""><strong>Subsets</strong> - Curated lists of accessions grouped by shared criteria</li>
<li class=""><strong>Trait data</strong> - Share phenotypic and other characterization data</li>
<li class=""><strong>Request material</strong> - Let researchers request germplasm directly from your website</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="see-it-in-action">See It In Action<a href="https://docs.genesys-pgr.org/blog/2026/07/29/embedded-genesys#see-it-in-action" class="hash-link" aria-label="Direct link to See It In Action" title="Direct link to See It In Action" translate="no">​</a></h3>
<p>Check out our <a href="https://genesys-pgr.p.gitlab.croptrust.org/ui-embedded/" target="_blank" rel="noopener noreferrer" class="">live demo site</a> to see Embedded Genesys in action.</p>
<p>Several CGIAR genebanks are already using Embedded Genesys on their institutional websites. Take a look at how it works at <a href="https://rbca.africarice.org/request-for-germplasm" target="_blank" rel="noopener noreferrer" class="">AfricaRice</a>, <a href="https://cipotato.org/genebankcip/cip-request/" target="_blank" rel="noopener noreferrer" class="">CIP</a>, <a href="https://www.irri.org/genesys-rice" target="_blank" rel="noopener noreferrer" class="">IRRI</a> and <a href="https://www.iita.org/germplasm-request" target="_blank" rel="noopener noreferrer" class="">IITA</a>.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="get-started">Get Started<a href="https://docs.genesys-pgr.org/blog/2026/07/29/embedded-genesys#get-started" class="hash-link" aria-label="Direct link to Get Started" title="Direct link to Get Started" translate="no">​</a></h3>
<p>Use the <a href="https://genesys-pgr.p.gitlab.croptrust.org/ui-embedded/installer/" target="_blank" rel="noopener noreferrer" class="">online installation wizard</a> to generate the code for embedding your collection on your website.</p>
<p>For more information, visit the <a class="" href="https://docs.genesys-pgr.org/docs/providers/embedded-genesys">Embedded Genesys documentation</a>.</p>]]></content:encoded>
            <category>Genebanks</category>
            <category>Data Providers</category>
        </item>
        <item>
            <title><![CDATA[Understanding the Genesys Terms and Conditions]]></title>
            <link>https://docs.genesys-pgr.org/blog/2026/07/27/understanding-terms-and-conditions</link>
            <guid>https://docs.genesys-pgr.org/blog/2026/07/27/understanding-terms-and-conditions</guid>
            <pubDate>Mon, 27 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[What the Terms and Conditions mean for you when you browse Genesys and download data from genebanks around the world.]]></description>
            <content:encoded><![CDATA[<p>When you browse Genesys and download data from genebanks around the world, you are using that data under a legal agreement called the <strong>Terms and Conditions of Use</strong>. You do not need to sign anything. By accessing the portal, you accept the terms automatically.</p>
<p>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.</p>
<!-- -->
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-license-are-you-getting">What license are you getting?<a href="https://docs.genesys-pgr.org/blog/2026/07/27/understanding-terms-and-conditions#what-license-are-you-getting" class="hash-link" aria-label="Direct link to What license are you getting?" title="Direct link to What license are you getting?" translate="no">​</a></h3>
<p>When you download data from Genesys, you receive a license from the Crop Trust that is:</p>
<ul>
<li class=""><strong>Revocable</strong>: The Crop Trust can modify or withdraw the license at any time.</li>
<li class=""><strong>Worldwide</strong>: It applies wherever you are in the world, no matter which country you are working in.</li>
<li class=""><strong>Royalty-free</strong>: You do not pay anything for the use of the data.</li>
<li class=""><strong>Non-exclusive</strong>: The same data is available to other users too. The Crop Trust can grant the same rights to anyone else.</li>
<li class=""><strong>Non-transferable</strong>: You cannot pass this license on to someone else. If a colleague or partner wants to use the data, they must download it themselves directly from Genesys.</li>
</ul>
<p>In plain terms, you get free access to use the data for your own research and applications, but the data is not yours to give away or resell.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-are-you-allowed-to-do">What are you allowed to do?<a href="https://docs.genesys-pgr.org/blog/2026/07/27/understanding-terms-and-conditions#what-are-you-allowed-to-do" class="hash-link" aria-label="Direct link to What are you allowed to do?" title="Direct link to What are you allowed to do?" translate="no">​</a></h3>
<p>The license grants you broad freedom to use the data for any lawful purpose. That covers research, plant breeding, education, conservation projects, and much more. The portal exists precisely to make plant genetic resource data accessible to everyone who needs it, and the Terms are designed to support that goal rather than restrict it.</p>
<p>You are also welcome to link to Genesys from your own website, provided you do so fairly, in good faith, and in a way that does not damage the reputation of the Crop Trust or take advantage of it. Importantly, you cannot establish a link or publish statements that imply any form of association with, approval from, or endorsement by the Crop Trust unless you have written confirmation from the Crop Trust that such a relationship exists.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-are-the-restrictions">What are the restrictions?<a href="https://docs.genesys-pgr.org/blog/2026/07/27/understanding-terms-and-conditions#what-are-the-restrictions" class="hash-link" aria-label="Direct link to What are the restrictions?" title="Direct link to What are the restrictions?" translate="no">​</a></h3>
<p>The Terms include a few important restrictions that protect the interests of the genebanks who share their data and the portal that makes it accessible:</p>
<p><strong>No redistribution.</strong> You cannot redistribute the data to other users. This means you cannot share downloaded data files with people outside your immediate team, upload them to another platform, or pass them on in any form. Instead, direct any interested potential users to Genesys so they can access the data themselves directly from the portal. This keeps the portal as the single, authoritative source and ensures proper attribution flows back to the original data providers.</p>
<p><strong>No republishing that competes with the portal.</strong> You cannot copy, reproduce, post, broadcast, or adapt the contents of Genesys in any way that would unreasonably harm the legitimate interests of the Crop Trust or compete with the portal. This means, for example, you cannot build a competing database that repackages and republishes Genesys data without adding substantial original value.</p>
<p><strong>No intellectual property claims.</strong> The data you download does not give you any copyright, intellectual property rights, or proprietary interest in that data. You are a licensee, not an owner.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="how-do-you-give-credit">How do you give credit?<a href="https://docs.genesys-pgr.org/blog/2026/07/27/understanding-terms-and-conditions#how-do-you-give-credit" class="hash-link" aria-label="Direct link to How do you give credit?" title="Direct link to How do you give credit?" translate="no">​</a></h3>
<p>When you use data from Genesys in your research, publications, or applications, you are required to acknowledge the original sources. The data comes from specific genebanks, and those institutions deserve recognition for sharing their collections.</p>
<p>Genesys provides guidance on how to format citations and attributions on the portal itself. Keeping intact any notices about the source of the data that accompany your downloads is part of your obligation under the Terms. You must also ensure that anyone you work with closely (for example, collaborators on a shared project) is aware of and complies with the same Terms when they use the data.</p>
<p>If you would like specific guidance on how to cite data from Genesys, see our <a class="" href="https://docs.genesys-pgr.org/docs/manual/legal/citation">Citation and attribution policy</a>.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-about-warranties-and-liability">What about warranties and liability?<a href="https://docs.genesys-pgr.org/blog/2026/07/27/understanding-terms-and-conditions#what-about-warranties-and-liability" class="hash-link" aria-label="Direct link to What about warranties and liability?" title="Direct link to What about warranties and liability?" translate="no">​</a></h3>
<p>The data on Genesys is provided <strong>as is</strong> from the original providers, without any warranty. This means the Crop Trust and the data providers do not guarantee that the data is accurate, complete, or fit for your particular purpose. Genebanks do their best to maintain high-quality records, but the nature of biological data means some uncertainty is inevitable.</p>
<p>For liability, the Crop Trust and the data providers are not liable for any loss or damage that arises from your use of the data, whether through your actions or someone else's. This includes indirect damages such as lost revenue, lost profits, or lost business opportunities. If negligence on the part of the Crop Trust or a data provider can be proved, liability is limited to direct financial loss only.</p>
<p>This is standard language in open data agreements. The goal is to make data freely available while protecting the institutions that share it from legal exposure that could discourage them from publishing in the first place.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-happens-if-the-terms-change">What happens if the Terms change?<a href="https://docs.genesys-pgr.org/blog/2026/07/27/understanding-terms-and-conditions#what-happens-if-the-terms-change" class="hash-link" aria-label="Direct link to What happens if the Terms change?" title="Direct link to What happens if the Terms change?" translate="no">​</a></h3>
<p>The Crop Trust may update the portal or change these Terms at any time. Changes take effect immediately upon posting on the Genesys homepage, unless otherwise stated. If you continue to use the portal after a change, you are deemed to have accepted the new Terms. We recommend checking this page occasionally to stay informed about any updates.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-happens-if-you-break-the-terms">What happens if you break the Terms?<a href="https://docs.genesys-pgr.org/blog/2026/07/27/understanding-terms-and-conditions#what-happens-if-you-break-the-terms" class="hash-link" aria-label="Direct link to What happens if you break the Terms?" title="Direct link to What happens if you break the Terms?" translate="no">​</a></h3>
<p>If you breach any of the Terms, your license is automatically terminated immediately, without notice. That means you lose your right to use the data right away. If the situation involves a legal dispute, the Crop Trust will resolve it through binding arbitration under UNCITRAL Rules, in Bonn, Germany, in English.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="in-summary">In summary<a href="https://docs.genesys-pgr.org/blog/2026/07/27/understanding-terms-and-conditions#in-summary" class="hash-link" aria-label="Direct link to In summary" title="Direct link to In summary" translate="no">​</a></h3>
<p>The Genesys Terms and Conditions are designed to keep plant genetic resource data open and accessible while protecting the genebanks who contribute it. You get broad, free, permanent rights to use the data for your own purposes, with the main obligations being attribution, no redistribution, and no competing republishing. The data is provided as-is, without warranties, and the Crop Trust and data providers are not liable for how you use it.</p>
<p>If you have questions about how the Terms apply to your specific situation, feel free to reach out to the helpdesk at <a href="mailto:helpdesk@genesys-pgr.org" target="_blank" rel="noopener noreferrer" class="">helpdesk@genesys-pgr.org</a>. And if you would like to read the full legal text, you can find it in our <a class="" href="https://docs.genesys-pgr.org/docs/manual/legal/terms-and-conditions">Terms and Conditions documentation</a>.</p>]]></content:encoded>
            <category>Legal</category>
            <category>Users</category>
        </item>
        <item>
            <title><![CDATA[The Data Provider Agreement, Explained]]></title>
            <link>https://docs.genesys-pgr.org/blog/2026/07/26/the-data-provider-agreement-explained</link>
            <guid>https://docs.genesys-pgr.org/blog/2026/07/26/the-data-provider-agreement-explained</guid>
            <pubDate>Sun, 26 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[What the Data Provider Agreement is, why genebanks need it, and what it means for your data on Genesys.]]></description>
            <content:encoded><![CDATA[<p>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. But the <strong>Data Provider Agreement (DPA)</strong> is simpler and friendlier than it sounds, and it exists to protect you as much as it protects the platform.</p>
<p>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.</p>
<!-- -->
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-the-dpa-does-and-doesnt-do">What the DPA does (and doesn't do)<a href="https://docs.genesys-pgr.org/blog/2026/07/26/the-data-provider-agreement-explained#what-the-dpa-does-and-doesnt-do" class="hash-link" aria-label="Direct link to What the DPA does (and doesn't do)" title="Direct link to What the DPA does (and doesn't do)" translate="no">​</a></h3>
<p>The DPA accomplishes three things. It authorizes the Crop Trust to publish your data by granting a perpetual, worldwide, royalty-free, non-exclusive license to use your accession data to build and operate Genesys. In plain terms, this lets us make your data available to users of the portal under the <a class="" href="https://docs.genesys-pgr.org/docs/manual/legal/terms-and-conditions">Terms and Conditions of Use</a>. It confirms in writing that you retain ownership. And it defines the responsibilities of both parties regarding data quality, attribution, and the broader operation of the portal.</p>
<p>Equally important is what the DPA does <strong>not</strong> do. It does not transfer ownership of your data to the Crop Trust. It does not give the Crop Trust permission to alter, modify, or redistribute your data outside Genesys. And it does not involve any financial transaction: there are no licensing fees, royalties, subscriptions, or service charges in either direction. The Crop Trust cannot republish your data in another medium without your written permission.</p>
<p>You can read the full breakdown in our <a class="" href="https://docs.genesys-pgr.org/docs/providers/dpa/what-is-dpa">DPA introduction guide</a>.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="you-keep-ownership-of-your-data">You keep ownership of your data<a href="https://docs.genesys-pgr.org/blog/2026/07/26/the-data-provider-agreement-explained#you-keep-ownership-of-your-data" class="hash-link" aria-label="Direct link to You keep ownership of your data" title="Direct link to You keep ownership of your data" translate="no">​</a></h3>
<p>This is the legal heart of the agreement, and we want to say it plainly: signing the DPA does not transfer ownership to the Crop Trust. The Crop Trust explicitly acknowledges that it will not claim any copyright, intellectual property rights, or proprietary interest in your data. When making your data available to third parties through Genesys, the Crop Trust must include that same condition downstream.</p>
<p>The license you grant is also <strong>revocable</strong>. You can withdraw your data at any time.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="you-can-walk-away-at-any-time">You can walk away at any time<a href="https://docs.genesys-pgr.org/blog/2026/07/26/the-data-provider-agreement-explained#you-can-walk-away-at-any-time" class="hash-link" aria-label="Direct link to You can walk away at any time" title="Direct link to You can walk away at any time" translate="no">​</a></h3>
<p>If you ever decide to remove your data from Genesys, the DPA makes that straightforward. You submit a formal written request to the Crop Trust, and your data is removed within three calendar months. The request needs to be formal (a special delivery letter to the Executive Secretary), not just an email, because the three-month window allows for an orderly removal including communications with end users who may rely on the data.</p>
<p>Either party can also terminate the entire DPA with six months' written notice. One important detail: existing end-user licenses for data that has already been downloaded are not affected. People who already downloaded your data keep their license to use it, but no new downloads happen after removal.</p>
<p>For the full details, see the <a class="" href="https://docs.genesys-pgr.org/docs/providers/dpa/dpa-characteristics">key characteristics of the DPA</a>.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="its-one-agreement-in-a-framework-of-three">It's one agreement in a framework of three<a href="https://docs.genesys-pgr.org/blog/2026/07/26/the-data-provider-agreement-explained#its-one-agreement-in-a-framework-of-three" class="hash-link" aria-label="Direct link to It's one agreement in a framework of three" title="Direct link to It's one agreement in a framework of three" translate="no">​</a></h3>
<p>Three legal documents together govern what happens on Genesys, but you only sign one of them. The <strong>DPA</strong> is between you and the Crop Trust. The <strong>Terms and Conditions of Use</strong> bind all end users, defining how they can use the data they access and explicitly prohibiting them from redistributing it. The <strong>Citation and attribution policy</strong> sets out how end users must acknowledge the source of any data they use.</p>
<p>Here is the key reassurance: by signing the DPA, you benefit from the protections built into the other two documents without having to manage them yourself. The Crop Trust takes on the responsibility of displaying those terms and enforcing citation requirements. You can review the <a class="" href="https://docs.genesys-pgr.org/docs/manual/legal/terms-and-conditions">Terms and Conditions of Use</a> and the <a class="" href="https://docs.genesys-pgr.org/docs/manual/legal/citation">Citation and attribution policy</a> at your convenience.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="who-signs-and-what-youll-need">Who signs, and what you'll need<a href="https://docs.genesys-pgr.org/blog/2026/07/26/the-data-provider-agreement-explained#who-signs-and-what-youll-need" class="hash-link" aria-label="Direct link to Who signs, and what you'll need" title="Direct link to Who signs, and what you'll need" translate="no">​</a></h3>
<p>The signatory must be someone with legal authority to bind your institute into agreements, typically the Director-General, Rector, or Chief Executive Officer, not the genebank curator. One DPA covers all genebanks operated by the same institute, so you only sign once even if your organization runs multiple collections.</p>
<p>To get started, you will need to provide six items to the Crop Trust:</p>
<ol>
<li class=""><strong>Full legal name</strong> of your institute</li>
<li class=""><strong>Mailing address</strong> of the institute</li>
<li class=""><strong>Name of the genebank</strong></li>
<li class=""><strong>FAO WIEWS institute code (INSTCODE)</strong>, the globally unique identifier assigned by FAO's World Information and Early Warning System on Plant Genetic Resources for Food and Agriculture (WIEWS)</li>
<li class=""><strong>Name and email</strong> of the primary focal point (your day-to-day contact)</li>
<li class=""><strong>Name and position</strong> of the authorized signatory</li>
</ol>
<p>You can find the full onboarding procedure in our <a class="" href="https://docs.genesys-pgr.org/docs/providers/getting-started/joining-genesys">guide to joining Genesys</a>.</p>
<p>If your genebank is ready to share its data with the world, we would love to hear from you. Reach out to the helpdesk at <a href="mailto:helpdesk@genesys-pgr.org" target="_blank" rel="noopener noreferrer" class="">helpdesk@genesys-pgr.org</a>, or dive into the <a class="" href="https://docs.genesys-pgr.org/docs/providers/dpa/what-is-dpa">full DPA guide</a> to learn more. We are here to help every step of the way!</p>]]></content:encoded>
            <category>Data Providers</category>
            <category>Legal</category>
        </item>
        <item>
            <title><![CDATA[Measuring Completeness: Understanding the PDCI Metric]]></title>
            <link>https://docs.genesys-pgr.org/blog/2026/07/22/pdci-metric</link>
            <guid>https://docs.genesys-pgr.org/blog/2026/07/22/pdci-metric</guid>
            <pubDate>Wed, 22 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[How to use the Passport Data Completeness Index (PDCI) to prioritize curation and improve your PGR collection's data quality.]]></description>
            <content:encoded><![CDATA[<p>We've 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're juggling missing dates and coordinates. If that sounds familiar, you're definitely not alone!</p>
<p>That's where the <strong>Passport Data Completeness Index (PDCI)</strong> comes to the rescue.</p>
<!-- -->
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-exactly-is-pdci">What exactly is PDCI?<a href="https://docs.genesys-pgr.org/blog/2026/07/22/pdci-metric#what-exactly-is-pdci" class="hash-link" aria-label="Direct link to What exactly is PDCI?" title="Direct link to What exactly is PDCI?" translate="no">​</a></h3>
<p>Think of the PDCI as a friendly little score from <strong>0 to 10</strong>. It gives you a quick snapshot of how complete an accession's passport data actually is, so you don't have to guess.</p>
<p>One thing to keep in mind: the PDCI measures <strong>presence, not correctness</strong>. For example, a record might hit a perfect 10 because every field is filled, even if there's a typo hidden in there. The PDCI doesn't tell you if the data is <em>right</em>, just that it's <em>there</em>.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="not-all-fields-are-created-equal">Not All Fields Are Created Equal<a href="https://docs.genesys-pgr.org/blog/2026/07/22/pdci-metric#not-all-fields-are-created-equal" class="hash-link" aria-label="Direct link to Not All Fields Are Created Equal" title="Direct link to Not All Fields Are Created Equal" translate="no">​</a></h3>
<p>The best part about the PDCI is that it's <strong>context-aware</strong>.</p>
<p>It understands that a wild accession needs different information than a modern cultivar. For a wild sample, coordinates and collection dates are the stars of the show. For a cultivar, we care more about the breeder's name and the pedigree. Because the PDCI weights descriptors based on the accession's <strong>biological status (SAMPSTAT)</strong>, every record can reach that perfect 10, whether it's a landrace or a breeding line.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="how-to-use-pdci-to-improve-your-collection">How to Use PDCI to Improve Your Collection<a href="https://docs.genesys-pgr.org/blog/2026/07/22/pdci-metric#how-to-use-pdci-to-improve-your-collection" class="hash-link" aria-label="Direct link to How to Use PDCI to Improve Your Collection" title="Direct link to How to Use PDCI to Improve Your Collection" translate="no">​</a></h3>
<p>When you're looking at your collection's PDCI distribution, you might be tempted to just chase the zeros. But here's a pro-tip for making your curation a bit more rewarding:</p>
<ul>
<li class=""><strong>Avoid the extremes</strong>: Records with very low scores might be missing information that's unfortunately gone for good. On the other hand, those with very high scores are already in great shape.</li>
<li class=""><strong>Target the "Middle"</strong>: This is where the magic happens! You'll often find the most "improvement potential" in intermediate scores. These are the records where a bit of digging through the archives can really boost the value of your data.</li>
<li class=""><strong>Spot Patterns</strong>: If all your wild accessions have low PDCI but your landraces are high, you've just found your target; it's likely a gap in your collecting-site data.</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="curation-is-a-journey">Curation is a Journey<a href="https://docs.genesys-pgr.org/blog/2026/07/22/pdci-metric#curation-is-a-journey" class="hash-link" aria-label="Direct link to Curation is a Journey" title="Direct link to Curation is a Journey" translate="no">​</a></h3>
<p>At Genesys, we view the PDCI as a helpful diagnostic tool rather than a final destination. By tracking your average score over time, you can see your hard work paying off in real-time.</p>
<p>Is your collection as complete as it could be? We'd love for you to head over to <a href="https://www.genesys-pgr.org/" target="_blank" rel="noopener noreferrer" class="">Genesys</a>, check your scores, and start your own journey toward a 10! And if you're one of our data providers, you can find a more detailed deep-dive in our <a class="" href="https://docs.genesys-pgr.org/docs/providers/preparing-mcpd/curation-validation">curation and validation guide</a>.</p>]]></content:encoded>
            <category>Data Quality</category>
            <category>PDCI</category>
        </item>
        <item>
            <title><![CDATA[New FAO E-learning Series: Four Free Courses on Plant Genetic Resources Data]]></title>
            <link>https://docs.genesys-pgr.org/blog/2026/07/20/fao-elearning-series</link>
            <guid>https://docs.genesys-pgr.org/blog/2026/07/20/fao-elearning-series</guid>
            <pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[FAO's free e-learning series covers the full journey of PGRFA data, from documenting accessions in GGCE to exploring collections on Genesys and planning global crop conservation strategies.]]></description>
            <content:encoded><![CDATA[<p>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.</p>
<!-- -->
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-series-at-a-glance">The series at a glance<a href="https://docs.genesys-pgr.org/blog/2026/07/20/fao-elearning-series#the-series-at-a-glance" class="hash-link" aria-label="Direct link to The series at a glance" title="Direct link to The series at a glance" translate="no">​</a></h3>
<p>The four courses build on each other and together form a comprehensive introduction to PGRFA data management:</p>
<ul>
<li class=""><strong><a href="https://elearning.fao.org/course/view.php?id=1364" target="_blank" rel="noopener noreferrer" class="">Course 1: Introduction to documenting plant genetic resources for food and agriculture</a></strong> (40 minutes). A grounding in the essential concepts behind PGRFA documentation. No prior experience needed.</li>
<li class=""><strong><a href="https://elearning.fao.org/course/view.php?id=1361" target="_blank" rel="noopener noreferrer" class="">Course 2: The Global Information System</a></strong> (1 hour 10 minutes). Explores GLIS, the digital infrastructure established under Article 17 of the International Treaty on PGRFA, including the role of digital object identifiers (DOIs) for accession-level data.</li>
<li class=""><strong><a href="https://elearning.fao.org/course/view.php?id=1365" target="_blank" rel="noopener noreferrer" class="">Course 3: GRIN-Global Community Edition (GGCE) and Genesys</a></strong> (1 hour 35 minutes). The course you came here for. It introduces GGCE as a genebank management system and Genesys as the global portal where participating institutions publish their accession data. This course is particularly relevant if you are considering joining Genesys as a data provider, or if you want to learn how to explore the platform effectively.</li>
<li class=""><strong><a href="https://elearning.fao.org/course/view.php?id=1362" target="_blank" rel="noopener noreferrer" class="">Course 4: Global crop conservation strategies</a></strong> (1 hour 40 minutes). Looks at how diversity coverage assessments and gap analyses inform conservation priorities and how global crop strategies guide collective efforts to safeguard crop diversity.</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-you-will-learn-in-the-genesys-course">What you will learn in the Genesys course<a href="https://docs.genesys-pgr.org/blog/2026/07/20/fao-elearning-series#what-you-will-learn-in-the-genesys-course" class="hash-link" aria-label="Direct link to What you will learn in the Genesys course" title="Direct link to What you will learn in the Genesys course" translate="no">​</a></h3>
<p>The course on GGCE and Genesys is divided into two lessons. The first covers GGCE, the open-source genebank management system that helps institutions capture, organize, and use PGRFA data to support consistent workflows. You will learn how accession and inventory records in GGCE support traceability of physical material, and how the system handles routine genebank activities such as viability testing, regeneration, multiplication, and distribution.</p>
<p>The second lesson shifts to Genesys. You will explore the main functions of the portal and the types of accession-level data available, learn how to query and interpret data using manual filters and Genesys AI, and understand the data quality principles and standards that make sharing through Genesys effective. The course is designed for a broad audience: genebank staff, data managers, researchers, breeders, and students alike.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="certification-is-available">Certification is available<a href="https://docs.genesys-pgr.org/blog/2026/07/20/fao-elearning-series#certification-is-available" class="hash-link" aria-label="Direct link to Certification is available" title="Direct link to Certification is available" translate="no">​</a></h3>
<p>Each course in the series offers a digital badge upon passing a final exam with a score of at least 75%. You can take the exam after completing the course, and you do not need to be affiliated with any institution to earn the badge. Once earned, your certificate is available from your <a href="https://elearning.fao.org/user/profile.php" target="_blank" rel="noopener noreferrer" class="">FAO elearning Academy profile</a>.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-bigger-picture">The bigger picture<a href="https://docs.genesys-pgr.org/blog/2026/07/20/fao-elearning-series#the-bigger-picture" class="hash-link" aria-label="Direct link to The bigger picture" title="Direct link to The bigger picture" translate="no">​</a></h3>
<p>This e-learning series sits within the broader ecosystem that Genesys helps to serve. By understanding how data is documented, quality-checked, and shared through systems like GGCE and platforms like Genesys, you become part of a much larger effort to make plant genetic resources visible and accessible to everyone who needs them.</p>
<p>If you manage a genebank or are considering sharing your data on Genesys, these courses will give you a solid foundation. And if you are a researcher, breeder, or student, they will help you understand exactly where the data on Genesys comes from and how to use it with confidence.</p>]]></content:encoded>
            <category>E-learning</category>
            <category>Data Providers</category>
            <category>Users</category>
            <category>Genebanks</category>
            <category>Data Standards</category>
        </item>
        <item>
            <title><![CDATA[Demystifying Data Standards: A Guide to MCPD 2.1]]></title>
            <link>https://docs.genesys-pgr.org/blog/2026/07/15/mcpd-guide</link>
            <guid>https://docs.genesys-pgr.org/blog/2026/07/15/mcpd-guide</guid>
            <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[A deep dive into the Multi-Crop Passport Descriptors (MCPD) 2.1 and why data standardization matters.]]></description>
            <content:encoded><![CDATA[<p>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 of us, "Collection Site" might be the go-to term, while someone else prefers "Origin." Without a shared language, sharing information between genebanks could easily become a confusing tangle of spreadsheets and guesswork.</p>
<p>That's where the <strong>Multi-Crop Passport Descriptors (MCPD) 2.1</strong> come to the rescue!</p>
<!-- -->
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-exactly-is-mcpd">What exactly is MCPD?<a href="https://docs.genesys-pgr.org/blog/2026/07/15/mcpd-guide#what-exactly-is-mcpd" class="hash-link" aria-label="Direct link to What exactly is MCPD?" title="Direct link to What exactly is MCPD?" translate="no">​</a></h3>
<p>Developed through a partnership between Bioversity International and the FAO, MCPD 2.1 is essentially the gold standard for exchanging passport information. You can think of it as a universal "passport" for every plant genetic resource (PGR) in a genebank. It's here to make sure that no matter where a sample originates, its core identity (who collected it, where it was found, and what it is) is recorded in a way that everyone understands.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-key-pillars-of-the-standard">The Key Pillars of the Standard<a href="https://docs.genesys-pgr.org/blog/2026/07/15/mcpd-guide#the-key-pillars-of-the-standard" class="hash-link" aria-label="Direct link to The Key Pillars of the Standard" title="Direct link to The Key Pillars of the Standard" translate="no">​</a></h3>
<p>If you're exploring an MCPD record, there are a few fields that really do the heavy lifting:</p>
<ul>
<li class=""><strong>PUID (Persistent Unique Identifier)</strong>: In Genesys, we lean on <strong>DOIs</strong>. Think of a PUID as a digital fingerprint; it's what allows a researcher in Japan and a curator in Brazil to be absolutely sure they're talking about the exact same accession.</li>
<li class=""><strong>SAMPSTAT (Biological Status)</strong>: Is it a wild relative, a landrace, or a breeding line? Knowing the biological status helps us put all the other data into the right context.</li>
<li class=""><strong>ORIGCTY (Country of Origin)</strong>: To keep things crystal clear, we use ISO 3-letter codes. This avoids any mix-ups between "USA", "United States", and "U.S.A."</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-bother-with-standardization">Why bother with standardization?<a href="https://docs.genesys-pgr.org/blog/2026/07/15/mcpd-guide#why-bother-with-standardization" class="hash-link" aria-label="Direct link to Why bother with standardization?" title="Direct link to Why bother with standardization?" translate="no">​</a></h3>
<p>We know that following strict formatting rules (like using <code>YYYYMMDD</code> for dates) can feel like a chore, but the benefits are truly worth it:</p>
<ol>
<li class=""><strong>Better Searchability</strong>: You can search across hundreds of collections simultaneously because the data is predictable and consistent.</li>
<li class=""><strong>Seamless Interoperability</strong>: Your data can move effortlessly between Genesys, EURISCO, and the World Information and Early Warning System on Plant Genetic Resources for Food and Agriculture (FAO WIEWS).</li>
<li class=""><strong>Future-Proofing</strong>: Standards keep your data relevant and usable, even as the technology around us continues to evolve.</li>
</ol>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="ready-to-dive-in">Ready to dive in?<a href="https://docs.genesys-pgr.org/blog/2026/07/15/mcpd-guide#ready-to-dive-in" class="hash-link" aria-label="Direct link to Ready to dive in?" title="Direct link to Ready to dive in?" translate="no">​</a></h3>
<p>For genebanks looking to join the Genesys community, adopting MCPD 2.1 is a fantastic first step toward gaining global visibility. We're here to help you with the tools and guidance needed to map your existing data to these descriptors, helping you transform your internal archives into a valuable global resource.</p>
<p>Want to get started with standardization? Head over to our <a class="" href="https://docs.genesys-pgr.org/docs/providers/preparing-mcpd/mcpd-2.1">provider documentation</a> to dive deeper into the descriptors.</p>]]></content:encoded>
            <category>Data Standards</category>
            <category>MCPD</category>
        </item>
        <item>
            <title><![CDATA[Behind the Scenes: The Genesys Advisory Committee]]></title>
            <link>https://docs.genesys-pgr.org/blog/2026/07/08/advisory-committee</link>
            <guid>https://docs.genesys-pgr.org/blog/2026/07/08/advisory-committee</guid>
            <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Meet the experts guiding the strategic direction of Genesys and how community input shapes our platform.]]></description>
            <content:encoded><![CDATA[<p>Ever wonder how we decide which features to build next? Or how we make sure Genesys works just as well for a small national genebank as it does for a giant international center?</p>
<p>That's where our wonderful <a class="" href="https://docs.genesys-pgr.org/docs/governance/advisory-committee">Advisory Committee</a> comes into play.</p>
<!-- -->
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="our-strategic-compass">Our Strategic Compass<a href="https://docs.genesys-pgr.org/blog/2026/07/08/advisory-committee#our-strategic-compass" class="hash-link" aria-label="Direct link to Our Strategic Compass" title="Direct link to Our Strategic Compass" translate="no">​</a></h3>
<p>Think of the Genesys Advisory Committee as more than just a formal board; it's really our strategic compass. Comprising a group of international experts, the committee gives us the high-level guidance we need to keep the platform sustainable, relevant, and truly driven by the community.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-seat-for-everyone">A Seat for Everyone<a href="https://docs.genesys-pgr.org/blog/2026/07/08/advisory-committee#a-seat-for-everyone" class="hash-link" aria-label="Direct link to A Seat for Everyone" title="Direct link to A Seat for Everyone" translate="no">​</a></h3>
<p>We truly believe that the best decisions happen when a wide range of perspectives are at the table. That's why we've carefully designed our committee to represent the whole ecosystem:</p>
<ul>
<li class=""><strong>Data Providers</strong>: The curators and institutions who look after the collections.</li>
<li class=""><strong>Users</strong>: The scientists and breeders who use the data for their research.</li>
<li class=""><strong>Donors</strong>: The organizations that make our work possible.</li>
<li class=""><strong>Global Partners</strong>: Ex-officio members from the ITPGRFA Secretariat and the Crop Trust help us stay aligned with global standards.</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="from-dialogue-to-development">From Dialogue to Development<a href="https://docs.genesys-pgr.org/blog/2026/07/08/advisory-committee#from-dialogue-to-development" class="hash-link" aria-label="Direct link to From Dialogue to Development" title="Direct link to From Dialogue to Development" translate="no">​</a></h3>
<p>When the committee gets together, it's about much more than just reviewing reports. They dive into the tough, real-world questions:</p>
<ul>
<li class=""><em>Should we prioritize multilingual support or more advanced trait data?</em></li>
<li class=""><em>How can we better support curators in developing nations?</em></li>
<li class=""><em>What's the best way to handle the transition to new data standards?</em></li>
</ul>
<p>This kind of collaboration ensures that Genesys never grows in a vacuum. Every update we bring to the platform is shaped by the actual needs of the people who use it every day.</p>
<p>We're so grateful to all the current and past committee members who volunteer their time and expertise to help us safeguard the world's plant genetic resources for food and agriculture (PGRFA).</p>]]></content:encoded>
            <category>Governance</category>
            <category>Advisory Committee</category>
        </item>
        <item>
            <title><![CDATA[The Vision and Mission of Genesys]]></title>
            <link>https://docs.genesys-pgr.org/blog/2026/07/01/vision-and-mission</link>
            <guid>https://docs.genesys-pgr.org/blog/2026/07/01/vision-and-mission</guid>
            <pubDate>Wed, 01 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Exploring the core goals and the strategic role of Genesys in the global plant genetic resources ecosystem.]]></description>
            <content:encoded><![CDATA[<p>Have you ever wondered what keeps us motivated at Genesys? For us, it's a simple but deeply important goal: we want to make sure the world's plant genetic resources for food and agriculture (PGRFA) aren't just tucked away in quiet vaults. Instead, we want them to be easy to find and accessible to all the wonderful people working hard to feed our planet.</p>
<!-- -->
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="more-than-just-a-database">More Than Just a Database<a href="https://docs.genesys-pgr.org/blog/2026/07/01/vision-and-mission#more-than-just-a-database" class="hash-link" aria-label="Direct link to More Than Just a Database" title="Direct link to More Than Just a Database" translate="no">​</a></h3>
<p>You can think of Genesys as a friendly bridge. While genebanks do the incredible work of <em>ex situ</em> conservation, keeping seeds safe and viable for the long haul, that knowledge only really comes to life when breeders, researchers, and policymakers know exactly where to find it.</p>
<p>We're so proud to be a key part of the Global Information System (GLIS) of the ITPGRFA. Our dream is a world where detailed information on every single accession in the world's genebanks is just a few clicks away and free for everyone to use.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="our-mission-in-action">Our Mission in Action<a href="https://docs.genesys-pgr.org/blog/2026/07/01/vision-and-mission#our-mission-in-action" class="hash-link" aria-label="Direct link to Our Mission in Action" title="Direct link to Our Mission in Action" translate="no">​</a></h3>
<p>To make this dream a reality, we've focused on two main things:</p>
<ol>
<li class=""><strong>Helping you, the user</strong>: We've built a platform that lets you search through hundreds of collections all at once. We want to save you from those long hours of digging through dozens of different websites just to find one specific landrace or wild relative.</li>
<li class=""><strong>Supporting our genebanks</strong>: We're not just here to collect data; we're here to support the wonderful institutions that provide it. We love working side-by-side with genebanks to help them document and prepare their data according to international standards, ensuring their hard work is both recognized and truly useful.</li>
</ol>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-this-matters">Why This Matters<a href="https://docs.genesys-pgr.org/blog/2026/07/01/vision-and-mission#why-this-matters" class="hash-link" aria-label="Direct link to Why This Matters" title="Direct link to Why This Matters" translate="no">​</a></h3>
<p>Whether it's helping crops adapt to our changing climate or rediscovering a forgotten trait that could fight off pests, it all starts with a simple discovery. By bridging the gap between the seed vault and the researcher, we're together helping to build a more resilient food system for everyone.</p>
<p>If you're a breeder or researcher, we'd love for you to <a href="https://www.genesys-pgr.org/" target="_blank" rel="noopener noreferrer" class="">explore the collections</a>. And if you manage a genebank, we'd be truly honored to help you share your treasures with the rest of the world.</p>
<p>If you'd like a more detailed look at our strategic framework, feel free to read our <a class="" href="https://docs.genesys-pgr.org/docs/governance/vision-and-mission">Vision and Mission</a> and explore the <a class="" href="https://docs.genesys-pgr.org/docs/governance/genesys-strategy">Genesys Strategy</a>.</p>]]></content:encoded>
            <category>Vision &amp; Mission</category>
        </item>
    </channel>
</rss>