Ecoinformatics Redmine: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362007-08-28T17:28:38ZEcoinformatics Redmine
Redmine InfoVeg - Bug #2913 (Closed): Ipomoea pes-capraehttps://projects.ecoinformatics.org/ecoinfo/issues/29132007-08-28T17:28:38Zxianhua liurobertliu325@yahoo.com
<p>Because Alan had the relationship as "?", we do not know whether or not</p>
<p>(in the range of Alan's flora) I.p. var emarginata sec Weakley < I.p.<br /> ssp <br />brasiliensis sec USDA. Thus, a determination to ssp brasiliensis is <br />indeterminant (ambiguous in our terminology) as to whether it belongs<br /> to <br />var emarinata. Given Alan recognizes only one taxon in the region and<br /> USDA <br />recognizes only one, it seems to me a no-brainer that the correct <br />relationship should be =, with the caveat that this is a<br /> region-specific <br />relationship and might not always apply elsewhere in the world. I am<br /> not <br />sure at what point Alan started being careful to make his concept maps <br />region specific rather than global, but perhaps after he handled I.c.<br /> ssp <br />e.</p>
<p>I note that the Carteret County record for I.p. shows up for the ssp<br /> and <br />not for the full species. This is an error which I will ask Xianhua to</p>
<p>log as a bug and eventually look into.</p>
<p>Bob</p>
<p>On Mon, 27 Aug 2007, Carol Ann McCormick wrote:</p>
<blockquote>
<p>Hmmm. I do not know why this is showing up as wimpy pink. We have</p>
</blockquote>
two
<blockquote>
<p>specimens: one is a photograph, then Matt Windsor collected the dead</p>
</blockquote>
dried
<blockquote>
<p>up stalk a few weeks later.</p>
<p>The confusion MAY come in the var. emarginata / ssp. brasiliensis .</p>
</blockquote>
Alan
<blockquote>
<p>had it as var. emarginata, but SPECIFY insists on putting it as ssp.<br />brasiliensis.</p>
<p>In Alan's flora he has I. P-c. var. emarginata as ? synonym with ssp.<br />brasiliensis.</p>
<p>This clarifies nothing I realize.</p>
<p>On a brighter note, Laura Cotterman is sending stuff about Eupatorium<br />paludicola to UNC Press Office today. She just called to ask</p>
</blockquote>
"exactly what
<blockquote>
<p>IS an Herbarium Associate?" I had to admit that it just means that</p>
</blockquote>
we give
<blockquote>
<p>you a key. And let you treat us to lunch frequently.</p>
<p>Carol Ann McCormick<br />Assistant Curator<br />University of North Carolina Herbarium (NCU)<br />CB#3280 Coker Hall<br />University of North Carolina<br />Chapel Hill NC 27599-3280 U.S.A.</p>
<p>-----Original Message-----<br />From: Richard LeBlond [mailto:<a class="email" href="mailto:RichardLeBlond@charter.net">RichardLeBlond@charter.net</a>]<br />Sent: Monday, August 27, 2007 10:49 AM<br />To: Carol Ann McCormick, MCS; Alan Weakley<br />Subject: online database</p>
<p>I see that the collections of Ipomoea pes-caprae from Carteret Co.</p>
</blockquote>
are
<blockquote>
<p>"ambiguous specimens." Am I correct that ambiguity refers to</p>
</blockquote>
identity?
<blockquote>
<p>-- <br />Richard LeBlond<br />P.O. Box 787<br />Richlands, NC 28574<br />(910) 324-2671</p>
</blockquote>
<p>====================================================================<br /> Robert K. Peet, Professor Phone: 919-962-6942<br /> Department of Biology, CB#3280 Fax: 919-962-6930<br /> University of North Carolina Cell: 919-368-4971<br /> Chapel Hill, NC 27599-3280 USA Email: <a class="email" href="mailto:peet@unc.edu">peet@unc.edu</a><br /> <a class="external" href="http://www.bio.unc.edu/faculty/peet/">http://www.bio.unc.edu/faculty/peet/</a>
====================================================================</p> SEEK - Bug #2731 (New): Make TCS document the direct data sourcehttps://projects.ecoinformatics.org/ecoinfo/issues/27312007-01-17T01:35:00Zxianhua liurobertliu325@yahoo.com
<p>Develop new functions to directly access TCS document.</p> SEEK - Bug #2730 (New): Publication problemhttps://projects.ecoinformatics.org/ecoinfo/issues/27302007-01-17T01:30:39Zxianhua liurobertliu325@yahoo.com
<p>For publication let's use be use to implement both short and long full text and guid. The rest is unnecessary for now.</p> SEEK - Bug #2729 (New): Support third party parent-child relationshiphttps://projects.ecoinformatics.org/ecoinfo/issues/27292007-01-17T01:28:45Zxianhua liurobertliu325@yahoo.com
<p>Third party parent-child, and should we allow parents to be specified for genus in definition.</p> SEEK - Bug #2728 (New): XML Output problemhttps://projects.ecoinformatics.org/ecoinfo/issues/27282007-01-17T01:23:45Zxianhua liurobertliu325@yahoo.com
<p>Mostly validation was fine, but one minor problem was <br />identified. TaxonRankEnum X puts in string like genus, when <br />should be TaxonomicRankGenusEnum. Suggest validate with XMLSpy or <br />Oxygen</p> SEEK - Bug #2727 (New): lost data during importhttps://projects.ecoinformatics.org/ecoinfo/issues/27272007-01-17T01:20:04Zxianhua liurobertliu325@yahoo.com
<p>One problem is that superfluous stuff is lost. For example:<br /><teeth>Y-5 molar pattern</teeth><br />We should capture all this in some form of buffer so it can be <br />exported. For example, all 18 relationship types shoudl come in and go out.</p>