VegBank

• Bug 986 has been marked as a duplicate of this bug. ***

The commconcept.commdescription field is 5000 chars long and it is being
populated by an Access Memo field ( < 64,000 char ) ....

only a tiny percentage of fields are giving trouble so I am unsure of what to do

a) Increase this field until we have no errors.
b) Increase this field up to the access max.
c) Truncate the field at some appropriate lenght.
d) a) and c)

The easiest is 'b)' but I am uncomfortable with this for some unknown reason.

regarding comment #2, we should probably just make the field a "text" field,
like these, rather than a varchar field. This makes it an unlimited length
character string in PostGreSQL, whereas Access can handle ~2Million if entered
programatically, I think. So I think we're OK on both sides as far as length
goes.

commClass.classNotes text,
commInterpretation.notes text,
coverIndex.indexDescription text,
disturbanceObs.disturbanceComment text,

comment #3 solves comment #2
Postgesql Text is the data type we want here and in other places mentioned. I
overlooked this type in the postgresql documentation.

This is here so that we know to deal with <i> and </i> in incoming natureserve
data. Leaving these alone will NOT result in italizing text in our display, at
least not without some alterations to our displaying features.

EcoArt is fine the way it is. We'll try to match new comms to current ones when
NatureServe gets their data to us.

changed from components that are to be deleted to "misc" so that bugs don't get
deleted with component. Sorry for all the email.

Original Bugzilla ID was 985