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

Don't allow the duplication of authorization numbers #11

Open
toraritte opened this issue May 19, 2023 · 1 comment
Open

Don't allow the duplication of authorization numbers #11

toraritte opened this issue May 19, 2023 · 1 comment

Comments

@toraritte
Copy link
Member

Authorization numbers are unique therefore they should be treated as such by the database as well but mostly because it is super error prone entering the same identifier by hand multiple times (as it is currently done).

Complicating factors:

  1. Multiple service areas per authorization

    For example, AT, ILS, Braille, and O&M under one auth.

  2. "TEMP" auths

    Sometimes auths are not received by us, but clients are supposed to start receiving services on a certain date. Also, the previous items applies here as well, that further complicates the situation, because there can be multiple TEMP auths, all of which could apply to multiple service areas.

@toraritte
Copy link
Member Author

Composite key for authorization ID + service area? But what about TEMP authorizations?

@toraritte toraritte added help wanted Extra attention is needed for_stakeholders and removed help wanted Extra attention is needed labels May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant