Replied: Sun, 19 May 2002 12:08:16 -0500 Replied: "Marlon Pierce" Return-Path: marpierc@indiana.edu Delivery-Date: Sun May 19 11:40:48 2002 Return-Path: Received: from plounts.uits.indiana.edu (plounts.uits.indiana.edu [129.79.1.73]) by grids.ucs.indiana.edu (8.10.2+Sun/8.10.2) with ESMTP id g4JGemu02274 for ; Sun, 19 May 2002 11:40:48 -0500 (EST) Received: from stjoseph.uits.indiana.edu (stjoseph.uits.indiana.edu [129.79.1.78]) by plounts.uits.indiana.edu (8.12.1/8.12.1/IUPO) with ESMTP id g4JGfLct019020 for ; Sun, 19 May 2002 11:41:22 -0500 (EST) Received: from fordyce (fordyce.ucs.indiana.edu [156.56.104.30]) by stjoseph.uits.indiana.edu (8.12.1/8.12.1/IUPO) with ESMTP id g4JGfE6K023984 for ; Sun, 19 May 2002 11:41:22 -0500 (EST) From: "Marlon Pierce" To: "'Geoffrey Fox'" Subject: Content request letter Date: Sun, 19 May 2002 11:39:09 -0500 Message-ID: <000101c1ff53$b614f600$1e68389c@fordyce> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0002_01C1FF29.CD3EEE00" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Content-Length: 11267 This is a multi-part message in MIME format. ------=_NextPart_000_0002_01C1FF29.CD3EEE00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit (Geoffrey-Wayne requests we also send to CPOCs so they can follow up with the FAs. I have all of these emails.) To Functional Area Leads-- We would like to request your help compiling functional area content for the Online Knowledge Center. We thank the CCM, CDLT, CE, CEA, CEN, and SIP teams for their PET2 contributions, which are available from the OKC web sites below. If you have not yet sent content for you functional area, please use the following guidelines: A. FORMAT: Any web content is acceptable. We only request that you do not use HTML frames and framesets. The OKC will provide these organizational features. See the "Guidelines" section at the IU OKC web site if you would like more extensive guidelines on some advanced topics such as how the OKC handles stylesheets and targets. B. CONTENT: The following are some minimum content guidelines for your site: 1. Short functional area description (a mission statement); 2. Contact information for members of your FA PET team (emails, phone numbers) ; 3. The name of the government CTA lead; 4. FA core activities, funded projects, roadmap of future activity; 5. Useful links: for example, software to download, documentation, upcoming meetings. You are of course welcome to provide more information than the above. C. DELIVERY: Contact Lesa Nelson ( Lesa.M.Nelson@erdc.usace.army.mi, Ph: 601-634-4070) to upload your files. If the zipped files are less the 5MB, you can email them. Otherwise, please contact Lesa to get access to our FTP site. D. PUBLICATION: We will put your material up on a staging server, (https://134.164.184.121:443/okc/index.jsp , and let you review it. The CPOC for your component will be responsible for checking the material for public release. After this has been done, we will move your content to the public server. The operational OKC will be available from ERDC soon. The prototype OKC is available at http://judi.ucs.indiana.edu/okcportal. ------=_NextPart_000_0002_01C1FF29.CD3EEE00 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable RE:

(Geoffrey—Wayne requests we also send to CPOCs so they can follow up with the FAs.  I have all of these = emails.)

To Functional Area = Leads--

We would like to request your help compiling functional area content for the = Online Knowledge = Center.   = We thank the CCM, CDLT, CE, CEA, CEN, and SIP teams for their PET2 = contributions, which are available from the OKC web sites below.  If you have not yet sent = content for you functional area, please use the following guidelines:

A. FORMAT: Any web content is acceptable.  We only request = that you do not use HTML frames and framesets.  The OKC will provide these organizational features.  See the "Guidelines" section at = the IU OKC web site if you would like more extensive guidelines on some = advanced topics such as how the OKC handles stylesheets and targets. =

B. CONTENT:  The following are some = minimum content guidelines for your site:
        1. Short functional area = description (a mission statement);
        2. Contact information for = members of your FA PET team (emails, phone numbers) ;
        3. The name of the government = CTA lead;
        4. FA core activities, funded projects, roadmap = of future activity; =
        5. Useful links: for example, = software to download, documentation, upcoming meetings.
You are of course welcome to provide more information than the above. =

C. DELIVERY: Contact Lesa Nelson (Lesa.M.Nelson@erdc.usace.army.mi= , Ph: 601-634-4070) to = upload your files. If the zipped files are less the 5MB, you can email = them.  Otherwise, please contact Lesa to get access to our FTP = site.

D. PUBLICATION:  We will put your = material up on a staging server, (https://134.164.184.121:44= 3/okc/index.jsp, and let you = review it.  The CPOC for = your component will be responsible for checking the material for public release.  = After this has been done, we will move your content to the public server. =   The = operational OKC will be available from ERDC soon.  The prototype OKC is available at http://judi.ucs.indiana.ed= u/okcportal.

 

 

------=_NextPart_000_0002_01C1FF29.CD3EEE00--