Skip to content

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

@djbusby

Description

@djbusby

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions