Skip to main content

Genesys

Integration with Genesys requires configuration of connection parameters in Application settings.

Connecting with Genesys

Genesys client

Contact helpdesk@genesys-pgr.org to register your GGCE as a Genesys client for your genebank.

Please indicate in your request if you wish to connect with Sandbox or with the Production environment, specify your FAO institute code, and the URL of your GGCE. They will respond with genesysUrl, clientId and clientSecret that are registered in Admin > Application settings.

Application settings

Your GGCE Adminstrator must register the following Application settings in the GENESYS_CLIENT category to make this work:

Category tagVariable nameDescription
GENESYS_CLIENTgenesysUrlGenesys API URL
GENESYS_CLIENTclientIdClient ID registered on Genesys
GENESYS_CLIENTclientSecret... and secret provided for your GGCE instance
GENESYS_CLIENToriginURL of your GGCE as registered in Genesys
GENESYS_CLIENTinstCodeThe WIEWS institute code of your genebank
GENESYS_CLIENTneverUploadFieldsOptional: A comma-separated list of MCPD fields to exclude
GENESYS_CLIENTdebugOptional: Set to Y to print debug messages in your server's logs

Sharing limited data with Genesys

GGCE uses the data flagged as Is Public to produce MCPD which is then uploaded to Genesys. You can use this flag on accession, accession source and other records to prevent it being shared with external users.

The setting neverUploadFields allows you to configure a list of MCPD fields that will not be shared with Genesys. These will set to null and will be completely cleared from Genesys. Please use sparingly and with care.

Genesys and GLIS

This will affect the data in ITPGRFA GLIS for accessions that have a DOI as GLIS automatically retrieves latest updates from Genesys!

Excluding coordinate data

To exclude only the coordinate data from being shared with Genesys you can use:

Category tagVariable nameValue
GENESYS_CLIENTneverUploadFieldsdecLatitude,decLongitude