From MAILER-DAEMON Sat Jul 25 10:09:18 2009
Date: 25 Jul 2009 10:09:18 -0400
From: Mail System Internal Data <MAILER-DAEMON@turing.acm.org>
Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
X-IMAP: 1248530958 0000000000
Status: RO

This text is part of the internal format of your mail folder, and is not
a real message.  It is created automatically by the mail system software.
If deleted, important folder data will be lost, and it will be re-created
with the data reset to initial values.

From normore@utk.edu  Fri Jul 24 18:02:18 2009
Return-Path: <normore@utk.edu>
Received: from mufasa.mail.utk.edu (mufasa.mail.utk.edu [160.36.178.84])
	by turing.acm.org (8.13.1/8.13.1) with ESMTP id n6OM2GKg019235
	for <perlman@turing.acm.org>; Fri, 24 Jul 2009 18:02:17 -0400
Received: from ksmtp2.utk.tennessee.edu (ksmtp2.utk.tennessee.edu [160.36.76.165])
	by mufasa.mail.utk.edu (8.14.1/8.14.1) with ESMTP id n6OM2Fh8006086
	for <perlman@turing.acm.org>; Fri, 24 Jul 2009 18:02:15 -0400
Received: from KFSVS2.utk.tennessee.edu ([160.36.76.173]) by ksmtp2.utk.tennessee.edu with Microsoft SMTPSVC(6.0.3790.3959);
	 Fri, 24 Jul 2009 18:02:15 -0400
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01CA0CAA.670DE89E"
Subject: RE: HFES in HCIBIB
Date: Fri, 24 Jul 2009 17:58:44 -0400
Message-ID: <0913EC48F2B05C4FBE4878BAFCABBFEC03F53801@KFSVS2.utk.tennessee.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: HFES in HCIBIB
Thread-Index: AcoMFYh6GTgj4hucSSuVdKx45sVMIgAlGEuH
References: <Pine.LNX.4.64.0907240011200.636@turing.acm.org>
From: "Normore, Lorraine" <normore@utk.edu>
To: "Gary PERLMAN" <perlman@turing.acm.org>
X-OriginalArrivalTime: 24 Jul 2009 22:02:15.0026 (UTC) FILETIME=[67488520:01CA0CAA]
X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166 definitions=2009-07-24_08:2009-07-24,2009-07-24,2009-07-24 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0811170000 definitions=main-0907240165
Status: R
X-Status: 
X-Keywords:                  

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA0CAA.670DE89E
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks for the chance to give some input here.  It's true that CSTG and =
the Internet group are no brainers but, as you say there are often other =
TGs with relevant stuff and it's pretty unpredictable just which TGs are =
going to be relevant.  If you don't think it would do harm to HCIBIB, =
I'd say to include the whole thing.=20
=20
My 2 cents.
=20
Hope things are going well for you.
=20
Lorraine=20

________________________________

From: Gary PERLMAN [mailto:perlman@turing.acm.org]
Sent: Fri 7/24/2009 12:16 AM
To: Normore, Lorraine
Cc: director@hcibib.org
Subject: HFES in HCIBIB



Hi Lorraine,

I've just determined that it now takes about 15 minutes to ingest an =
annual
meeting proceedings from the HFES DL into the HCIBIB. So I am getting =
ready
to pick up the backlog to 1995 or 1996. I can import the entire =
proceedings,
or with slightly less work, select the TGs to represent in the HCIBIB.

Some TGs are no-brainers, like CG and Internet. Then SD and T&E are =
often
relevant. And then there are potpourri sessions and student sessions.
I could toss abstracts, but I wonder if the noise from even the "Tote =
that
Bail" sessions would be a problem for the HCIBIB.

Seeing as you have contributed the most the get the HFES records into =
the
HCIBIB, I wanted to get your input about what you would like to see in =
there.

Gary



------_=_NextPart_001_01CA0CAA.670DE89E
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>HFES in HCIBIB</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText15658 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Thanks for =
the chance to give&nbsp;some input here.&nbsp; It's true that CSTG and =
the Internet group are no brainers but, as you say there are often other =
TGs with relevant stuff and it's pretty unpredictable just which TGs are =
going to be relevant.&nbsp; If you don't think it would do harm to =
HCIBIB, I'd say to include the whole thing.&nbsp;</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>My 2 cents.</FONT></DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Hope things are going well =
for you.</FONT></DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial =
size=3D2>Lorraine</FONT>&nbsp;</DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Gary PERLMAN =
[mailto:perlman@turing.acm.org]<BR><B>Sent:</B> Fri 7/24/2009 12:16 =
AM<BR><B>To:</B> Normore, Lorraine<BR><B>Cc:</B> =
director@hcibib.org<BR><B>Subject:</B> HFES in =
HCIBIB<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Hi Lorraine,<BR><BR>I've just determined that it now =
takes about 15 minutes to ingest an annual<BR>meeting proceedings from =
the HFES DL into the HCIBIB. So I am getting ready<BR>to pick up the =
backlog to 1995 or 1996. I can import the entire proceedings,<BR>or with =
slightly less work, select the TGs to represent in the =
HCIBIB.<BR><BR>Some TGs are no-brainers, like CG and Internet. Then SD =
and T&amp;E are often<BR>relevant. And then there are potpourri sessions =
and student sessions.<BR>I could toss abstracts, but I wonder if the =
noise from even the "Tote that<BR>Bail" sessions would be a problem for =
the HCIBIB.<BR><BR>Seeing as you have contributed the most the get the =
HFES records into the<BR>HCIBIB, I wanted to get your input about what =
you would like to see in =
there.<BR><BR>Gary<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01CA0CAA.670DE89E--

