Page Comparison

...

Show the IOR and the course CRN.
The UI should have the subject code, the course number, the section number, the term and the CRN (not necessarily in this order).
The UI should pre populate grades to its grade field as transferred to it by the course converter tool.
Avoid horizontal scrolling where possible. Put the grade input field in one of the first few columns.
- Target screen resolution: ??
Default sort order is by student name (Last, First Name), then CRN.
Has button to submit to final grade submission tool.
Has button to save input and allow user to exit. NOTE: If we use AJAX, this may not be applicable.

Technology Related Questions

...

Question
Answer
Add the Banner student ID as well?

Is it a Sakai tool/service?

What is the requirement for storing data entered on the page?

If the tool needs to persist data in a data base, should it use one the existing
Sakai or UCD DataSources or should it use it's own one?

What is the requirement for storing data entered on the page?

Will the unsubmitted data need to persist between user sessions? If so,
do we assume the next user session is on the app server saving the data
or can it be any member of the cluster?

What are the logging/auditing requirements for the app? Should logging/auditing be
done in the DB or is a file alone okay? Should we be using standard sakai
services(ala events/sessions/etc) to make things easier on Dave W, ITX, and you?
Since this is an external tool, do we have to skin it?
Probably but as simply as possible.
How can an end user input grades, save, and return to complete the final grade submission transaction?

How do we transfer data from the course converter tool to this landing page tool?
- REST, SOAP, GWT-RPC, ...
Don't know yet.
What data format shall be used to transfer data from the course converter tool to
this landing page tool?

Should the landing page write the final grade file to AFS?

Do we need the Final Grade Submission tool to change also?

What happens if the end user hits the back button while inputting grades?
-- Could this be used as "undo"

At waht what time is user input persisted, it at all?
-- using AJAX after each field edit
-- once by clicking on "save/submit" button

What software development tools will be used for programming
the landing page tool?

General Questions:

Question	Answer
Add the Banner student ID as well?
Since this is an external tool, do we have to skin it?	Probably but as simply as possible. TPA: Enduser experiance should set the standard
Should the landing page write the final grade file to AFS?
Do we need the Final Grade Submission tool to change also?
Can the landing page tool look up the grading option for the student's enrollment information?	We carry this information in one of our tables.
If we have the student's enrollment grading option for the course, can we reveal this to the end user? If not, we just pass along to the output file whatever grade the end user inputs.	Answer from the Reg Office: The faculty is not supposed to know about the option for Pass No Pass grading. The letter grade is supposed to be submitted to registrar's office. The option on the grading is handled when the grade rolls to history in Banner.
Does the landing page tool perform any other grade look up validation?
Can the landing page tool look up the grading mode for the course?	We don't carry this information in our external database. Need to determine if we can get this, and if so if how we would implement different drop-downs for the relevant grading mode.	What software development tools will be used for programming the landing page tool?

Versions Compared

Old Version 11

New Version 12

Key

Technology Related Questions

General Questions:

Question	Answer
Add the Banner student ID as well?
Is it a Sakai tool/service?
What is the requirement for storing data entered on the page?
If the tool needs to persist data in a data base, should it use one the existing Sakai or UCD DataSources or should it use it's own one?
What is the requirement for storing data entered on the page?
Will the unsubmitted data need to persist between user sessions? If so, do we assume the next user session is on the app server saving the data or can it be any member of the cluster?
What are the logging/auditing requirements for the app? Should logging/auditing be done in the DB or is a file alone okay? Should we be using standard sakai services(ala events/sessions/etc) to make things easier on Dave W, ITX, and you?	Since this is an external tool, do we have to skin it?	Probably but as simply as possible.
How can an end user input grades, save, and return to complete the final grade submission transaction?
How do we transfer data from the course converter tool to this landing page tool? - REST, SOAP, GWT-RPC, ...	Don't know yet.
What data format shall be used to transfer data from the course converter tool to this landing page tool?
Should the landing page write the final grade file to AFS?
Do we need the Final Grade Submission tool to change also?
What happens if the end user hits the back button while inputting grades? -- Could this be used as "undo"
At waht what time is user input persisted, it at all? -- using AJAX after each field edit -- once by clicking on "save/submit" button
What software development tools will be used for programming the landing page tool?