Support and maintenance expectations (DRAFT)

For Chemistry Instructional and IT staff

Useful to distinguish between something breaking (worked yesterday!) and something new needed (consultation/ design/ implementation).

For now, keep communications flowing directly between PatH, Dani, and Tu.
- De-bugging, tweaking, etc.
After project is "completed" (~mid-Sept?), all All requests (for breakage or new feature requests) are to go to ChemIT, from Instructional staff.
- In an emergency (time-sensitive situation), in addition to contacting ChemIT, PatH may contact Dani or Tu.

...

Debugging a problem is easier if changes to the source DB is known up-front.
There are many, many moving parts to this complex and interdependent system!
- An example: Uploads may not work correctly or otherwise need to be tested if structural changes are made.
Backups and restores may not work correctly if structural changes are made.

A&S is providing provides the FMPro server hosting services.
- This includes performing and confirming back-ups and restore procedures, especially .
- Special focus is on addressing an any infrastructure problem at their end.
A&S staff can do Design/ Creation work on a case-by-case basis
- This will usually require Frank's approval, with negotiated timelines.

Who do If students contact if they have questions or concerns about the web site?, they are to contact Chemistry Instructional staff.

Chemistry's web page

http://chemistry.cornell.edu/courses/grade-faq.cfm
- https://chemlabs.arts.cornell.edu/grades/
What is done now for the Waiting List web application? Do same thing?
Would it not be PatH's office? If so, how communicate on the page?

...