The amplicon_size field in Mpox is an integer but the example provided lists 300 bp but that would be invalid input. In some lists (like GRDI) it is an integer and the example is 300 which is fine, except the guidance says "expressed in base pairs" which may cause people to include bp. In Cancogen the fields is a whitespacestring and so it's fine that it gives the 300bp example and asks to include units in the guidance, but can we update the guidance/examples to fit better with the input types? For the harmonized version I am going to make it integer compatible and just have it ontologically associated with the bp .
The
amplicon_sizefield in Mpox is anintegerbut the example provided lists300 bpbut that would be invalid input. In some lists (like GRDI) it is anintegerand the example is300which is fine, except the guidance says "expressed in base pairs" which may cause people to includebp. In Cancogen the fields is awhitespacestringand so it's fine that it gives the300bpexample and asks to include units in the guidance, but can we update the guidance/examples to fit better with the input types? For the harmonized version I am going to make itintegercompatible and just have it ontologically associated with thebp.