hort.net Seasonal photo, (c) 2006 Christopher P. Lindsey, All Rights Reserved: do not copy
articles | gallery of plants | blog | tech blog | plant profiles | patents | mailing lists | top stories | links | shorturl service | tom clothier's archive0
Gallery of Plants
Tech Blog
Plant Profiles
Mailing Lists
    Search ALL lists
    Search help
    Subscription info
Top Stories
sHORTurl service
Tom Clothier's Archive
 Top Stories
New Trillium species discovered

Disease could hit Britain's trees hard

Ten of the best snowdrop cultivars

Plant protein database helps identify plant gene functions

Dendroclimatologists record history through trees

Potato beetle could be thwarted through gene manipulation

Hawaii expands coffee farm quarantine

Study explains flower petal loss

RSS story archive

re: Checklist conversion to Database program

  • To: iris-l@Rt66.com
  • Subject: re: Checklist conversion to Database program
  • From: Tom Tadfor Little <telp@Rt66.com>
  • Date: Wed, 6 Nov 1996 15:34:02 -0700

Chad Schroter writes

:        If you scan the Checklists into files (ie .csv). The files can be
:imported into many data base programs ie. Microsoft Access. If the scanned
:data does not conform to the import data requirements (ie. we need to add
:to delineate some fields) but does adhere to some format in terms of
:number of
:fields etc., It should be possible to write a program that would "parse" the
:checklist entries into separate fields with commas etc. prior to importing it
:into the database.

Several of us conducted an extended discussion on this subject off-list
a few months back. The problem is that the printed checklists themselves
are not consistent in the "fields" they use for registration data, and there
are many nuances in properly interpreting registration entries, especially
from the older checklists. If you have access to the 1939 checklist, open
it up and compare a few entries with those in the current set of R & Is.
I'm convinced that a human being with iris knowledge would have to review
each entry in order to correctly feed it into a database.

Tom Tadfor Little                  telp@Rt66.com
Santa Fe, New Mexico (USA)
Telperion Productions  http://www.rt66.com/telp/

 © 1995-2017 Mallorn Computing, Inc.All Rights Reserved.
Our Privacy Statement
Other Mailing lists | Author Index | Date Index | Subject Index | Thread Index