GAPS: Link stock data to specific storage temperature ranges

[adamdewey]

Is your feature request related to a problem? Please describe 👀

Part of Epic https://github.com/msupply-foundation/open-msupply/issues/4362

Describe the solution you'd like 🎁

You can already assign multiple locations to a cold chain asset:

So just need to add temperature_range to a location. This would need to be stored in OMS central, on the location table (much like the name_oms_fields extension of the name table)

Show the temperature range in brackets after the location name, when selecting the location for a stock line (i.e. in inbound shipment)

This can then be used in dashboard queries

Additional context 💌

User story	A.6.2
As a…	Health Care Worker (HCW) or warehouse worker
I want…	Stock inventory data to be associated with the correct cold storage location
So that…	I can see exactly what stock each CCE is storing at any given time

Solution A.6.2

The system will allow for users to make the association between stock storage locations and CCE by providing a mechanism to create new stock storage locations that represent the cold storage within CCE.

Multiple locations will be possible for each CCE and the user will be able to specify which type of cold storage they are associated with - e.g. +5 °C and -20 °C for hybrid refrigerator / freezers.

Note: the exactly what stock each CCE is storing would be nice but not required at this stage 🙏

Moneyworks Jobcode 🧰

CCEIDEV

[lache-melvin]

Some decision changes since above!

• GAPS script will configure 3 location_type records in OG, for +5, -20 and -70
• Create new translation for location_type in OMS (OG central data pull)
• Add location_type_id to the location sync translations
• Add location_type dropdown to the location edit modal in OMS
• Display the location_type description (/name?) in parentheses in the location select dropdowns

Somewhere we will create a mapping to be used for the dashboards, deriving the known temperature ranges from the location_types to line up with the rest of the GAPS data

[mark-prins]

Thanks Laché that's great! There is some practical cross-over with the storage capacity properties of cold chain equipment:

and

We've talked about implementing a dashboard or report to show available volume and volume used. The question is whether we bring across the location volume from OG, or use the volume property from the asset. While not ideal, we can make do with the latter for now.

[jmbrunskill]

We've talked about implementing a dashboard or report to show available volume and volume used. The question is whether we bring across the location volume from OG, or use the volume property from the asset.

I think there's potential for locations to be broken down more than what's in the asset. E.g. you could a location for each shelf in a fridge. Ideally the system should warn or stop the user from a assigning more volume that the asset actually has. I agree we can live with using asset volumes for now, but thought I'd mention...

[adamdewey]

Ideally the system should warn or stop the user from a assigning more volume that the asset actually has.

Agree, also ideally the system would actually create a stock location with the appropriate temperature range when creating an asset..

[CarlosNZ]

5179

[CarlosNZ]

Just re-opening until I add in the front-end mutation to update the cold storage setting on location.

Will also need coldStorageType GraphQL node to get the list of storage types