Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Any benefit in changing the current "export" process?

To do's for this project

See the following section for context related to these to-do's.

...

  • Do ~end of Sept? (No later, please!)
  • To be done by PatH. Presumably via self-service. :-)

Enable PatH's remote access

  • ChemIT must do this. Oliver must do or assign.

Enable ChemIT staff's access to CCB FMPro DBs.

  • Do via AD group. Enable only "Admin" accounts, not ChemIT staff's user accounts. (Right, Roger?)
  • Tu to work with Roger.

Ensure FMPro access by TAs and a few staff

  • Ensure that all "single account set up for a whole course for use by many TAs" is cleaned up. (Legacy capability which is no longer needed. And confuses things now.)
    • Dani and PatH
  • Ensure works from systems: TA room, DanL, CynthiaK, and Sam's.
    • ChemIT staff:MichaelH.
  • Create appropriate "read-only" account for Becky to allow her to continue doing exports herself.
    • Dani and PatH Roger (working with Becky)
    • Outline some options, for later focus. (Unlikely do any other changes right now!)

...

Clarify support and maintenance expectations

...

  • Hosting vs. Design/ Creation vs. Support

...

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 requests (for breakage or new feature requests) are to go to ChemIT
    • In an emergency (time-sensitive situation), in addition to contacting ChemIT, PatH may contact Dani or Tu.

Instructional staff are encouraged to involve A&S support staff if making structural changes to their DBs. And if Instruction staff make structural changes to any of their DBs, at the very least inform A&S staff as an FYI.

  • 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!
A&S's role
  • A&S is providing the FMPro server hosting services.
    • This includes performing and confirming back-ups and restore procedures, especially focus on addressing an infrastructure problem at their end.
  • A&S staff can Design/ Creation on a case-by-case basis
    • This will usually require Frank's approval.

Map out transition steps remaining

...