While writing transformer functions for the new SESAR - iSamples sync, I noticed some inconsistencies in the SESAR fields used for mapping to iSamples.
Description
IEDUT103B: Sample classification, collection method, and sample description
EOI00002H: Not Provided, missing available data used in example 1
Example 3: I'm not sure as to why the SESAR internal database id is considered an "alternate identifier".
While writing transformer functions for the new SESAR - iSamples sync, I noticed some inconsistencies in the SESAR fields used for mapping to iSamples.
Description
IEDUT103B: Sample classification, collection method, and sample description
EOI00002H: Not Provided, missing available data used in example 1
Example 3: I'm not sure as to why the SESAR internal database id is considered an "alternate identifier".
Produced By Label
EOI00002H: Collection Method
IEDUT103B: Cruise Field Program
IEEJR000M: "collection event" string
Produced By Description
EOI00002H: Cruise Field Program, Launch Platform Name, Collection Method, Sample Description,
IERVTL1I7: Missing available cruise field program
IEDUT103B: Missing available cruise field program and sample description
Produced By Reponsibility
ODP02Q1IZ: Cruise Field Program as Sponsor
EOI00002H: Collector, missing available sponsor
IEDUT103B: Empty, Missing available collector and sponsor
Sampling site Description
EOI00002H: location description
IEDUT103B: locality description
IEJEN0040: sample comment
The current output from the sync functions can be found here.