You are not logged in.

Announcement

Welcome to the forum for discussion of NBN technical issues. If you are new and want some guidance on getting started view the help page. Be sure to read this if you need help on setting up Email Digests, which will allow you to recieve forum updates via email. This forum is dedicated to the various aspects of the NBN including Recorder biological recording software, Indicia and the NBN Gateway as well as the needs of the NBN technical group.

#1 2010-03-04 09:18:53

johnvanbreda
Moderator
From: UK
Registered: 2006-04-27
Posts: 659
Website

Measurement Field Lengths

Seeing that SQL Server will only store the data that is present in a VARCHAR field and will not waste space, is there any reason why the field length of the data field in Taxon_Occurrence_Data is only 20 characters (similar for the other measurement types though some are 40)? I guess I can answer my own question - the reason is legacy from Access when we were trying not to waste space. But I want to be able to attach descriptive data to my occurrences, and to keep these descriptions in separate fields rather than mix it all up in the comments field. The measurements would seem an ideal place to keep these (unless we go the whole hog and add a new tab for descriptors) but for the data length issue. I appreciate that the measurements grid may not cope well with longer pieces of text, but my primary concern at this stage is getting data in so that it is most useful in future.


John van Breda
Biodiverse IT

Offline

 

#2 2010-03-04 09:22:09

RobLarge
Veteran
From: Wiltshire
Registered: 2008-07-15
Posts: 246
Website

Re: Measurement Field Lengths

I agree John, I have been using the measurements tab in this way also and find the truncation annoying at times.


Rob Large
Wildlife Sites Officer
Wiltshire & Swindon Biological Records Centre
robl@wiltshirewildlife.org

Offline

 

#3 2010-03-04 10:40:32

Janet Simkin
Veteran
From: Northumberland
Registered: 2006-05-10
Posts: 88

Re: Measurement Field Lengths

I raised this a couple of years ago as we really need a 32 character field to handle our measurement data. At that time I seem to remember being told that it could be changed but wouldn't be as I was the only person asking for it. Now it is a more general requirement, so let's hope for a more positive response!

Janet


Janet Simkin
British Lichen Society

Offline

 

#4 2010-03-04 13:35:30

Lynn Heeley
Administrator
Registered: 2008-07-03
Posts: 312

Re: Measurement Field Lengths

Thanks I have noted this. The import wizard truncates the measurement qualifier to 20 characters despite there being enough room for 40 in the database itself - this is being resolved in the next build.

Lynn

Offline

 

#5 2010-04-29 10:41:35

johnvanbreda
Moderator
From: UK
Registered: 2006-04-27
Posts: 659
Website

Re: Measurement Field Lengths

Hi Mary
Please could you give us some feedback as to where in the priorities list increasing the measurement data field lengths from 20 or 40 characters to at least, say, 100 characters? Is it likely to happen in a future build?

Best Wishes


John van Breda
Biodiverse IT

Offline

 

#6 2010-04-30 15:46:13

Mary Campling
Moderator
Registered: 2010-04-16
Posts: 60

Re: Measurement Field Lengths

Hi John,

The feature request has been logged on the 'wish list' but no priority level has been set as of yet.
However the amendment to the import wizard of increasing the allowable field size for 'measurement qualifier' from 20 to 40 characters will be included in the next release (June).

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2008 PunBB