Refactor extended time database model to be more efficient

Laura had an uber-test plan on for all of this at

https://jira.sakaiproject.org/issues/?jql=text%20~%20%22qti%22%20and%20status%20in%20(open%2C%20%22awaiting%20review%22)%20and%20project%20%3D%20sam

I feel like that's really good. The only open issues I still know of are

• : Improved process for editing an existing row.

  • This is in progress

• : Settings are not saved unless user clicks to add exception

  • I think with the new UI that Sam did, it's a lot more clear and this isn't as necessary

• : Excepted students cannot view the test when site-level retract date is set to if "Late submission is not accepted"

  • This is one I still plan to investigate and improve. The issue is that on the regular date selection there's a "yes/no" for late submission, but there (currently isn't) on extended. It seems like if it's "No" then no dates in extended override this no. I think it should just have the date blank (for no override) or filled in (for override)

Test plan ? Is there an uber-test plan for all these related issues?

I merged this initial work and created/moved open subtasks related to this. Wait to verify/merge this until all of the subtasks are resolved.

, I'm working on it right now. I welcome any efforts towards collaboration.

EDIT: I have the hibernate / object part done. I am partially done with the front end (the framework is written, but a lot needs to be done to make it functional). I have a partial DAO. I'm currently working on making an actual Service for ExtendedTime. Of course, everything is harder in Samigo.

Is this something you're working on? These jiras were something I (Longsight) was planning on getting done prior to 11.3 since I didn't believe anyone else was going to pick it up.