4,713
edits
Dataset Errata: Difference between revisions
Jump to navigation
Jump to search
m
→Errors noted in varioushttps://www.idigbio.org/wiki/skins/common/images/button_nowiki.png files
| Line 12: | Line 12: | ||
('''Ed''': Verbatim field contain verbatim results. No lichen labels have DwC complaint decimal coordinates. Likewise, no labels has DwC compliant event dates, thus '''you probably only want to only use verbatim fields for stats''') | ('''Ed''': Verbatim field contain verbatim results. No lichen labels have DwC complaint decimal coordinates. Likewise, no labels has DwC compliant event dates, thus '''you probably only want to only use verbatim fields for stats''') | ||
Check this with Alex --[[User:Dpaul|Dpaul]] 16:33, 12 June 2013 (EDT) | Check this with Alex --[[User:Dpaul|Dpaul]] 16:33, 12 June 2013 (EDT) | ||
<br> | |||
<br> | |||
<br> | <br> | ||
This is open to debate, but I think Elevation should be a pure numeric field, assumed to be in meters. Therefore, it should not be expressed as "750 m", but rather as "750". verbatimElevation, of course, should retain the "m" if it was present on the label. (Note that Darwin Core apparently does not have a field called "elevation", but rather MinimumElevationInMeters, and MaximumElevationInMeters, both numeric fields.) Not sure if this is something to change on the labels, but worth being aware of. I think parsing programs should generate the Darwin Core fields. ('''Daryl''') | This is open to debate, but I think Elevation should be a pure numeric field, assumed to be in meters. Therefore, it should not be expressed as "750 m", but rather as "750". verbatimElevation, of course, should retain the "m" if it was present on the label. (Note that Darwin Core apparently does not have a field called "elevation", but rather MinimumElevationInMeters, and MaximumElevationInMeters, both numeric fields.) Not sure if this is something to change on the labels, but worth being aware of. I think parsing programs should generate the Darwin Core fields. ('''Daryl''') | ||
| Line 17: | Line 19: | ||
('''Bryan:''' Odd to not have "elevation" I agree with the use of verbatimElevation. If "elevation" is filled it is numeric.) <br> | ('''Bryan:''' Odd to not have "elevation" I agree with the use of verbatimElevation. If "elevation" is filled it is numeric.) <br> | ||
('''Deb''': What are the ramifications then? Does the lichen set need to be fixed in this regard? or just ignore derived columns and expect letters like m or mi or ft in verbatimElevation field?)--[[User:Dpaul|Dpaul]] 16:40, 12 June 2013 (EDT) | ('''Deb''': What are the ramifications then? Does the lichen set need to be fixed in this regard? or just ignore derived columns and expect letters like m or mi or ft in verbatimElevation field?)--[[User:Dpaul|Dpaul]] 16:40, 12 June 2013 (EDT) | ||
<br> | |||
<br> | |||
<br> | |||
Inconsistency in the Gold Parsed labels for Country. If a US State is listed as the state, the label doesn't always say the name of the country, though it is obviously the USA. Some Gold parsed results leave it blank, some fill it in with "USA", or "United States", though neither of these are on the label. I think it is valid to fill it in, but it should be consistent. ('''Daryl''') | Inconsistency in the Gold Parsed labels for Country. If a US State is listed as the state, the label doesn't always say the name of the country, though it is obviously the USA. Some Gold parsed results leave it blank, some fill it in with "USA", or "United States", though neither of these are on the label. I think it is valid to fill it in, but it should be consistent. ('''Daryl''') | ||
<br>('''Bryan''': I think for Gold the field should not be filled in if it is not on the label.) | <br>('''Bryan''': I think for Gold the field should not be filled in if it is not on the label.) | ||
<br> | |||
<br> | |||
<br> | |||
Many Gold Parse Tennessee lichen labels have country errors. | Many Gold Parse Tennessee lichen labels have country errors. | ||
<br>Examples: | <br>Examples: | ||
| Line 29: | Line 35: | ||
-- Gold Parsed TENN-L-0000005_lg.csv leaves country blank, but the label shows it as "USA". Again, maybe this is OK, but it should be consistent. (Daryl) (Bryan: Agreed. Should be fixed to match the OCR label.) (Ed: Fixed, country had county value) | -- Gold Parsed TENN-L-0000005_lg.csv leaves country blank, but the label shows it as "USA". Again, maybe this is OK, but it should be consistent. (Daryl) (Bryan: Agreed. Should be fixed to match the OCR label.) (Ed: Fixed, country had county value) | ||
<br> | |||
<br> | |||
<br> Inconsistency and errors in TENN Lichen Gold Parsed dateIdentified. Examples: | <br> Inconsistency and errors in TENN Lichen Gold Parsed dateIdentified. Examples: | ||