Details
-
Improvement
-
Resolution: Done
-
Minor
-
None
-
None
-
DS Refinement, Data Standard Sprint 22, Data Standard Sprint 23, Data Standard Sprint 24
-
2
Description
In my experience sending gradingPeriods (and grades as a result), there has been quite a bit of difficulty in creating unique gradingPeriods that match our own data representation. The key is very rigid and the only value we can really "fudge" for uniqueness is periodSequence. I would not say it's typical that schools would configure things in such a way that would give us issues, but the possibility of it means we have to program around it.
I would suggest a change similar to the addition of SessionName between suite 2 and 3. Having some kind of text-field we could add additional uniqueness values to would be a lifesaver. Currently we succumb to getting all our gradingPeriods and then ordering them in ways that are 'unnatural' to our own data in order to determine the key, which includes on the per-grade level, whereas ideally we'd only need information on the one gradingPeriod we're sending grade(s) for.
Like with SessionName, this might also result in less volatile keys. Right now adding a single gradingPeriod could potentially cascade to all the rest of them since periodSequence is our only outlet of uniqueness, which I know relates to historical issues with this resource.
Attachments
Issue Links
- is covered by
-
DATASTD-2074 GradingPeriod Sample Data Updates
- Closed
- mentioned in
-
Page Loading...