Replied: Mon, 07 Jan 2002 11:52:56 -0500 Replied: "Nelson, Replied: Lesa M ERDC-ITL-MS Contractor" Return-Path: Lesa.M.Nelson@erdc.usace.army.mil Delivery-Date: Mon Jan 7 11:49:40 2002 Return-Path: Received: from snorkel.uits.indiana.edu (snorkel.uits.indiana.edu [129.79.6.186]) by grids.ucs.indiana.edu (8.10.2+Sun/8.10.2) with ESMTP id g07Gne628499 for ; Mon, 7 Jan 2002 11:49:40 -0500 (EST) Received: from WESMAIL03.wes.army.mil (eie03a.wes.army.mil [134.164.38.19]) by snorkel.uits.indiana.edu (8.10.1/8.10.1/IUPO) with ESMTP id g07Gndh11645 for ; Mon, 7 Jan 2002 11:49:39 -0500 (EST) Received: by wesmail03.wes.army.mil with Internet Mail Service (5.5.2650.21) id ; Mon, 7 Jan 2002 10:49:36 -0600 Message-ID: From: "Nelson, Lesa M ERDC-ITL-MS Contractor" To: "'Colbert Mason M Contr ASC/HP'" , "Andrew Schatzle (E-mail)" , "Randy Schauer (E-mail)" Cc: "'gcf@indiana.edu'" Subject: RE: PET OKC updates Date: Mon, 7 Jan 2002 10:49:30 -0600 Return-Receipt-To: "Nelson, Lesa M ERDC-ITL-MS Contractor" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1979B.49633CD0" Content-Length: 3222 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1979B.49633CD0 Content-Type: text/plain; charset="iso-8859-1" I guess I didn't explain things very well since I've gotten several questions about the OKC updates, sorry about that. Here's what the plan is for updating information that is wrong. For example, our contact information is out of date, the leads have changed, the training coordinator has changed, and the email addresses are incorrect. All we plan to do for the first release of the OKC is to change the information on the page contacts.htm. The tar file I plan to send to Geoffrey will just contain the updated file /pet/contacts/contacts.htm. The reason for maintaining the structure is so that the folks working for Geoffrey will know where to put the file in the OKC structure. Don't plan on doing major revisions to the PET1 site. Anything major can wait and be incorporated into the OKC. Geoffrey will set up a procedure for major changes/new pages after the OKC is up and running. I hope this clears things up, if not let me know and I'll try to get things straight! Thanks, Lesa Lesa Nelson PET Technologist ERDC MSRC Computer Sciences Corporation (601)634-4070 ------_=_NextPart_001_01C1979B.49633CD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: PET OKC updates

I guess I didn't explain things very well since I've = gotten several questions about the OKC updates, sorry about that.  = Here's what the plan is for updating information that is = wrong.   For example, our contact information is out of date, = the leads have changed, the training coordinator has changed, and the = email addresses are incorrect.  All we plan to do for the first = release of the OKC is to change the information on the page = contacts.htm.  The tar file I plan to send to Geoffrey will just = contain the updated file /pet/contacts/contacts.htm.  The reason = for maintaining the structure is so that the folks working for Geoffrey = will know where to put the file in the OKC structure. 

Don't plan on doing major revisions to the PET1 = site.  Anything major can wait and be incorporated into the = OKC.  Geoffrey will set up a procedure for major changes/new pages = after the OKC is up and running.

I hope this clears things up, if not let me know and = I'll try to get things straight!

Thanks,
Lesa

Lesa Nelson
PET Technologist
ERDC MSRC
Computer Sciences Corporation
(601)634-4070

------_=_NextPart_001_01C1979B.49633CD0--