DPL-310 Destruction feature to move labware to LabWhere 'destroyed' location (C=M)

[KatyTaylor]

User story
As a Sample Management or Heron user I would like the destruction feature of Asset Audits to move the labware to a special location in LabWhere that I use to indicate that labware are destroyed, so that I don't have to go to LabWhere separately to do this.

Who are the primary contacts for this story
Danni & Anna G

Acceptance criteria
To be considered successful the solution must allow:

• Labware marked for destruction in Asset Audits should also have their locations updated in LabWhere, to a special 'destroyed' location.
• There is messaging on the page to explain this is what will happen, and feedback to say whether the update in LabWhere was successful or not.

Additional context
Asset Audits has its own event-based way of marking a labware as destroyed. However, the Asset Audits feature is not being used, and the accepted way of marking labware as destroyed is to use these special locations in LabWhere.

[TWJW-SANGER]

There are a 6 "Destroyed" locations within labwhere (search for 'Destroyed'). We may need clarity on which one to use or allow users to choose....

[SujitDey2022]

A process improvement requirement to help reduce manual efforts when destroying multiple samples and derivatives.

[SujitDey2022]

09Jan2024 - Team Discussion

1. Which of the 6 Destroyed location is to be considered as 'Destroyed' location?
2. Do we need to identify the need for data migration from some or all locations to the new one?

[SujitDey2022]

17Jan2024 - Team Discussion

1. Create new single location to be created in 'Labwhere' with destroyed labware type.
2. Currently tableau is used to report on archived samples which may also have location information.
3. Nice to have people destroying samples using Asset Audits and only limited access for the ones who can do it in 'Labwhere'

[yoldas]

Notes:

• Destroying labware process does not require instrument barcode.

destroy_labware:
  name: Destroying labware
  request_instrument: false
  visual_check_required: false

• Asset Audits uses Sequencescape API for users, however Labwhere has its own users table.

[yoldas]

Assumptions

My current assumption is that barcode of the user from SS matches the Labwhere user barcode. If they are the same, Asset Audit post for "Destroying Labware" process becomes simply including a second post to Labwhere to set the unique Destroyed location for the listed barcodes.

When user selects Asset Audits "Destroying Labware" process, we will display info about what will happen. After submit, any errors from Asset Audit post and the secondary Labwhere "post" will be consolidated and shown. On success, a feedback will be shown about the destruction and the location is also set in Labwhere.

Existing Form Screenshots

Asset Audits	Labwhere

Database schemas

Asset Audits (SS)	Labwhere Users

How to do a "Two phase commit" involving two apps after validation?

WIP

[yoldas]

• Create Story1: Updating swipecard in SS Profile will update Labware swipecard as well.
• Create Story2: Create an endpoint in Labwhere for sync.ing barcode as well and provide a UI to sync.
• Write down a confluence page to explain the auth and relationships of the apps.

[yoldas]

I have done some further research and written a Confluence article:
User authentication, swipe-cards, barcodes and relationships between apps

[yoldas]

I have created the following stories for synchronising the user swipe-cards and barcodes across applications:

• Y24-116 Use the same user swipe-card codes in Sequencescape, LabWhere and Asset Audits labwhere#784
• Y24-117 Use the same user barcodes in Sequencescape, LabWhere and Asset Audits labwhere#785