From - Sat Jan 25 16:56:53 2003
X-UIDL: 3e32cf290000000b
X-Mozilla-Status: 0013
X-Mozilla-Status2: 00000000
Received: from jay.mail.ku.edu (jay.mail.ku.edu [129.237.35.95])
	by ns.cria.org.br (8.11.2/8.11.2) with ESMTP id h0OJgTi25935
	for <ricardo@cria.org.br>; Fri, 24 Jan 2003 17:42:29 -0200
Received: by jay.mail.ku.edu with Internet Mail Service (5.5.2653.19)
	id <ZJTLAMWV>; Fri, 24 Jan 2003 14:42:27 -0600
Message-ID: <F73B91BED37FD5119F970008C7CF50FC0EE2D511@skylark.mail.ukans.edu>
From: "Stewart, Aimee Marian" <astewart@ku.edu>
To: "'Ricardo Scachetti Pereira'" <ricardo@cria.org.br>,
   "Beach, James H"
	 <beach@ku.edu>,
   "Vorontsov, Gregory Yakovlevich" <voron999@ku.edu>,
   "Stewart, Aimee Marian" <astewart@ku.edu>,
   "Downie, Scott Russell"
	 <sdownie@ku.edu>, reed.beaman@yale.edu
Subject: RE: Value added products to collection as webservices
Date: Fri, 24 Jan 2003 14:42:19 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2C3E9.166B4400"
X-MailScanner: Found to be clean
Status: RO

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_01C2C3E9.166B4400
Content-Type: text/plain;
	charset="iso-8859-1"

Hi Ricardo,
 
Great suggestions!  I think that this is an excellent way to increase our
value to data providers.   I will think about some more services that can be
implemented.  
 
By the way, 2 services are available at
http:\\beta.lifemapper.org\Services\QueryByLocation and
http:\\beta.lifemapper.org\Services\QueryTaxa .  Number 6 on your
spreadsheet could be easily be put together from methods in these services.

 
Number 7 would be easy once we gather layers for areas outside the US.  I
will get to that once we have successfully moved to production. 
 
We can create the initial services, then create some applications using the
services to implement commiting the new data back to provider databases
(interactively, one record at a time or groups at a time for normalization,
in Specify perhaps).  To get some interest quickly, I think we need to allow
providers a way to improve their own data without on-site programmers.  
 
Report cards could include geostatistical analysis of entire collections,
genus, species, subspecies.  I've been wanting to explore that ESRI
extension!
 
Perhaps a short questionaire for existing contributors could determine
whether there is any interest in these services, or if they have some ideas
we haven't yet come up with.  The initial Fishnet (Ed) reaction was very
positive!
 
Aimee
 
 

 -----Original Message-----
From: Ricardo Scachetti Pereira [mailto:ricardo@cria.org.br]
Sent: Friday, January 24, 2003 11:47 AM
To: Beach, James H; voron999@UKANS.EDU; Stewart, Aimee Marian; Downie, Scott
Russell; reed.beaman@yale.edu
Subject: Value added products to collection as webservices



    Hey, guys.
    How have you been?

    Let me bring something up, so we can discuss it and think about it a
little, if you want.
    I've been thinking about value added products to collections and came up
with some ideas.
    Among the categories of value added products, I could list those: 
    1) Error checking and correction tools, such as: normalization of field
values, checking for invalid characters, checking compliance of date or
coordinate formats, checking mispellings and typos, cross-reference of
textual location descriptions (country, state, county, etc) with
georeferences, etc; Reed's georeferencing tool could be put in this
category, if you consider that putting a georeference in a record that does
not contain one means correcting it, i.e., filling in the blanks on
georeference field.
    2) Visualization tools: Showing data on maps (like GIS tools and WMS
services);
    3) Statistics and other analysis tools: Measuring clustering of points,
correlation between data points and infrastructure, sampling densities, etc.
    As far as I know, the tools in category #3 don't lend themselves well to
a webservice implementation. They could be implemented as services, but they
are not very important to stand up for themselves.
    Tools in #2 are currently being well covered by Aimee's WMS.
    So I tried to think about possible #1 tools that would become good
webservices. The result of that is summarized in the Excel spreadsheet
attached.
    I'm still not pretty sure what would be the best architecture to
implement them.
    A possibility would be implement each of them as one object, or methods
within an object. 
    Each object would have a SOAP and/or XML/HTTP wrapper so they become
webservices.
    This way, local server components can use the objects directly. Remote
components and other users can call the services programmatically using the
webservices. Some can be implemented in Kansas, other at CRIA, or we could
have copies in both places. Pretty flexible.
    Last but not least, there are the report cards to the collections, that
could use some of those services and some other statistics from Lifemapper.
    Questions:
    1) What do you think of the general idea and the proposed architecture?
    2) What do you think of the services listed? Can you add some more to
the list?
    3) Do you guys have more ideas for the report cards? What should be in
there?
    4) Market analysis: would any one out there (collections community) in
need to use such services?

    That is about it.
    Cheers,

Ricardo



Attached is a set of 10 possible value added products that

-- 

Ricardo Scachetti Pereira

Gerente de Pesquisa

Centro de Referência em Informação Ambiental - CRIA

http://www.cria.org.br/ <http://www.cria.org.br/> 

-- 
This message has been scanned for viruses and 
dangerous content and is believed to be clean. 


--
This message has been scanned for viruses and
dangerous content and is believed to be clean.


------_=_NextPart_001_01C2C3E9.166B4400
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE></TITLE>

<META content="MSHTML 6.00.2800.1126" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2>Hi Ricardo,</FONT></SPAN></DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2>Great suggestions!&nbsp; I think that this is an excellent way to 
increase our value to data providers.&nbsp;&nbsp; I will think about some more 
services that can be implemented.&nbsp;&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2>By the way, 2 services are available 
at&nbsp;http:\\beta.lifemapper.org\Services\QueryByLocation 
and&nbsp;&nbsp;http:\\beta.lifemapper.org\Services\QueryTaxa .&nbsp; Number 6 on 
your spreadsheet could be easily be put together from methods in these 
services.&nbsp; </FONT></SPAN></DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2>Number 7 would be easy once we gather layers for areas outside the 
US.&nbsp; I will get to that once we have successfully moved to production. 
</FONT></SPAN></DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2>We can create the initial services, then create some applications using 
the services to implement commiting the new data back to provider databases 
(interactively, one record at a time or groups at a time for normalization, in 
Specify perhaps).&nbsp; To get some interest quickly,&nbsp;I think we need to 
allow providers a way to improve their own data without on-site 
programmers.&nbsp; </FONT></SPAN></DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2></FONT></SPAN><SPAN class=137075719-24012003><FONT 
face="Palatino Linotype" color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2>Report cards could include geostatistical analysis of entire collections, 
genus, species, subspecies.&nbsp; I've been wanting to explore that ESRI 
extension!</FONT></SPAN></DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2>Perhaps a short questionaire for existing contributors could determine 
whether there is any interest in these services, or if they have some ideas we 
haven't yet come up with.&nbsp; The initial Fishnet (Ed) reaction was very 
positive!</FONT></SPAN></DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2>Aimee</FONT></SPAN></DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=137075719-24012003><FONT face="Palatino Linotype" color=#0000ff 
size=2></FONT></SPAN><FONT face=Tahoma><FONT face="Palatino Linotype" 
color=#0000ff size=2></FONT><FONT face="Palatino Linotype" color=#0000ff 
size=2></FONT><FONT face="Palatino Linotype" color=#0000ff 
size=2></FONT>&nbsp;</DIV>
<DIV><FONT face="Palatino Linotype" color=#0000ff size=2></FONT><BR><FONT 
size=2><SPAN class=137075719-24012003>&nbsp;</SPAN>-----Original 
Message-----<BR><B>From:</B> Ricardo Scachetti Pereira 
[mailto:ricardo@cria.org.br]<BR><B>Sent:</B> Friday, January 24, 2003 11:47 
AM<BR><B>To:</B> Beach, James H; voron999@UKANS.EDU; Stewart, Aimee Marian; 
Downie, Scott Russell; reed.beaman@yale.edu<BR><B>Subject:</B> Value added 
products to collection as webservices<BR><BR></DIV></FONT></FONT>
<BLOCKQUOTE>&nbsp;&nbsp;&nbsp; Hey, guys.<BR>&nbsp;&nbsp;&nbsp; How have you 
  been?<BR><BR>&nbsp;&nbsp;&nbsp; Let me bring something up, so we can discuss 
  it and think about it a little, if you want.<BR>&nbsp;&nbsp;&nbsp; I've been 
  thinking about value added products to collections and came up with some 
  ideas.<BR>&nbsp;&nbsp;&nbsp; Among the categories of value added products, I 
  could list those: <BR>&nbsp;&nbsp;&nbsp; 1) <B>Error checking and correction 
  tools</B>, such as: normalization of field values, checking for invalid 
  characters, checking compliance of date or coordinate formats, checking 
  mispellings and typos, cross-reference of textual location descriptions 
  (country, state, county, etc) with georeferences, etc; Reed's georeferencing 
  tool could be put in this category, if you consider that putting a 
  georeference in a record that does not contain one means correcting it, i.e., 
  filling in the blanks on georeference field.<BR>&nbsp;&nbsp;&nbsp; 2) 
  <B>Visualization tools</B>: Showing data on maps (like GIS tools and WMS 
  services);<BR>&nbsp;&nbsp;&nbsp; 3) <B>Statistics and other analysis 
  tools</B>: Measuring clustering of points, correlation between data points and 
  infrastructure, sampling densities, etc.<BR>&nbsp;&nbsp;&nbsp; As far as I 
  know, the tools in category #3 don't lend themselves well to a webservice 
  implementation. They could be implemented as services, but they are not very 
  important to stand up for themselves.<BR>&nbsp;&nbsp;&nbsp; Tools in #2 are 
  currently being well covered by Aimee's WMS.<BR>&nbsp;&nbsp;&nbsp; So I tried 
  to think about possible #1 tools that would become good webservices. The 
  result of that is summarized in the Excel spreadsheet 
  attached.<BR>&nbsp;&nbsp;&nbsp; I'm still not pretty sure what would be the 
  best architecture to implement them.<BR>&nbsp;&nbsp;&nbsp; A possibility would 
  be implement each of them as one object, or methods within an object. 
  <BR>&nbsp;&nbsp;&nbsp; Each object would have a SOAP and/or XML/HTTP wrapper 
  so they become webservices.<BR>&nbsp;&nbsp;&nbsp; This way, local server 
  components can use the objects directly. Remote components and other users can 
  call the services programmatically using the webservices. Some can be 
  implemented in Kansas, other at CRIA, or we could have copies in both places. 
  Pretty flexible.<BR>&nbsp;&nbsp;&nbsp; Last but not least, there are the 
  report cards to the collections, that could use some of those services and 
  some other statistics from Lifemapper.<BR>&nbsp;&nbsp;&nbsp; 
  Questions:<BR>&nbsp;&nbsp;&nbsp; 1) What do you think of the general idea and 
  the proposed architecture?<BR>&nbsp;&nbsp;&nbsp; 2) What do you think of the 
  services listed? Can you add some more to the list?<BR>&nbsp;&nbsp;&nbsp; 3) 
  Do you guys have more ideas for the report cards? What should be in 
  there?<BR>&nbsp;&nbsp;&nbsp; 4) Market analysis: would any one out there 
  (collections community) in need to use such 
  services?<BR><BR>&nbsp;&nbsp;&nbsp; That is about it.<BR>&nbsp;&nbsp;&nbsp; 
  Cheers,<BR><BR>Ricardo<BR><BR><BR><BR>Attached is a set of 10 possible value 
  added products that<BR><PRE class=moz-signature cols="$mailwrapcol">-- 
Ricardo Scachetti Pereira
Gerente de Pesquisa
Centro de Referência em Informação Ambiental - CRIA
<A class=moz-txt-link-freetext href="http://www.cria.org.br/">http://www.cria.org.br/</A>
</PRE><BR>-- <BR>This message has been scanned for viruses and <BR>dangerous 
  content and is believed to be clean. </BLOCKQUOTE></BODY><BR>--
<BR>This message has been scanned for viruses and
<BR>dangerous content and is believed to be clean.
</HTML>

------_=_NextPart_001_01C2C3E9.166B4400--