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

Legacy License Data Cleanup Issues #70

Open
djbusby opened this issue Jun 5, 2024 · 0 comments
Open

Legacy License Data Cleanup Issues #70

djbusby opened this issue Jun 5, 2024 · 0 comments

Comments

@djbusby
Copy link
Member

djbusby commented Jun 5, 2024

In some situations a license will change onwers.

Here we had a case where LicenseA was owned by one party in 2021, 2022 using SoftwareA.
In 2023 LicenseA was sold to a new individual.
In 2024 the agency provided a report to the current owner of LicenseA that there were data errors.
The LCB has asked the 2023 owner of LicenseA to correct the data from before they owned the license.

It's a little awkward to be asked to update data for a license from before the current party was responsible for said data.

It's also been our experience that the agency has licensees "clean-up" their data before being sold/transferred. Perhaps that just slipped by in this case.

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