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.

Sign up for GitHub

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

Jump to bottom

Don't allow duplication of SIP plans #12

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

Don't allow duplication of SIP plans #12

toraritte opened this issue May 20, 2023 · 1 comment
Labels
for_stakeholders

Comments

@toraritte
Copy link
Member

toraritte commented May 20, 2023 •
edited
Loading

SIP plans are the equivalent of authorizations for CORE, but for SIP, and the same arguments about their uniqueness apply (see issue #11 "Don't allow the duplication of authorization numbers"). (Note: SIP notes are similar to lesson notes for CORE.)
@toraritte
Copy link
Member Author

Currently, it is named by concatenating

  1. date
  2. instructor
  3. service (area?)

This would be a good starting point for a composite key. Maybe the date and service area would be enough? (or replace date with datetime)

@toraritte toraritte mentioned this issue May 20, 2023
Open
@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
Assignees
No one assigned
Labels
for_stakeholders
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@toraritte