Attempt to track current and past work to make the Testing Center more robust.

Table of Contents

Next steps

2017-02-10

Nick Taylor (Testing Lab) to dos:

Tech-related work (in priority order)

  1. Determine how daily file-copies are being done from TC2 to TC3. In that case FMPro file copied. Determine how to replicate so copies also going to TC1. And copies from TC1 to TC2 and TC3.
  2. Determine how EZData functions, including dependent helper files, so that it could be reconstructed if on new OS with new version of FM Pro.
  3. Determine how FMPro scripts work so system could be reconstructed or migrated to new version of FM Pro.

Procedures and such

  1. Establish clear procedures for staff to follow if a particular computer or printer is not working.
    1. How much to attempt to fix (answer: very little!). Who to contact (anser: <PhysIT@cornell.edu>). How to do things "by hand", and what to do after system is back up and running.
  2. Question Nick was going to discuss with Alan: Is it worth have a weekly "snapshot" on a USB drive in Alan's office, which would be more "off site"? Worth the added risk?

Status reports

2017-03-09

Imaged systems now contained within an encrypted file, placed on a thumb drive, to give to Craig for safe-keeping.

Was: 2/10/17: Image all three systems in case of hard drive failure. Might protect against other likelihoods, too.

2017-03-01

Request from Craig for recommended action.

2017-02-23

Discovered that Brightworks is not available to do this work. (Was: 2/15/17, Oliver contacted Brightworks to see if they might be engaged with this work: Ticket#95300/Physics Testing Center, ensuring robustness in its setup.)

2017-02-10

Oliver and Nick Taylor <nwt2> created to-do lists following failing TC1 this week. Either in "Next steps" or "Status reports" (both, above), depending on completion level.

Past "Next steps"

8/27/15

Historical info:

Prior defined "next step", from spring 2015: