Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strain Name reported is not linked to the license number - Strain Update Duplicate but then Fails #67

Open
djbusby opened this issue Apr 4, 2023 · 3 comments

Comments

@djbusby
Copy link
Member

djbusby commented Apr 4, 2023

On 3/22 we had uploaded some variety data, including a variety called 'BreathWorks'.
Attached in file 'Strain_AF0E72B77C_01GW3QA6QPN565X25549JF4HBV.csv'

We received a response from CCRS that shows this strain is a DUPLICATE.
Attached as Strain_20230321T210800142.csv

This is expected, this means that CCRS has recorded this strain for this licensee: 417401 and the strain is valid.

Then we've uploaded Inventory_AF0E72B77C_01GX4YYZ2P4V0TC3YX837GDJF4.csv (also attached)

And we received an error message in Inventory_AF0E72B77C_20230403T184950162.csv, specifically:

-system-,03/13/2023,Strain Name reported is not linked to the license number. Please ensure the strain being reported belongs to the licensee,417401,01GV495C708A6326,,,INSERT,ACC,BreathWorks,Clones,,,.00,False,

And this is a big problem, because on March 21 your system reported that 'BreathWorks' was a duplicate strain; which means you had it recorded for this license. But then on the update of April 04 we've been told that strain is not valid. Notice that all of this occurred AFTER the March 14th announcement by the LCB of the "bug" affecting strain data in CCRS.

It's very difficult to keep information in CCRS updated when the system provides us with conflicting information.
There is no way for us to resolve it either; as re-uploading the strain provides the strain-duplicate error.
And re-uploading the inventory provides the strain-missing error.
Does CCRS have this strain for this licensee or not?

This issue of strain-data inconsistencies is affecting at least dozens of licensees and 100s of strains.
When inventory uploads are block because of this.
Then manifests fail.

IR74879

@djbusby
Copy link
Member Author

djbusby commented Apr 4, 2023

This got two tickets from LCB IR74864 and then also IR74879.
And they've closed IR74879

Assigned to: Kelly, Joseph (LCB)
Resolution Category: Cancelled
Resolution Comment: did not need to be escalated

Status of IR74864 is unknown.

@djbusby
Copy link
Member Author

djbusby commented Apr 6, 2023

Have gotten a correction from the LCB via IR74864. It was an "issue with strain attribution" which LCB has corrected. Must now re-upload all strain data. Also, have to diagnose this for a few 100 other licensees :(

@djbusby
Copy link
Member Author

djbusby commented Apr 6, 2023

Have reported the issue for 15 total licenees.

@djbusby djbusby changed the title Strain Update Duplicate but then Fails Strain Name reported is not linked to the license number - Strain Update Duplicate but then Fails Jul 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant