Mouthwash kit receipt error in Biospecimen Dashboard ( May release)

[erincschwartz]

FNL reported the following error when attempting to receipt mouthwash kit, Collection ID CHA000022 0007 in the Biospecimen Dashboard

Prod data showed the tracking number as

FNL reports that they did not receive any error messages after scanning the kit tracking number, they received the checkmark in the Dashboard.

@JoeArmani suggested FNL attempt to manually enter the tracking number with the parenthesis. FNL was able to receipt the kit and all receipt data populated on the back end.

[sonyekere]

Hi @erincschwartz is this also connected to issue #970 ?

[erincschwartz]

@sonyekere I do not believe this is directly related to #970. @JoeArmani, thoughts?

[JoeArmani]

@sonyekere @erincschwartz I agree that it's a separate issue. It would probably be most efficient for a single developer to tackle the range of Home Collections issues for familiarity and also to avoid merge conflicts (if they're all resolved in the upcoming cycle).

[sonyekere]

Thanks Both. @JoeArmani good point!

[amber-emmes]

This issue is currently planned to be resolved by automatically stripping non-numeric characters from barcodes entered in this field on the mouthwash kit receipt page.

1. Is this as desired?
2. Should any other pages, such as the mouthwash kit assembly and assign pages, also be updated to strip non-numeric inputs from entered tracking numbers?
3. Will a data update script be needed to strip erroneous parentheses from existing data?

[JoeArmani]

@amber-emmes @erincschwartz Erin, please confirm/update this:

1. The issue starts with the scan in 'Assemble Kits.' We need to eliminate this possibility throughout the process.
2. Please ensure all the tracking number fields allow numeric input only. I'd mock the returned data from the scanner to make sure the process works as expected -- they will be using a scanner in real-time (not manual entry).
3. We'll want to update those records in prod. There are only 4 records with this issue currently. @erincschwartz should this go into the prod changelog or are you expecting many more in the upcoming weeks?

[amber-emmes]

A PR to fix this going forward has been submitted; however, it will not fix the existing records in prod, which must be fixed separately. I would also like to see about updating the backend to strip non-numeric characters from tracking numbers to further harden this.

[erincschwartz]

We will request a prod change for existing records to coincide with the Prod release, as there may be more cases in the meantime if FNL team forgets to remove the parenthesis. That way, will not have to make multiple prod change requests.

[amber-emmes]

This is now in dev and ready for testing.

[wyattks]

Parenthesis automatically were removed when scanned in for the kit.

Tested in Dev. Ready for Stage.

[wyattks]

Tested in Stage. Ready for Prod.

[amber-emmes]

This is now in prod.