Support for DNAsample UUID

Objective

Clients need to be able to associate the genotyping data collected on a sample with the phenotyping data collected in the field to make breeding decisions. In the last year the CGIAR community has settled on using a unique sample ID to be able to track samples generated across multiple instances and types of breeding management and sample tracking systems. The ideal unique sample ID is the sample UUID (universally unique identifier),  which is a 128-bit number used to identify information in computer systems such as  123e4567-e89b-12d3-a456-426655440000. However, since there is still not complete standardization of sample IDs, there is some variation on length and mix of numbers and characters.

We cannot use the Sample UUID as the sample name, since users still need a readable sample name. Therefore, we need another field to be able to store this sampleUUID.

Since it is an important concept/field in the CGIAR community, we need to be able to search on this field. Therefore, it should be a key field or a props field that can be easily searched on.

It should ideally be a required field, but we need to be able to accommodate legacy data that does not have this field included.

We need to be able to extract these metadata fields in the sample.file and see them in the hapmap extract file with the other metadata

It should be at the dnasample level as this is a field associated with the dnasample. It will be a one-to-one relationship with the sample_name

Clients are also starting to add UUIDs to the plate level. It would also be good to add a PlateID field as well as having a plate name. This field doesn't need to be highly searchable.

While we are adding fields to the sample table, it would be good to add a row_column plate field since that is how samples are usually labelled e.g., as A01, not separate columns of row = A and column = 1

Success metrics

Assumptions

1. Client has generated UUID for samples using an acceptable standard
2. Client has validated UUIDs for samples
3. Curators have ensured that UUIDs can be connected to appropriate data in Germplasm management system
4. Sample UUID == sample code

Stories

User interaction and design

Open Questions

Out of Scope

• GDM will not generate/modify any sample UUIDs