No subject
Tue Mar 22 16:36:09 PST 2005
neither a domain or thesaurus is identified (particlarly literature
catalogs) so unless this is optional, you will discourage people from
converting older data to EML. This is the same issue i tried to raise with
the name fields in party. I cant load a bibliograpy from Endnote into a
valid EML Literature file without first splitting all the author fields into
first middle and last names, and assigning domains to all the keywords.
These steps cannot be 100% automated and will probably hinder adoption of
EML Literature as a bibliography exchange format.
Peter McCartney (peter.mccartney at asu.edu)
Center for Environmental Studies
Arizona State University
480-965-6791
-----Original Message-----
From: Rudolf Nottrott, NCEAS [mailto:nottrott at nceas.ucsb.edu]
Sent: Thursday, February 21, 2002 2:05 PM
To: jones at ulysses.nceas.ucsb.edu
Cc: eml-dev at ecoinformatics.org
Subject: Re: Keyword types in EML
Matt,
If we agree to stick with the present EML keywords
theme, place, stratum and temporal, I can change the Web form script
(load-dataset.cgi) to include a taxonomic keyword (to go into taxonomicCov,
keywtax, taxonkey) an a "none" (to be dropped in the XML file). Is there
anything else we need to consider for the Web form?
For the EML-DEVers who may not recently have looked at the Web forms, they
are at
http://knb.ecoinformatics.org/cgi-bin/load-dataset.cgi?cfg=nrs
and
http://knb.ecoinformatics.org/cgi-bin/load-dataset.cgi?cfg=obfs
Rudolf
At 05:19 PM 2/20/2002 -0800, you wrote:
>Hi Matt, I agree with all of the below. We can safely drop discipline, I
>think it'll be covered by theme. The present NRS keyword list comes from
>the ISO standard (without going back and looking, I believe I just copied
>their types).
>
>Rudolf
>
>At 03:30 PM 2/20/2002 -0900, you wrote:
>Date: Wed, 20 Feb 2002 15:30:52 -0900
>From: Matt Jones <jones at nceas.ucsb.edu>
>To: "Rudolf Nottrott, NCEAS" <RNottrott at UCNRS.org>
>Subject: Re: Keyword types in EML
>
>>Rudolf,
>>
>>There is no reason that the scientists/users need to know about it or be
>>affected by it. They can still enter keywords in the current form. The
>>script will need to be modified so that taxonomic keywords are put in
>>one place (keywtax) and the other valid keywords are put in another
>>(keyword). This is backend encoding into XML, and has nothing to do with
>>a frontend user interface presentation.
>>
>>I think the default of "none" is fine for the pulldown, but the script
>>simply needs to omit the "keywordType" attribute when it is set to none
>>(the keywordType attribute is #IMPLIED, so it is not required and can be
>>safely omitted, but if it is present then it must have one of the values
>>place, stratum, temporal, or theme).
>>
>>The larger issue is what to do with your type "discipline". I think it
>>should be omitted altogther from the list. If there is a compelling
>>reason for EML to be modified to accomodate this type I would like to
>>consider it. Thanks,
>>
>>Matt
>>
>>Rudolf Nottrott, NCEAS wrote:
>>
>>> Matt,
>>>
>>> Sticking with the NBII scheme is fine -- that's the way standards work.
It
>>> is not going to be obvious to NRS users (or OBFS users) and we'll have
some
>>> explaining to do. Taking the present options "theme, place, stratum
and
>>> temporal" as fixed, what do you all suggest we should use for the
default
>>> of the drop-down list? (It's presently the catch-all type "none", which
>>> probably should be called "other" or "miscellaneous", which is a mute
>>> point, however, because it's illegal.)
>>>
>>> Rudolf
>>>
>>> At 02:29 PM 2/20/2002 -0900, you wrote:
>>>
>>>>Rudolf,
>>>>
>>>>I was aware of this problem, but I think that taxonomic keywords should
>>>>go in the field designed for them in the taxonomic coverage module,
>>>>sepcifically "keywtax". This is adopted from NBII. NBII made a new
>>>>keyword field for taxonomic keywords because FGDC would not allow them
>>>>to extend the domain of the keyword field. We followed suit, which will
>>>>make translation to the other standards easier. Sooo, is there a reason
>>>>you can't use the keywtax field for taxonomic keywords?
>>>>
>>>>Matt
>>>>
>>>>Rudolf Nottrott, NCEAS wrote:
>>>>
>>>>
>>>>>Matt, and DEVers,
>>>>>
>>>>>We designed the NRS registry entry form with keyword types of
>>>>>
>>>>>none, theme, taxonomic, discipline, place, stratum and temporal
>>>>>
>>>>>NRS has used the form with types like that so far, and the OBFS form
has
>>>>>the same types.
>>>>>
>>>>>The present EML standard, however, has only
>>>>>
>>>>>theme, place, stratum and temporal
>>>>>
>>>>>I'm ok changing the existing NRS keyword type list, but I do think we
need
>>>>>to keep at least the type taxonomic. This is the most common keyword I
>>>>>have encountered in the first 15 entries we received.
>>>>>
>>>>>What do you think.
>>>>>
>>>>>Rudolf
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Date: Tue, 19 Feb 2002 10:32:25 -0900
>>>>>>From: Matt Jones <jones at nceas.ucsb.edu>
>>>>>>User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.7+)
>>>>>>
>>>>>>
>>>>>Gecko/20020117
>>>>>
>>>>>
>>>>>>To: "Rudolf Nottrott, NCEAS" <RNottrott at UCNRS.org>
>>>>>>Subject: Re: nrsadmin account
>>>>>>
>>>>>>Hi Rudolf,
>>>>>>
>>>>>>Actually, no. The problem is that the keyword types that you have in
>>>>>>the web form are not valid in eml. The only allowed values according
to
>>>>>>EML for the keywordType attribute are "place", "stratum", "temporal",
>>>>>>and "theme". We need to eliminate the others from the web form.
>>>>>>
>>>>>>Matt
>>>>>>
>>>>>>Rudolf Nottrott, NCEAS wrote:
>>>>>>
>>>>>>
>>>>>>>Hi Matt,
>>>>>>>
>>>>>>>To test your changes I have tried a real entry (one that had been
>entered
>>>>>>>previously without problems). I got an error
>>>>>>>
>>>>>>>Processing error. Attribute "keywordType" with value "discipline"
must
>>>>>>>
>>> have
>>>
>>>>>>>a value from the list "(place|stratum|temporal|theme)".
>>>>>>>
>>>>>>>This was apparently caused by the keyword "Invasion Ecology",
entered as
>>>>>>>type "discipline". I suspect that somehow deleted the type
"discipline"
>>>>>>>was dropped in the perl processing (perhaps an array or hash
problem).
>>>>>>>
>>>>>>>Rudolf
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>>>--
>>>>*******************************************************************
>>>>Matt Jones jones at nceas.ucsb.edu
>>>>http://www.nceas.ucsb.edu/ Fax: 425-920-2439 Ph: 907-789-0496
>>>>National Center for Ecological Analysis and Synthesis (NCEAS)
>>>>
>>>>Interested in ecological informatics? http://www.ecoinformatics.org
>>>>*******************************************************************
>>>>
>>>>
>>> _______________________________________________
>>> eml-dev mailing list
>>> eml-dev at ecoinformatics.org
>>> http://www.ecoinformatics.org/mailman/listinfo/eml-dev
>>>
>>
>>
>>--
>>*******************************************************************
>>Matt Jones jones at nceas.ucsb.edu
>>http://www.nceas.ucsb.edu/ Fax: 425-920-2439 Ph: 907-789-0496
>>National Center for Ecological Analysis and Synthesis (NCEAS)
>>
>>Interested in ecological informatics? http://www.ecoinformatics.org
>>*******************************************************************
>>
>
_______________________________________________
eml-dev mailing list
eml-dev at ecoinformatics.org
http://www.ecoinformatics.org/mailman/listinfo/eml-dev
--Boundary_(ID_JwqLIRlKcajMqI4vx9c4uw)
Content-type: text/html; charset="iso-8859-1"
Content-transfer-encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: Keyword types in EML</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Frankly, i dont understand what a taxonomic keyword =
would be other than taxon names themselves - anything else i can think =
of ("raptors"? "anadronous"?) seems to make better =
sense to create a new taxonomy domain and use the keywords location. If =
the keywords are there to help find the dataset, it seems easier to me =
to have all keywords in one place. If we force the creation of a new =
location for keywords to accomodate what someone in the future decides =
is a distinct semantic domain, then we will have to keep rewriting our =
search applications to look in those extra areas in the metadata. I =
dont understand why "stratum" is in the list, but =
"taxonomy" isnt. </FONT></P>
<P><FONT SIZE=3D2>Im wondering what the relative trade offs are between =
a rigid set of domains or types versus allowing some extensibility =
here. I worked with a group about three years ago to define a metadata =
standard for anthropological collections in which we arrived at the =
same keyword structure, but a different set of domains (culture, =
language, theme, place, time, individual - thank god we were PC enough =
to leave out "race"). Looking ahead to scaling our =
metadata schemes accross disciplines, it seems we would be wise to at =
least recognize that our perspective on what is a keyword domain will =
vary, but that we might want to adhere to a common structure. =
</FONT></P>
<P><FONT SIZE=3D2>From a practical point of view, there is a ton of =
legacy data for which neither a domain or thesaurus is identified =
(particlarly literature catalogs) so unless this is optional, you will =
discourage people from converting older data to EML. This is the same =
issue i tried to raise with the name fields in party. I cant load a =
bibliograpy from Endnote into a valid EML Literature file without first =
splitting all the author fields into first middle and last names, and =
assigning domains to all the keywords. These steps cannot be 100% =
automated and will probably hinder adoption of EML Literature as a =
bibliography exchange format. </FONT></P>
<P><FONT SIZE=3D2>Peter McCartney (peter.mccartney at asu.edu)</FONT>
<BR><FONT SIZE=3D2>Center for Environmental Studies</FONT>
<BR><FONT SIZE=3D2>Arizona State University</FONT>
<BR><FONT SIZE=3D2>480-965-6791 </FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Rudolf Nottrott, NCEAS [<A =
HREF=3D"mailto:nottrott at nceas.ucsb.edu">mailto:nottrott at nceas.ucsb.edu</=
A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, February 21, 2002 2:05 PM</FONT>
<BR><FONT SIZE=3D2>To: jones at ulysses.nceas.ucsb.edu</FONT>
<BR><FONT SIZE=3D2>Cc: eml-dev at ecoinformatics.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: Keyword types in EML</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Matt, </FONT>
</P>
<P><FONT SIZE=3D2>If we agree to stick with the present EML keywords =
</FONT>
<BR><FONT SIZE=3D2>theme, place, stratum and temporal, I can change the =
Web form script</FONT>
<BR><FONT SIZE=3D2>(load-dataset.cgi) to include a taxonomic keyword =
(to go into taxonomicCov,</FONT>
<BR><FONT SIZE=3D2>keywtax, taxonkey) an a "none" (to be =
dropped in the XML file). Is there</FONT>
<BR><FONT SIZE=3D2>anything else we need to consider for the Web =
form? </FONT>
</P>
<P><FONT SIZE=3D2>For the EML-DEVers who may not recently have looked =
at the Web forms, they</FONT>
<BR><FONT SIZE=3D2>are at</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://knb.ecoinformatics.org/cgi-bin/load-dataset.cgi?cfg=3Dnrs=
" =
TARGET=3D"_blank">http://knb.ecoinformatics.org/cgi-bin/load-dataset.cgi=
?cfg=3Dnrs</A></FONT>
<BR><FONT SIZE=3D2>and </FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://knb.ecoinformatics.org/cgi-bin/load-dataset.cgi?cfg=3Dobf=
s" =
TARGET=3D"_blank">http://knb.ecoinformatics.org/cgi-bin/load-dataset.cgi=
?cfg=3Dobfs</A></FONT>
</P>
<P><FONT SIZE=3D2>Rudolf</FONT>
</P>
<P><FONT SIZE=3D2>At 05:19 PM 2/20/2002 -0800, you wrote:</FONT>
<BR><FONT SIZE=3D2>>Hi Matt, I agree with all of the below. We =
can safely drop discipline, I</FONT>
<BR><FONT SIZE=3D2>>think it'll be covered by theme. The =
present NRS keyword list comes from</FONT>
<BR><FONT SIZE=3D2>>the ISO standard (without going back and =
looking, I believe I just copied</FONT>
<BR><FONT SIZE=3D2>>their types).</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>Rudolf</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>At 03:30 PM 2/20/2002 -0900, you wrote:</FONT>
<BR><FONT SIZE=3D2>>Date: Wed, 20 Feb 2002 15:30:52 -0900</FONT>
<BR><FONT SIZE=3D2>>From: Matt Jones =
<jones at nceas.ucsb.edu></FONT>
<BR><FONT SIZE=3D2>>To: "Rudolf Nottrott, NCEAS" =
<RNottrott at UCNRS.org></FONT>
<BR><FONT SIZE=3D2>>Subject: Re: Keyword types in EML</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>>Rudolf,</FONT>
<BR><FONT SIZE=3D2>>></FONT>
<BR><FONT SIZE=3D2>>>There is no reason that the scientists/users =
need to know about it or be </FONT>
<BR><FONT SIZE=3D2>>>affected by it. They can still enter =
keywords in the current form. The </FONT>
<BR><FONT SIZE=3D2>>>script will need to be modified so that =
taxonomic keywords are put in </FONT>
<BR><FONT SIZE=3D2>>>one place (keywtax) and the other valid =
keywords are put in another </FONT>
<BR><FONT SIZE=3D2>>>(keyword). This is backend encoding into =
XML, and has nothing to do with </FONT>
<BR><FONT SIZE=3D2>>>a frontend user interface =
presentation.</FONT>
<BR><FONT SIZE=3D2>>></FONT>
<BR><FONT SIZE=3D2>>>I think the default of "none" is =
fine for the pulldown, but the script </FONT>
<BR><FONT SIZE=3D2>>>simply needs to omit the =
"keywordType" attribute when it is set to none </FONT>
<BR><FONT SIZE=3D2>>>(the keywordType attribute is #IMPLIED, so =
it is not required and can be </FONT>
<BR><FONT SIZE=3D2>>>safely omitted, but if it is present then it =
must have one of the values </FONT>
<BR><FONT SIZE=3D2>>>place, stratum, temporal, or =
theme).</FONT>
<BR><FONT SIZE=3D2>>></FONT>
<BR><FONT SIZE=3D2>>>The larger issue is what to do with your =
type "discipline". I think it </FONT>
<BR><FONT SIZE=3D2>>>should be omitted altogther from the =
list. If there is a compelling </FONT>
<BR><FONT SIZE=3D2>>>reason for EML to be modified to accomodate =
this type I would like to </FONT>
<BR><FONT SIZE=3D2>>>consider it. Thanks,</FONT>
<BR><FONT SIZE=3D2>>></FONT>
<BR><FONT SIZE=3D2>>>Matt</FONT>
<BR><FONT SIZE=3D2>>></FONT>
<BR><FONT SIZE=3D2>>>Rudolf Nottrott, NCEAS wrote:</FONT>
<BR><FONT SIZE=3D2>>></FONT>
<BR><FONT SIZE=3D2>>>> Matt, </FONT>
<BR><FONT SIZE=3D2>>>> </FONT>
<BR><FONT SIZE=3D2>>>> Sticking with the NBII scheme is fine =
-- that's the way standards work.</FONT>
<BR><FONT SIZE=3D2> It</FONT>
<BR><FONT SIZE=3D2>>>> is not going to be obvious to NRS users =
(or OBFS users) and we'll have</FONT>
<BR><FONT SIZE=3D2>some</FONT>
<BR><FONT SIZE=3D2>>>> explaining to do. Taking =
the present options "theme, place, stratum and</FONT>
<BR><FONT SIZE=3D2>>>> temporal" as fixed, what do you =
all suggest we should use for the default</FONT>
<BR><FONT SIZE=3D2>>>> of the drop-down list? (It's =
presently the catch-all type "none", which</FONT>
<BR><FONT SIZE=3D2>>>> probably should be called =
"other" or "miscellaneous", which is a =
mute</FONT>
<BR><FONT SIZE=3D2>>>> point, however, because it's =
illegal.)</FONT>
<BR><FONT SIZE=3D2>>>> </FONT>
<BR><FONT SIZE=3D2>>>> Rudolf</FONT>
<BR><FONT SIZE=3D2>>>> </FONT>
<BR><FONT SIZE=3D2>>>> At 02:29 PM 2/20/2002 -0900, you =
wrote:</FONT>
<BR><FONT SIZE=3D2>>>> </FONT>
<BR><FONT SIZE=3D2>>>>>Rudolf,</FONT>
<BR><FONT SIZE=3D2>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>I was aware of this problem, but I =
think that taxonomic keywords should </FONT>
<BR><FONT SIZE=3D2>>>>>go in the field designed for them in =
the taxonomic coverage module, </FONT>
<BR><FONT SIZE=3D2>>>>>sepcifically =
"keywtax". This is adopted from NBII. NBII made a new =
</FONT>
<BR><FONT SIZE=3D2>>>>>keyword field for taxonomic keywords =
because FGDC would not allow them </FONT>
<BR><FONT SIZE=3D2>>>>>to extend the domain of the keyword =
field. We followed suit, which will </FONT>
<BR><FONT SIZE=3D2>>>>>make translation to the other =
standards easier. Sooo, is there a reason </FONT>
<BR><FONT SIZE=3D2>>>>>you can't use the keywtax field for =
taxonomic keywords?</FONT>
<BR><FONT SIZE=3D2>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>Matt</FONT>
<BR><FONT SIZE=3D2>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>Rudolf Nottrott, NCEAS wrote:</FONT>
<BR><FONT SIZE=3D2>>>>></FONT>
<BR><FONT SIZE=3D2>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>Matt, and DEVers, </FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>We designed the NRS registry =
entry form with keyword types of </FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>none, theme, taxonomic, =
discipline, place, stratum and temporal</FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>NRS has used the form with types =
like that so far, and the OBFS form has</FONT>
<BR><FONT SIZE=3D2>>>>>>the same types.</FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>The present EML standard, =
however, has only </FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>theme, place, stratum and =
temporal</FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>I'm ok changing the existing NRS =
keyword type list, but I do think we</FONT>
<BR><FONT SIZE=3D2>need</FONT>
<BR><FONT SIZE=3D2>>>>>>to keep at least the type =
taxonomic. This is the most common keyword I</FONT>
<BR><FONT SIZE=3D2>>>>>>have encountered in the first 15 =
entries we received.</FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>What do you think.</FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>Rudolf</FONT>
<BR><FONT SIZE=3D2>>>>>> </FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>Date: Tue, 19 Feb 2002 =
10:32:25 -0900</FONT>
<BR><FONT SIZE=3D2>>>>>>>From: Matt Jones =
<jones at nceas.ucsb.edu></FONT>
<BR><FONT SIZE=3D2>>>>>>>User-Agent: Mozilla/5.0 =
(Windows; U; Windows NT 5.0; en-US; rv:0.9.7+)</FONT>
<BR><FONT SIZE=3D2>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>Gecko/20020117</FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>To: "Rudolf Nottrott, =
NCEAS" <RNottrott at UCNRS.org></FONT>
<BR><FONT SIZE=3D2>>>>>>>Subject: Re: nrsadmin =
account</FONT>
<BR><FONT SIZE=3D2>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>Hi Rudolf,</FONT>
<BR><FONT SIZE=3D2>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>Actually, no. The =
problem is that the keyword types that you have in </FONT>
<BR><FONT SIZE=3D2>>>>>>>the web form are not valid =
in eml. The only allowed values according</FONT>
<BR><FONT SIZE=3D2>to </FONT>
<BR><FONT SIZE=3D2>>>>>>>EML for the keywordType =
attribute are "place", "stratum", =
"temporal", </FONT>
<BR><FONT SIZE=3D2>>>>>>>and "theme". =
We need to eliminate the others from the web form.</FONT>
<BR><FONT SIZE=3D2>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>Matt</FONT>
<BR><FONT SIZE=3D2>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>Rudolf Nottrott, NCEAS =
wrote:</FONT>
<BR><FONT SIZE=3D2>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>>Hi Matt, </FONT>
<BR><FONT SIZE=3D2>>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>>To test your changes I =
have tried a real entry (one that had been</FONT>
<BR><FONT SIZE=3D2>>entered</FONT>
<BR><FONT SIZE=3D2>>>>>>>>previously without =
problems). I got an error</FONT>
<BR><FONT SIZE=3D2>>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>>Processing error. =
Attribute "keywordType" with value "discipline" =
must</FONT>
<BR><FONT SIZE=3D2>>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>> have</FONT>
<BR><FONT SIZE=3D2>>>> </FONT>
<BR><FONT SIZE=3D2>>>>>>>>a value from the list =
"(place|stratum|temporal|theme)". </FONT>
<BR><FONT SIZE=3D2>>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>>This was apparently =
caused by the keyword "Invasion Ecology",</FONT>
<BR><FONT SIZE=3D2>entered as</FONT>
<BR><FONT SIZE=3D2>>>>>>>>type =
"discipline". I suspect that somehow deleted the =
type</FONT>
<BR><FONT SIZE=3D2>"discipline"</FONT>
<BR><FONT SIZE=3D2>>>>>>>>was dropped in the perl =
processing (perhaps an array or hash problem).</FONT>
<BR><FONT SIZE=3D2>>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>>Rudolf</FONT>
<BR><FONT SIZE=3D2>>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>>>></FONT>
<BR><FONT SIZE=3D2>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>-- </FONT>
<BR><FONT =
SIZE=3D2>>>>>***********************************************=
********************</FONT>
<BR><FONT SIZE=3D2>>>>>Matt =
Jones &=
nbsp; &=
nbsp; =
jones at nceas.ucsb.edu</FONT>
<BR><FONT SIZE=3D2>>>>><A =
HREF=3D"http://www.nceas.ucsb.edu/" =
TARGET=3D"_blank">http://www.nceas.ucsb.edu/</A> Fax: =
425-920-2439 Ph: 907-789-0496</FONT>
<BR><FONT SIZE=3D2>>>>>National Center for Ecological =
Analysis and Synthesis (NCEAS)</FONT>
<BR><FONT SIZE=3D2>>>>></FONT>
<BR><FONT SIZE=3D2>>>>>Interested in ecological =
informatics? <A HREF=3D"http://www.ecoinformatics.org" =
TARGET=3D"_blank">http://www.ecoinformatics.org</A></FONT>
<BR><FONT =
SIZE=3D2>>>>>***********************************************=
********************</FONT>
<BR><FONT SIZE=3D2>>>>></FONT>
<BR><FONT SIZE=3D2>>>>></FONT>
<BR><FONT SIZE=3D2>>>> =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>>>> eml-dev mailing list</FONT>
<BR><FONT SIZE=3D2>>>> eml-dev at ecoinformatics.org</FONT>
<BR><FONT SIZE=3D2>>>> <A =
HREF=3D"http://www.ecoinformatics.org/mailman/listinfo/eml-dev" =
TARGET=3D"_blank">http://www.ecoinformatics.org/mailman/listinfo/eml-dev=
</A></FONT>
<BR><FONT SIZE=3D2>>>> </FONT>
<BR><FONT SIZE=3D2>>></FONT>
<BR><FONT SIZE=3D2>>></FONT>
<BR><FONT SIZE=3D2>>>-- </FONT>
<BR><FONT =
SIZE=3D2>>>*******************************************************=
************</FONT>
<BR><FONT SIZE=3D2>>>Matt =
Jones &=
nbsp; &=
nbsp; =
jones at nceas.ucsb.edu</FONT>
<BR><FONT SIZE=3D2>>><A HREF=3D"http://www.nceas.ucsb.edu/" =
TARGET=3D"_blank">http://www.nceas.ucsb.edu/</A> Fax: =
425-920-2439 Ph: 907-789-0496</FONT>
<BR><FONT SIZE=3D2>>>National Center for Ecological Analysis and =
Synthesis (NCEAS)</FONT>
<BR><FONT SIZE=3D2>>></FONT>
<BR><FONT SIZE=3D2>>>Interested in ecological informatics? <A =
HREF=3D"http://www.ecoinformatics.org" =
TARGET=3D"_blank">http://www.ecoinformatics.org</A></FONT>
<BR><FONT =
SIZE=3D2>>>*******************************************************=
************</FONT>
<BR><FONT SIZE=3D2>>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>eml-dev mailing list</FONT>
<BR><FONT SIZE=3D2>eml-dev at ecoinformatics.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://www.ecoinformatics.org/mailman/listinfo/eml-dev" =
TARGET=3D"_blank">http://www.ecoinformatics.org/mailman/listinfo/eml-dev=
</A></FONT>
</P>
</BODY>
</HTML>=
--Boundary_(ID_JwqLIRlKcajMqI4vx9c4uw)--
More information about the Eml-dev
mailing list