Genesys
Integration with Genesys requires configuration of connection parameters in Application settings.
Connecting with Genesys
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 tag | Variable name | Description |
|---|---|---|
GENESYS_CLIENT | genesysUrl | Genesys API URL |
GENESYS_CLIENT | clientId | Client ID registered on Genesys |
GENESYS_CLIENT | clientSecret | ... and secret provided for your GGCE instance |
GENESYS_CLIENT | origin | URL of your GGCE as registered in Genesys |
GENESYS_CLIENT | instCode | The WIEWS institute code of your genebank |
GENESYS_CLIENT | neverUploadFields | Optional: A comma-separated list of MCPD fields to exclude |
GENESYS_CLIENT | debug | Optional: 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 or used for DOI registration. Please use sparingly and with care.
This affects data shared with both Genesys and ITPGRFA GLIS. Fields listed here are omitted when sending data to Genesys and GLIS.
Supported field names
The neverUploadFields value is a comma-separated list of the field names below. Fields marked Yes in the GLIS DOI request column are also respected when data is submitted to GLIS for DOI registration.
| Field | Description | Genesys upload | GLIS DOI request |
|---|---|---|---|
puid | Persistent unique identifier (DOI) | Yes | Always |
acceName | Accession name | Yes | Yes |
acceUrl | Accession URL | Yes | Never |
acquisitionDate | Acquisition date | Yes | Yes |
ancest | Ancestral data | Yes | Yes |
availability | Availability for distribution | Yes | Never |
bredCode | Breeding institute code | Yes | Yes |
bredName | Breeding institute name | Yes | Yes |
collCode | Collecting institute code | Yes | Yes |
collDate | Collecting date of sample | Yes | Yes |
collInstAddress | Collecting institute address | Yes | Yes |
collMissId | Collecting mission identifier | Yes | Yes |
collName | Collecting institute name | Yes | Yes |
collNumb | Collecting number | Yes | Yes |
collSite | Location of collecting site | Yes | Yes |
collSrc | Collecting/acquisition source | Yes | Yes |
coordDatum | Coordinate datum | Yes | Yes |
coordUncert | Coordinate uncertainty | Yes | Yes |
cropName | Common crop name | Yes | Yes |
curationType | Curation type | Yes | Never |
decLatitude | Latitude of collecting site | Yes | Yes |
decLongitude | Longitude of collecting site | Yes | Yes |
donorCode | Donor institute code | Yes | Yes |
donorName | Donor institute name | Yes | Yes |
donorNumb | Donor accession number | Yes | Yes |
duplSite | Location of safety duplicates | Yes | Never |
elevation | Elevation of collecting site | Yes | Yes |
geoRefMeth | Georeferencing method | Yes | Yes |
historical | Status of the accession in the collection | Yes | Always |
mlsStat | MLS status of the accession | Yes | Yes |
origCty | Country of origin | Yes | Yes |
otherNumb | Other identifiers associated with the accession | Yes | Yes |
remarks | Remarks | Yes | Never |
sampStat | Biological status of accession | Yes | Yes |
species | Species | Yes | Yes |
spAuthor | Species authority | Yes | Yes |
storage | Type of germplasm storage | Yes | Never |
subtAuthor | Subtaxa authority | Yes | Yes |
subtaxa | Subtaxon | Yes | Yes |
genus, sampleid (the accession number), historical and puid are always sent to GLIS and cannot be excluded with neverUploadFields.
Excluding coordinate data
To exclude only the coordinate data from being shared with Genesys you can use:
| Category tag | Variable name | Value |
|---|---|---|
GENESYS_CLIENT | neverUploadFields | decLatitude,decLongitude |