6.0 Feedback: mounts described as "empty" when they aren't or don't need to be

[ecormany]

Overview

The app is too liberal in using the term "Empty" for pipette mounts. We should adopt clearer language on the Devices and Protocols page.

Current Behavior

Robots page

On the robots page, both mounts for unavailable robots are listed as "Empty". Since the robots aren't in communication with the app, that information may be incorrect (and likely is incorrect in settings where users don't remove their pipettes).

Protocols page

If a protocol only uses a single pipette, it lists the other mount as "empty". This makes it seem like the protocol requires that the other pipette be removed in order to run it, when this is not the case.

Expected Behavior

Robots page

The mount sections should either show:

1. The pipettes that were in place when the robot was last seen.
2. Some text expressing that the information is not available: e.g. "Unknown" or an em dash

Protocol page

The unused mount should say "Unused" or "Not used".

Steps To Reproduce

View any unavailable robot on the Robots page or any loaded protocol on the Protocols page.

Operating system

Mac

Robot setup or anything else?

No response

[koji]

@emilywools @mmencarelli
What do you think about this?

Another question empty 's first letter should be a capital letter?

[nusrat813]

Addressing Ed's expected behavior comment #1 - #10032

[ecormany]

Another question empty 's first letter should be a capital letter?

I think initial capital on any of the language we wind up using, so: Empty, Unused, Not used, Unknown, etc.

[nusrat813]

@mikecardarelli - to ticket
protocol page - unused
wording for empty not needed because section will be taken out

[mikecardarelli]

New ticket for "Not used" pipettes: https://app.zenhub.com/workspaces/app--ui-5f6248dba845b000139aa767/issues/opentrons/opentrons/10180

[nusrat813]

PR Merged - https://app.zenhub.com/workspaces/app--ui-5f6248dba845b000139aa767/issues/opentrons/opentrons/10188

[y3rsh]

I think this is good