assessmentIdentificationSystemDescriptors State Awareness

REF:

• assessmentIdentificationSystemDescriptors
• POST /assessments

ISSUE: Vendors need state awareness of assessmentIdentificationSystemDescriptors to avoid error responses on POST /assessments

VENDOR OPTIONS

1. Always POST (UPSERT) to assessmentIdentificationSystemDescriptors, prior to POST /assessments and allow a wasted transaction if descriptor already exists (Wasteful)
2. Put error handling around error message (not error code) returned for assessmentIdentificationSystemDescriptor doesn't exist, and POST a new one to /assessmentIdentificationSystemDescriptor (String Error Parsing is never preferred)
3. Option 2 + Store in our DB that the descriptor exists. This could pre-eliminate errors returned by the ODS (Getting tightly coupled here)

EDFI OPTIONS

1. Make assessmentIdentificationSystemDescriptors be a UPSERT in the POST /assessments call. It already allows VENDORS to create them without scrutiny in the POST /assessmentIdentificationSystemDescriptors call. Why make Vendors take a additional step, and require state awareness? (My preferred, and most future proof option if Vendors are supposed to have POST control over assessmentIdentificationSystemDescriptors)
2. If District discretion is the reason for this roundabout way of performing these actions, then
   i. Cut of VENDOR POST access to the assessmentIdentificationSystemDescriptors
   ii. Look at standardizing descriptors to a base ODS set, rather than a district specific
   set. This would make it so Vendors always know that X ODS will have X Descriptor we will always use
3. Allow ODS's to create their own
   assessmentIdentificationSystemDescriptors sets and require Vendor to make
   descriptors a configurable. I assume this isn't the only descriptor I'm going to be running into this problem with, so the configurations could get lengthy here.
4. Make the Vendors maintain state / error handling from this (See VENDOR options)