You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Making CCB's very important ChemGrades DB more robust, and enabling necessary increased functionality, especially for teaching faculty and students. Ensuring its long-term support and operation. Representing customer is Pat Hine's (PatH).

Links

When completed, here's the URL for the read-only web access:

Eval from 8/13/13:

To do's and questions

Establish procedure for PatH to update web-hosted data. "Push the button".

As of 8/16/13, function doesn't exist for PatH.

  • Requires ODBC connection. Not possible at FMPro server; must be set up at FMPro client's computer.
    • Do for PatH's computer. As backup, do on Sam's computer.
    • Current plan: For each computer, set ODBC up as system's Admin (vs. user) so ODBC accessible/ configured for any computer account.
    • Tu will work with Roger.
      • Tu needs IP addresses. Roger can do the installs. And he may have better alternatives. :-)

Establish semester-start procedures and processes. Includes:

  • Initially populating the DB with PeopleSoft data via a PeopleSoft import.
    • Question: Can a vetted clone of a DB on Pat's desktop be used to replace the server production DB?
    • Function tends to be of most value at the beginning of the semester. Other times? (See revert procedure, below).

Notes:

  • This is a one-time import per DB.
  • ChemIT can do the uploads, if not A&S (if at all desired).

Establish semester-end procedures and processes. Includes:

  • Pat pulling the final data
  • The data getting zeroed out in each of the ChemGrades DBs before the start of their next use

Establish DB revert procedure. Initiating request and subsequent restoration from back-up.

  • Likelihood of needing to do this is reduced because Pat and others can run recent clone of production DB (from backup) and test on own desktop first.

Ensure Pat's "low friction" access to the backup files.

  • Do in a way to minimize need for mediation by others. Pat may need access during a weekend or after-hours, for example.
  • Confirm Pat's access.

Enable Pat's view of DB data from home.

  • View only (where web access or clone (backup) would suffice), or are modifications required?
  • Web version OK for view-only of some data, but obviously not as flexible for searching.
  • Idea 1: With FMPro installed on dept. laptop, access AS's FMPro server off-campus (possible?) and do the work that way.
  • Idea 2: Enable Remote Desktop on PatH's main work computer. Access from off-campus via VPN.

Ensure security of FERPA data in Grades DB.

See Michael Hint's emails with Tu and Frank for more on this. Some thoughts, initially:

  • FERPA-like data so ChemIT would appreciate understanding the ACL (see for subnet?) and firewall configurations.
    • ChemIT thinks there shouldn't be any off-campus access except via VPN. Thus take off of public net and put into 10-space. But there may be other factors to consider.
  • Who else has access to Grades DB FMPro DB?
  • Ideal: Make all access via NetID/ NetID p/w, not via FMPro DB's own controls.
    • Control NetID membership via Active Directory groups.
      • Start with Grad TA access, via theTA room kiosks? Also start with faculty access?
      • Once process confirmed, establish procedure for enabling and disabling NetID access to Grades FMPro DB by grads and faculty
        • Can take ChemIT staff less than a minute to do this, and is effective immediately.
  • Confirm FMPro server and admin groups support required staff access rights.
    • Currently it authorized CCB staff to see all PatH sees.
    • Confirm Becky can see what she needs to see.
      • Exports data using PatH's account.
    • Confirm TAs can see/ edit what they need to edit.

Clarify support and maintenance expectations

  • Clarify to what degree A&S staff (Dani and Tu) are available and willing to perform support.
    • Hosting vs. Design/ Creation vs. Support
  • Distinguish between something breaking (worked yesterday!) and new need (consultation/ design/ implementation).

Map out transition steps remaining

  • Change direction of cname, <grades.chem.cornell.edu> from old to new instance.
    • ChemIT needs a date.
    • Doing this means other systems (2 computers in TA room; Becky's computer) automatically cut-over. :-)
  • Shut off access to old ChemIT-run instance (Win7 VM). "Legacy Grades".
    • ChemIT needs a date.
  • When add access via AD groups?
  • No labels