You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Who are the primary contacts for this story
Danni, Adam F
Acceptance criteria
After scanning a plate or tube rack into Asset Audits, if it is imported from 'wrangler' or 'lighthouse', I can see its priority. The priority of the labware is calculated as the same as the highest priority of its samples.
See priority on Wrangler samples
See priority on LH samples (BLOCKED)
Dependencies
This story is related to the following:
Lighthouse: doesn't seem to expose priority information
Lighthouse information comes from the Mongo Database populated by the wrangler, thus any priority information would need to come through the CSV files provided by the labs. This doesn't appear to be the case currently.
Currently not part of the requirements, but would be theoretically possible. Would be another API call on an already slow process though. Theoretically you could unify the wrangler and LH summary imports under a single SS call, but this would tie you to synchronous import.
User story
Extracted from #149
Who are the primary contacts for this story
Danni, Adam F
Acceptance criteria
After scanning a plate or tube rack into Asset Audits, if it is imported from 'wrangler' or 'lighthouse', I can see its priority. The priority of the labware is calculated as the same as the highest priority of its samples.
Dependencies
This story is related to the following:
(not actually blocked because the priority info can be retrieved from the MLWH)
The text was updated successfully, but these errors were encountered: