Details
-
Improvement
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
-
Data Standard Sprint 22, Data Standard Sprint 23
-
2
Description
Similar to DATASTD-891, review options for reducing the natural key volatility of Session. Feedback from Infinite Campus on ODS-2508 is copied below, and the example file is also copied to this ticket. The main concern seems to be around Session Name. Another implementation solution to solve the use case is to add the "allow primary key updates" language feature to Session, which would introduce cascades into the generated sql, but this is considered to be a non data standard concern. This ticket should primarily focus on options for adjusting the modeling of Session to improve these scenarios.
Hi all, we are in development for the 3.1 version and have come across this issue again in development and would like to put it on the radar again to consider adding cascading updates again to all dependent resources under Sessions: Course, Course Offering, Section, Student Section Association, Staff Section Association, Grades, Student Section Attendance Events.
In going back to the example I provided above, we are still struggling with a solution to not have to change the Session Name when a school changes their Term Descriptors. I have provided a screen shot above of how a school would start out aligning their terms to a Term Descriptor and then change it. Any recommendations would be helpful as well on how to handle this situation if cascading updates cannot be turned on. Sessions.pdf
Attachments
Issue Links
- relates to
-
DATASTD-1973 Documentation Assessment for Term and Session
-
- Closed
-
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-