Name resolution using OT services was a bottleneck during load testing. Possible solution is to use GNRD to resolve against OTT. GNRD can match against OTT, returning ottids, which means we can replace OT taxonomy services with GNRD. This means fewer steps, also probably faster and more robust. GNRD also can include valid names that do not match OTT.
Therefore GNRD can replace OT taxonomy services in all workflows.
[ ] Dima: please explain how to invoke GNRD to get the desired result. Provide a test case.
[ ] Abu: please make sure the phylotastic wrapper service supports the above options
Name resolution using OT services was a bottleneck during load testing. Possible solution is to use GNRD to resolve against OTT. GNRD can match against OTT, returning ottids, which means we can replace OT taxonomy services with GNRD. This means fewer steps, also probably faster and more robust. GNRD also can include valid names that do not match OTT.
Therefore GNRD can replace OT taxonomy services in all workflows.