Dataset Errata

From iDigBio
Jump to: navigation, search

Errors noted in various files

New Errors 2/27/13

Gold Parsing Errors


Lichen Gold


verbatimLatitude and verbatimLongitude


Many of the Lichen Gold labels have verbatimLatitude and verbatimLongitude, but the Gold Parsed files do not have the calculated decimalLatitude and decimalLongitude. This seems especially true for the New York labels. (Daryl)
(Bryan: I think the decimal values were "bonus" I could be wrong. If we choose to do this later it might be easier to pre-fill as many fields as we can using your algorithm.)
(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 --Dpaul 16:33, 12 June 2013 (EDT)

elevation verbatimElevation

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)
(Bryan: Odd to not have "elevation" I agree with the use of verbatimElevation. If "elevation" is filled it is numeric.)
(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?)--Dpaul 16:40, 12 June 2013 (EDT)

Clarified - in conversation with Daryl, we will leave verbatimElevation as is, if anyone wants to calculate min / max elevation in meters -- that's extra credit. --Dpaul 17:54, 3 July 2013 (EDT)

Gold Parsed Country errors

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)
(Bryan: I think for Gold the field should not be filled in if it is not on the label.)
(Deb: Note, to be clear!, the country is often in the DatasetName and from that, most (all?) of us put the country listed there in the dwc:country field). This seems fine and right to me.
(Deb: A different issue is putting in the country when it's not listed anywhere on the label -- that's indeed inference -- and we ought to try and clean that up where it happened. IMHO. --Dpaul 21:00, 13 June 2013 (EDT)).


Many Gold Parse Tennessee lichen labels have country errors.
Examples:

(Deb: if there are many country errors on these, where the error is one of putting country in by deducing it because the state is in the USA, ...removing the value will take some time to fix as every single record will need to be verified. --Dpaul 16:40, 12 June 2013 (EDT))

-- Gold Parsed TENN-L-0000001_lg.csv lists country as "USA", but on the .txt label, it is "U.S.A." (with periods).
Same with Gold Parsed TENN-L-0000035_lg.csv and others.(Daryl)  
(Bryan: Agreed. Should be fixed to match the label.)
(Ed: fixed, note that TENN-L-0000035_lg.txt has "U. S. A. " with spaces, thus conserved format)

-- 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)


Inconsistency and errors in TENN Lichen Gold Parsed dateIdentified. Examples:

dateIdentified or verbatimEventDate errors

-- TENN-L-0000015_lg.csv has dateIdentified in the wrong format, neither verbatim, nor standard DarwinCore format: Verbatim would be: Nov. 12, 1939, DarwinCore would be: 1939-11-12, Listed is: 1939-November-12.
(Bryan: I think excel may have imposed it's own format and changed the records. If the column type is set to "text" Excel will not transform to a new format. )
(Ed: The verbatimEventDate (not dateIdentified is in the correct format, but if you open file in excel it will convert the display to match program's defaults)).
Deb - verified verbatimEventDate="Nov. 12, 1939 in csv --Dpaul 21:21, 13 June 2013 (EDT)
-- TENN-L-0000017_lg.csv omits dateIdentified, though it is on the label as 3 Feb. 1963 
(Bryan: Agreed. Should be fixed to match the label.)
(Ed: That is the collection date, not the dateIdentified. Format is correct in verbatimDate)
Deb: this is a confusing label! the line begins with

Det.:Barbara Moore, this is followed by Date: 3 Feb 1963.
(A person who knows this collector's label and habits would know if the date represents collected or identified date. An outsider may very well conclude eventDate (date collected) is missing.--Dpaul 21:21, 13 June 2013 (EDT)


-- TENN-L-0000019_lg.csv has 1954-Aug-8, but on the label it is "8 Aug 1954", again neither verbatim nor DarwinCore (1954-08-08). (Daryl) 
(Bryan: Agreed. Should be fixed to match the label.)
Deb: in csv, dwc:verbatimEventDate=8 Aug 1954
dwc:eventDate=1954-08-08
dwc:dateIdentified=1954-Aug-8
it's this last field that's funky and I"ve changed it to be 1954-08-08 --Dpaul 21:32, 13 June 2013 (EDT)

comma, space, period, apostrophe in verbatimCoordinates errors

Gold Parsed NY01075760_lg.csv replaces the comma with a space, and replaces an apostrophe (') with a double quote (") in verbatimCoordinates: 38°42'20"N, 83°08'25'W is rendered as 38°42'20""N 83°08'25""W. (Note also that the double quote is replaced with two double quotes. This may be necessary to preserve the quote-delimited, comma separated fields, but could cause some problems when uploading to a database. Not presented here as an error, but we should be aware of possible implications.) 
(Bryan: Agreed. Should be fixed to match the Label except, the double quoted double quote I think is needed for CSV readers to identify fileds. I am not sure)

Fixed --Dpaul 21:49, 13 June 2013 (EDT) See this for how csv looks now.
NY01075760_lg.csv:Richard C. Harris,52766,"38°42'20""N 83°08'25""W",21 May 2006,2006-05-21,,Scioto,Ohio,U.S.A.,Polycoccum minutulum Kocourková & 'F. Berger,"Shawnee State Forest, along Pond Lick Run N of Forest Road 1, 0.35 mi SW of SR 125",sandstone boulders along stream and adjacent oak woods.,on Trapeliopsis placodioides Coppins & James,ca. 190 m,,,"38°42'20""N",83°08'25'W,1075760,New York Botanical Garden,,Polycoccum minutulum Kocourková & F. Berger,,,,


Gold Parsed NY01075764_lg.csv has a similar problem where a single space is replaced with a double space in verbatimCoordinates. 
(Bryan: Agreed. Should be fixed to match the label as best as possible. If it is not clear follow the OCR file.)

Inconsistencies in several Gold Parsed labels regarding whether to include the period at the end of a field as part of the field. Example: verbatimCoordinates in NY01075782_lg.csv includes the period at the end. NY01075780_lg.csv does not include the period. (Bryan: It could go either way but I think for consistancy throughout we should keep the period at the end of anything. Whenever there are sentences with a period we keep them as in "One mile east of Dodge City." we would not think of removing the period. In gold we should treat it as verbatim. If we do platinum it could be removed.)

Gold Parsed NY01075761_lg.txt corrects a Gold OCR error by adding the 1 to the end of 0107576. The field should be corrected in the Gold OCR, but until done so, the parsing should be verbatim (see below under Gold OCR Errors). (Bryan: hmmm. Gold shoudl be as-if the OCR engine read the label with no mistakes. Silver would leave it as 0107576 but in Gold we shoudl put what was on the label. That would include the "1".)

Gold Parsed NY01075766_lg.csv omits the catalogNumber, though it is present in the NY01075766_lg.txt file. (Bryan: Agreed. Should be fixed to match the label.)

Gold Parsed NY01075789_lg.csv adds "NY" as a prefix to the catalogNumber, though it is not present on the .txt file. (Bryan: Agreed. Should be fixed to match the Label.)

Gold Parsed NY01075760_lg.csv omits dataset, which should be "Lichens of Ohio" (Bryan: Agreed. Should be fixed to match the label.)

Gold Parsed NY01075775_lg.csv omits "Boulder" from municipality.(Bryan: Agreed. Should be fixed to match the Label.)

Gold Parsed NY01075761_lg.csv lists "Peru" as municipality, but NY01075779_lg.csv lists "Town of Peru", though they both appear identical ("Town of Peru") on the labels. Probably should be "Peru" on both...? (Bryan: This is complex but in this case I think it should be "Town of Peru". The bald "Peru" could be read as an error with the misplacment of "Country". Likely the Label author was worried about the same thing and included "Town of". In both cases include what is on the label.)

Gold Parsed TENN-L-0000029_lg.csv and TENN-L-0000035_lg.csv both list municipality as "NORTH AMERICA" (Bryan: Agreed. Should be assigned to "country".)

Gold Parsed TENN-L-0000083_lg.csv lists municipality as "Ontario", but this is not on the label. (Bryan: Agreed. Should be fixed to match the label.)

Gold Parsed WIS-L-0011732_lg.csv (and many other lichen gold parsed labels) removes a space from verbatimLatitude and from verbatimLongitude, changing this: 60° 33.579'N into this: 60°33.579'N. The space removal is inconsistent, on some labels, not on others.  (Bryan: Agreed. Should be fixed to match the label. I think if the OCR had been perfect the space would not be n the OCR file do it is a tough call.)



Gold Parsed NY01075791_lg.csv converts the "u" in "Mull" to an umlaut yielding "Müll". This actually reflects the original label, but not the Gold OCR NY01075791_lg.txt file, which has "Mull". Same for NY01075792_lg.csv, and several other in the series. (Bryan: The OCR messed up. Gold should fix OCR errors so the umlaut shoudl saty.)

FIXED for Lichen set in gold csv of /home/aocr/webroot/datasets/lichens/gold/parsed and gold txt of /home/aocr/webroot/datasets/lichens/gold/ocr
made the csv and txt files consistent with the label image -- if umlaut is present in the image, I put it in the csv and txt files. --Dpaul 17:40, 1 July 2013 (EDT)

Gold Parsed CSV File Issues

Lichen NY CSV

There are more errors in gold csv files. (Qianjin)
(Bryan: I agree with Qianjin's edits except as noted below)

NY01075759_lg verbatimEventDate (1998-04-19), it should be 19 April 1998

From Deb: path /home/aocr/webroot/datasets/lichens/gold/parsed the csv file, opened in Notepad++ has 19 April 1998, encoding is ANSI --Dpaul 21:20, 30 June 2013 (EDT)

I think the CSV file is now correct with "19 April 1998" --Pbryan.heidorn 18:44, 2 July 2013 (EDT)

here's what it looks like when opened in Notepad++
dwc:recordedBy, dwc:recordNumber, dwc:verbatimCoordinates, dwc:verbatimEventDate, dwc:eventDate, dwc:municipality, dwc:county, dwc:stateProvince, dwc:country, aocr:verbatimScientificName, dwc:verbatimLocality, dwc:habitat, dwc:substrate, dwc:verbatimElevation, dwc:identifiedBy, dwc:dateIdentified, dwc:verbatimLatitude, dwc:verbatimLongitude, dwc:catalogNumber, aocr:verbatimInstitution, dwc:datasetName, dwc:scientificName, dwc:decimalLatitude, dwc:decimalLongitude, dwc:fieldNotes, dwc:sex
Richard C. Harris,42164,"41°11'N, 74°08'W",19 April 1998,1998-04-19,,Rockland,NEW YORK,U.S.A.,,"Harriman State Park, along Woodtown Road West near dam at S end of Lake Sebago along Seven Lakes Drive",mixed hardwood-hemlock forest with granitic erratics.,on Trapelia placodioides Coppins & P. James,ca. 240 m,,,41°11'N,74°08'W,01075759,New York Botanical Garden,Lichens of New York State,Polycoccum minutulum Kocourkova & F. Berger,,,,
here's what it looks like when I open it at the command line with text editor (vi)
dwc:recordedBy, dwc:recordNumber, dwc:verbatimCoordinates, dwc:verbatimEventDate, dwc:eventDate, dwc:municipality, dwc:county, dwc:stateProvince, dwc:country, aocr:verbatimScientificName, dwc:verbatimLocality, dwc:habitat, dwc:substrate, dwc:verbatimElevation, dwc:identifiedBy, dwc:dateIdentified, dwc:verbatimLatitude, dwc:verbatimLongitude, dwc:catalogNumber, aocr:verbatimInstitution, dwc:datasetName, dwc:scientificName, dwc:decimalLatitude, dwc:decimalLongitude, dwc:fieldNotes, dwc:sex
Richard C. Harris,42164,"41°11'N, 74°08'W",1998-04-19,4/19/1998,,Rockland,NEW RK,U.S.A.,,"Harriman State Park, along Woodtown Road West near dam at S end of Lake Sebago along Seven Lakes Drive",mixed hardwood-hemlock forest with granitic erratics.,on Trapelia placodioides Coppins & P. James,ca. 240 m,,,41°11'N,74°0W,01075759,New York Botanical Garden,Lichens of New York State,Polycoccum minutulum Kocourkova & F. Berger,,,,


NY01075760_lg no datesetName

FIXED in /home/aocr/webroot/datasets/lichens/gold/parsed --Dpaul 23:18, 30 June 2013 (EDT)

NY01075765_lg verbatimEventDate (Feb. 1898), it should be verbatimEventDate ( Feb 1898.)

FIXED in /home/aocr/webroot/datasets/lichens/gold/parsed --Dpaul 23:18, 30 June 2013 (EDT)

NY01075766_lg decimalLatitude (White Horse Beach, between Manomet Pt. and Rocky Pt., Plymouth area), it should be locality or habitat; no catalogNumber

FIXED in /home/aocr/webroot/datasets/lichens/gold/parsed --Dpaul 23:18, 30 June 2013 (EDT)
NOTE since there's no host field, the shell of Balanus balanoides is in habitat which really is not right --Dpaul 23:18, 30 June 2013 (EDT)

This is beyond scope for this project but you are correct. Pbryan.heidorn 18:38, 2 July 2013 (EDT)

NY01075767_lg verbatimEventDate format

FIXED in /home/aocr/webroot/datasets/lichens/gold/parsed --Dpaul 23:18, 30 June 2013 (EDT)

NY01075767_lg verbatimEventDate (July 1979), it should be (Jul-79)

See error above, Label reads July 1979 I fixed the verbatimEventDate to match.--Dpaul 23:18, 30 June 2013 (EDT)

NY01075768_lg country (canada), it should be (ca.) 

Fixed verbatim locality to include the ca. (iow, about) --Dpaul 23:18, 30 June 2013 (EDT)

NY01075770_lg habitat (on Acmaea digitalis Eschsch. Host determined by A. R. Grant) and identifiedBy (A. R. Grant.)

fixed habitat to read: on Acmaea digitalis Eschsch. Host determined by A. R. Grant.
removed A. R. Grant. from identifiedBY (she or he identified the host, not the lichen)--Dpaul 23:18, 30 June 2013 (EDT)

NY01075770_lg habitat (Host determined by A. R. Grant)

see above --Dpaul 23:18, 30 June 2013 (EDT)

NY01075771_lg verbatimCoordinates mixed with verbatimLocality

verbatimLocality -includes all information in the locality -- looks correct to me.--Dpaul 23:18, 30 June 2013 (EDT)
I agree Pbryan.heidorn 18:38, 2 July 2013 (EDT)
verbatim coordinates on this record probably ought to be blank since the collector essentially provided 3 different sets of lat / lon values.--Dpaul 23:18, 30 June 2013 (EDT)
I did not change this record.--Dpaul 23:18, 30 June 2013 (EDT)

NY01075779_lg habitat concatenation (Bryan: "on Protoblastenia rupestris" appears before the location and habitate section of the label. However, Habitate says "dolomite rock along lake shore and adjacent Thuja forest; on Protoblastenia rupestris". There was a period after "forest". The period was removed and a ";" added. Then the "on Protoblastenia rupestris" from the earlier part of the label was concatinated. 

changed dwc:habitat to:
on Protoblastenia rupestris dolomite rock along lake shore and adjacent Thuja forest.
--Dpaul 23:19, 30 June 2013 (EDT)

NY01075780_lg NEW YOUR BOTANICAL GARDEN (Bryan: the label said "GARDEN". The OCR said "CARDEN". SIlver should be "CARDEN" Gold should be "GARDEN"

the OCR I see says "Garden" in /home/aocr/webroot/datasets/lichens/silver/ocr --Dpaul 23:19, 30 June 2013 (EDT)
fixed the Gold (changed from Carden to Garden), left the silver alone.--Dpaul 23:19, 30 June 2013 (EDT)

NY01075789_lg catalogNumber (NY01075789) in the csv file; but it is (01075789) in the text file.

fixed in gold csv (path is /home/aocr/webroot/datasets/lichens/gold/parsed) --Dpaul 23:19, 30 June 2013 (EDT)

NY01075797_lg recordedBy ( William Russell Buck) in the csv file; but it is (William R. Buck) in the text file.

fixed in gold csv (path is /home/aocr/webroot/datasets/lichens/gold/parsed) --Dpaul 23:19, 30 June 2013 (EDT)

NY01075805_lg stateProvince (South Carolina) in the csv file; but it is (S.C.) in the text file.

changed to S.C. in the csv --Dpaul 23:19, 30 June 2013 (EDT)

NY01075812_lg recordedBy( William Russell Buck) in the csv file; but it is (William R. Buck) in the text file.

fixed --Dpaul 23:19, 30 June 2013 (EDT)

NY01075816_lg recordedBy( William Russell Buck) in the csv file; but it is (William R. Buck) in the text file.

fixed --Dpaul 23:19, 30 June 2013 (EDT)

NY01075817_lg recordedBy( William Russell Buck) in the csv file; but it is (William R. Buck) in the text file.

fixed --Dpaul 23:19, 30 June 2013 (EDT)

NY01075818_lg no scientificName

not null in the csv record I see in /home/aocr/webroot/datasets/lichens/gold/parsed
but the umlaut was missing from the txt file and the csv -- so I fixed that. --Dpaul 23:19, 30 June 2013 (EDT)

NY01075819_lg recordedBy( William Russell Buck) in the csv file; but it is (William R. Buck) in the text file.

fixed --Dpaul 23:19, 30 June 2013 (EDT)

NY01075820_lg recordedBy( William Russell Buck) in the csv file; but it is (William R. Buck) in the text file.

fixed --Dpaul 23:19, 30 June 2013 (EDT)

NY01075821_lg scientificName (null)

fixed --Dpaul 23:19, 30 June 2013 (EDT)

NY01075821_lg no scientificName

fixed --Dpaul 23:19, 30 June 2013 (EDT)

NY01075822_lg no scientificName

fixed --Dpaul 23:19, 30 June 2013 (EDT)

NY01075823_lg identifiedBy (Bryan: ?? I do not see the problem)

From Deb. We (the herb set) did put determinations on a separate line, as done in this file. We did not do it the same way, however. Need to discuss.--Dpaul 23:19, 30 June 2013 (EDT)
I did put in umlauts for the u's in the name Müll. (they are in image, not in csv or txt,but they should be).--Dpaul 23:19, 30 June 2013 (EDT)
not sure what to do. I guess leave as is since maybe programs can deal with it. --Pbryan.heidorn 18:44, 2 July 2013 (EDT)

TODO: fix all instances of Mull to Müll in txt and csv gold lichen at paths /home/aocr/webroot/datasets/lichens/gold/ocr and /home/aocr/webroot/datasets/lichens/gold/parsed --Dpaul 23:19, 30 June 2013 (EDT)

FIXED in ocr txt files and parsed csv files. --Dpaul 15:21, 1 July 2013 (EDT)

Lichen TENN CSV

TENN-L-0000001_lg verbatimLocality mixed with verbatimElevation

NOT FIXED i see no problem with this, the elevation is embedded in the locality. Then the relevant value is in the dwc:verbatimElevation (1500 m) field too.--Dpaul 15:47, 1 July 2013 (EDT)

TENN-L-0000010_lg verbatimLocality contains (Exposure W,) but habitat contains (Exposure W).

FIXED. verbatimLocality now contains ROCKY MOUNTAIN NATIONAL PARK, Exposure W, NW. Longs Peak, top of Trough and
FIXED. habitat contains "'Crystalline rocks. Exposure W, NW.--Dpaul 15:47, 1 July 2013 (EDT)

TENN-L-0000012_lg verbatimLocality (apria -s ) in the text file; but it is (apricas) in the csv file. (Bryan: on the label the word is hyphenated and split across lines. SO, if we ignore the "New Line" the word is "apria -cas" and not what Qianjin listed. so, folloing the rule for gold of making perfect OCR, character by character, the csv shoudl say "apria -cas")

FIXED (txt file is good as is, changed csv file to have a hyphen in the locality text string reading ...'ad rupes apri-cas' --Dpaul 15:47, 1 July 2013 (EDT)

TENN-L-0000014_lg identifiedBy (H. Kashiwadani) in the csv file; but it is identifiedBy (S. Kurokawa and H. Kashiwadani) in the text file.

Not what I see in gold csv. I see recordedBy:H. Kashiwadani and Y. Endo and identifiedBy:H. Kashiwadani which is correct.
no changes made. gold txt file is correct too.--Dpaul 16:08, 1 July 2013 (EDT)

TENN-L-0000015_lg verbatimInstitution (TENNESSEE (TENN))

From Deb: verbatimInstitution looks fine in the csv=HERBARIUM OF THE UNIVERSITY OF TENNESSEE -- that's what's on the actual label and in the gold txt file. --Dpaul 16:08, 1 July 2013 (EDT)
the person transcribing the image, put the name listed on the barcode in the gold txt file and it reads University of Tennessee (TENN)
NOT FIXED - I did not adjust these, they seem interpreted correctly to me.--Dpaul 16:08, 1 July 2013 (EDT)

TENN-L-0000016_lg verbatimInstitution (HERBARIUM OF THE UNIVERSITY OF TENNESSEE)

No error here - interpretation correct afaikt in gold csv and gold txt. not changed. --Dpaul 16:08, 1 July 2013 (EDT)

TENN-L-0000017_lg verbatimInstitution (University of Tennessee (TENN))

FIXED gold csv, label verbatimInstitution reads: HERBARIUM OF THE UNIVERSITY OF TENNESSEE now gold csv reads the same, as does the gold txt file --Dpaul 16:08, 1 July 2013 (EDT)

TENN-L-0000018_lg verbatimInstitution (University of Tennessee (TENN))

FIXED gold csv, label verbatimInstitution reads: HERBARIUM OF THE UNIVERSITY OF TENNESSEE now gold csv reads the same, as does the gold txt file --Dpaul 16:08, 1 July 2013 (EDT)

TENN-L-0000019_lg identifiedBy (Alt.Set.) in the csv file; verbatimEventDate (8 Aug 1954) is mixed with dateIdentified (8 Aug 1954)

FIXED gold csv. on original label, identifiedBy and dateidentifed are not provided. --Dpaul 16:22, 1 July 2013 (EDT)

TENN-L-0000021_lg verbatimInstitution ((TENN))

FIXED changed to:HERBARIUM OF THE UNIVERSITY OF TENNESSEE --Dpaul 16:22, 1 July 2013 (EDT)

TENN-L-0000022_lg verbatimEventDate (23 July 1955) is mixed with dateIdentified (23 July 1955)

FIXED, removed date from dateIdentified field as label appears to imply date collected and no way to be sure the identified date is the same. --Dpaul 16:22, 1 July 2013 (EDT)

TENN-L-0000033_lg no catalogNumber in OCRed text file

FIXED, put 67 in the recordnumber field, catalognumber is present (TENN-L-0000033) in the gold csv file I am looking at in the /home/aocr/webroot/datasets/lichens/gold/parsed csv files. --Dpaul 16:22, 1 July 2013 (EDT)

TENN-L-0000036_lg verbatimEventDate (format)

FIXED to read: Nov. 3, 1956 --Dpaul 16:49, 1 July 2013 (EDT)

TENN-L-0000036_lg eventDate (format)

FIXED to read 1956-11-03 --Dpaul 16:49, 1 July 2013 (EDT)

TENN-L-0000045_lg recordNumber (null)

TENN-L-0000045_lg stateProvince (Mont.) in the text file; but it is (Montana) in the csv file.

FIXED, changed dwc:stateProvince to literal label = Mont. --Dpaul 16:49, 1 July 2013 (EDT)

TENN-L-0000048_lg verbatimLocality (near) is mixed with habitat (near)

FIXED, removed near from habitat --Dpaul 16:49, 1 July 2013 (EDT)

TENN-L-0000050_lg stateProvince (Mont.) in the text file; but it is (Montana) in the csv file. verbatimElevation (Alt.: 6000 ft) in the csv file.

FIXED, changed dwc:stateProvince to literal label = Mont. --Dpaul 16:49, 1 July 2013 (EDT)

TENN-L-0000052_lg identifiedBy (Alt.: About 3500 ft.) FIXED, put Alt.: About 3500 ft. in dwc:verbatimElevation --Dpaul 16:49, 1 July 2013 (EDT)

TENN-L-0000053_lg identifiedBy is on the 2nd line; dateIdentified is on the 2nd line.

GET ED TO CHECK. --Dpaul 16:49, 1 July 2013 (EDT)
(I think) this lichen has 3 identifications. One original in 1969, two by J P Dey (one in 1973-74 and another in 1980)... and so there ought to be 3 lines (not 2) which is what I did. --Dpaul 16:49, 1 July 2013 (EDT)

TENN-L-0000054_lg identifiedBy (!A. Skorepa) in the text file; but it is (A. skoepa) in the csv file.

From Deb: note that ! means agreement with determination present. But in the nature of "exact" and "verbatim" transcription and parsing, I'm not sure of the correct tactic. I'd think we only want to parse the name and not the ! --Dpaul 16:49, 1 July 2013 (EDT)
YOUR INPUT? --Dpaul 16:49, 1 July 2013 (EDT)
I did fix the spelling in the txt and csv files, but did not do anything with the !. --Dpaul 17:29, 1 July 2013 (EDT)

TENN-L-0000056_lg oliff occurs in habitat but it is cliff in text file; dateIdentified (format)

FIXED in gold csv and gold txt --Dpaul 17:29, 1 July 2013 (EDT)

TENN-L-0000063_lg verbatimLocality contains scientific name

FIXED in gold csv --Dpaul 17:29, 1 July 2013 (EDT)

TENN-L-0000063_lg verbatimScientificName (Amherst)

FIXED in gold csv --Dpaul 17:29, 1 July 2013 (EDT)

TENN-L-0000064_lg recordedBy (H. A. Sierk) is mixed with identifiedBy (H. A. Sierk); verbatimEventDate (August 1, 1957) is mixed with dateIdentified (August 1, 1957)

FIXED in gold csv and gold txt
txt and csv had incorrect recordNumber
coll and det same person, correct to assume date for both is the same. I did change the formatting of dateIdentified to yyyy-mm-dd. --Dpaul 17:29, 1 July 2013 (EDT)

TENN-L-0000065_lg recordedBy (A. J. Sharp) is mixed with identifiedBy (A. J. Sharp) verbatimEventDate (31 July, 1955) is mixed with dateIdentified (31 July, 1955)

FIXED (see above). --Dpaul 17:29, 1 July 2013 (EDT)

TENN-L-0000068_lg verbatimLocality (edge of road near gorge); habitat (bark, edge of road)

FIXED? I put locality: edge of road near gorge Cheboygan County
FIXED? I put habitat: bark, edge of road near gorge
some overlap is going to happen. --Dpaul 17:29, 1 July 2013 (EDT)

TENN-L-0000072_lg verbatimCoordinates contains null in the csv file; (Lat. 40� N) is in text file.

FIXED verbatimCoordinates, set =Lat. 40° N --Dpaul 17:29, 1 July 2013 (EDT)
FIXED country = U.S.A. (literal from label) --Dpaul 17:29, 1 July 2013 (EDT)

TENN-L-0000076_lg stateProvince (Minn,) in the text file; but it is (Minnesota) in the csv file.

FIXED to Minn. in gold csv to match gold txt file --Dpaul 17:29, 1 July 2013 (EDT)

TENN-L-0000077_lg identifiedBy (Date) in the csv file

FIXED by removing identifiedBy (it's not provided) as well as date identified (not provided). --Dpaul 17:29, 1 July 2013 (EDT)

TENN-L-0000077_lg datasetName (Michigan FLORA OF) in the text file; but it is (FLORA OF Michigan) in the csv file.

NOT FIXED because literally, the word Michigan is typed above the words FLORA OF--Dpaul 17:29, 1 July 2013 (EDT)

TENN-L-0000083_lg no recordNumber in the csv file; DateIdentified (format)

FIXED, put 599 for recordNumber and yyyy-mm-dd fmt for date identified. --Dpaul 17:29, 1 July 2013 (EDT)

TENN-L-0000083_lg verbatimEventDate (August 1 1957) is mixed with dateIdentified (August 1 1957)

FIXED see above. event date and date identified are the same. --Dpaul 17:37, 1 July 2013 (EDT)

TENN-L-0000084_lg scientificName (null)

NOT FIXED because the scientific name is not null but is confusing because there's a hand-written specific epithet written just over the typed specific epithet.
What to do about scientificname? which currently is set to the hand-written name (which is likely an annotation).? --Dpaul 17:37, 1 July 2013 (EDT)

TENN-L-0000089_lg verbatimCoordinates (Lat.40 N.) in the text file; but no verbatimCoordinates in the csv file

FIXED, put Lat.40° N. in the verbatimCoordinates of the gold csv file. --Dpaul 17:37, 1 July 2013 (EDT)

TENN-L-0000090_lg stateProvince (AK) in the csv file; but it is (ALASKA) in the text file.

FIXED, put AK in stateProvince. --Dpaul 17:37, 1 July 2013 (EDT)

Lichen WIS CSV

WIS-L-0011728_lg stateProvince (AK) in the text file; but it is (ALASKA) in the csv file.

image has FLORA OF ALASKA so seems okay to me to put ALASKA. The image also shows U.S. Fish & Wildlife Service, Anchorage, AK...neither of these is in the Location: string that reads: Funny River road; Kenai NWR
DID NOT FIX, left ALASKA in the csv file. --Dpaul 15:43, 2 July 2013 (EDT)

WIS-L-0011730_lg stateProvince (AK) in the text file; but it is (ALASKA) in the csv file. habitat (Site: ) in the csv file.

same as above
DID NOT FIX, left ALASKA in the csv file. --Dpaul 15:43, 2 July 2013 (EDT)

WIS-L-0012026_lg no datasetName

FIXED, put FLORA OF ALASKA in datasetName field, committed to GitHub. --Dpaul 15:43, 2 July 2013 (EDT)

WIS-L-0012038_lg no verbatimCoordinates

FIXED, added verbatimCoordinates, committed to GitHub. --Dpaul 16:40, 2 July 2013 (EDT)

WIS-L-0012040_lg locality (Cen- tral Brooks) in the text file; but it is (Central Brooks) in the csv file

FIXED, now locality reads, "Collected in the North Slope Foothills of the Cen-tral Brooks Range, .5 km E of Toolik Lake" Committed to GitHub --Dpaul 15:43, 2 July 2013 (EDT)

WIS-L-0012041_lg no datasetName in the csv file; no scientificName in the csv file; verbatimEventDate (format) in the csv file; dateIdentified (format) in the csv file

William Ulate FIXED this record and pushed the changes to GitHub on 2 July 2013. --Dpaul 14:26, 3 July 2013 (EDT)

WIS-L-0012045_lg verbatimCoordinates concatenation

the label image has Latitude 60° 33.436'N Longitude 172° 55.950'W
the csv had 60° 33.436'N,172° 55.950'W
Deb removed the comma and put the field names back in to match for verbatim coordinates as Latitude 60° 33.436'N Longitude 172° 55.950'W --Dpaul 14:26, 3 July 2013 (EDT)

WIS-L-0012051_lg dateIdentified (format)

FIXED (was 2003-November, changed to 2003-11) --Dpaul 14:26, 3 July 2013 (EDT)

WIS-L-0012055_lg verbatimEventDate (format)

FIXED, changed to match what is on the label 19 July 2003 --Dpaul 14:26, 3 July 2013 (EDT)

WIS-L-0012055_lg verbatimEventDate (19 July 2003) in the text file; but it is (2003-July-19) in the csv file

FIXED, and fixed the dateIdentified format too. --Dpaul 14:26, 3 July 2013 (EDT)

WIS-L-0012056_lg dateIdentified (format)

FIXED, the dateIdentified format --Dpaul 14:26, 3 July 2013 (EDT)

WIS-L-0012057_lg no datesetName

FIXED --Dpaul 14:26, 3 July 2013 (EDT)

WIS-L-0012064_lg verbatimCoordinates concatenation

looks okay? They are exactly as they appear on label, albeit with the field names included, reading: Latitude 66°54,02.9" N Longitude 159° 59' 02.2" W --Dpaul 14:26, 3 July 2013 (EDT)
TO BRYAN (from deb): OR do we want only: 66°54,02.9" N 159° 59' 02.2" W
From Deb: this will be challenging, it's been done several ways, with and w/o the label terms, and when "without" the lat lon label terms a comma was used (added). I have been removing the commas. --Dpaul 14:26, 3 July 2013 (EDT)

WIS-L-0012073_lg identifiedBy (By P. Y. Wong) in the csv file

FIXED,removed the By--Dpaul 14:26, 3 July 2013 (EDT)

WIS-L-0012074_lg county (null)

NOT FIXED, there is no county on the label. Thunder Bay is a District (not a county).--Dpaul 14:26, 3 July 2013 (EDT)

WIS-L-0012074_lg county (null)

NOT FIXED, there is no county on the label. Thunder Bay is a District (not a county).--Dpaul 14:26, 3 July 2013 (EDT)

WIS-L-0012077_lg verbatimLocality contains verbatimCoordinates (Qianjin)

NOT FIXED, this is okay, they are embedded. --Dpaul 14:26, 3 July 2013 (EDT)

Gold OCR (TXT file) Errors

NY01075761_lg.txt has catalogNumber as 0107576, omitting the 1 at the end.

FIXED --Dpaul 17:20, 3 July 2013 (EDT)

WIS-L-0012026_lg.txt:: Several errors: Replaced the "N" in Latitude with a "K". Question mark instead of apostrophe in Longitude. Sandra Looman replace with Sandra Lcoman. Two dots after the date.

FIXED, note the"K" is the only error I saw in the TXT and CSV file.--Dpaul 17:20, 3 July 2013 (EDT)


TENN-L-0000029_lg.txt adds a "1" to the scientificName ("Actinogyra muhlenbergii 1 (Ach.) Schol.").

NY01075791_lg.txt converted "Müll" on the original label NY01075791_lg.jpg to "Mull" (converted umlaut "ü" to "u". We may want to do this, but if we do it should be standardized and consistent across all the labels. Same for NY01075791_lg.txt, and several others in the series).

FIXED en mass for Mull to Mül using GREP to find, csv in Notepad++ to fix. --Dpaul 14:26, 3 July 2013 (EDT)

Silver Parsed CSV File Issues


(Bryan: I do not get most of these. There should be OCR errors in silver. We do need to stay true to the OCR output.) 

"Silver Parsed CSV Files" There were some errors in the Silver CSV dataset. (Steven C.)


NY01075760_lg character encoding in verbatimScientificName typos in verbatimCoordinates

Character encoding fixed. verbatimCoordinates fixed.--Daryllafferty 16:18, 10 July 2013 (EDT)

Silver Parsed CSV NY Issues

NY01075761_lg misspelling in verbatimScientificName

FIXED Polycoccum to Polxcoccum to match OCR results (Not synced) --Daryllafferty 20:00, 3 July 2013 (EDT)

NY01075762_lg misspelling in habitat misspelling in verbatimLocality (Bryan: I think the problem is that habitate is concatinated with the substraight "Abies [7a[5amzfem—Betu[a papyrzfem forest over granite adjacent to waterfall, parasite on Peltigera scabrosa". the parasite part is from another part of the label. It shoudl be on a new row.)

NY01075764_lg misspelling in units for verbatimElevation

Fixed -- m changed to In as on silver .txt file.--Daryllafferty 00:55, 7 July 2013 (EDT)

NY01075765_lg character encoding in verbatimScientificName removed extra period in verbatimEventDate

Fixed. Added period so that "Feb. 1898" now reads "Feb. 1898.", to match silver .txt file.--Daryllafferty 00:25, 9 July 2013 (EDT)

NY01075768_lg separated verbatimLocality data into two columns

Fixed. Entire verbatimLocality moved within the quotes, while before the end quote was in the middle of the field.

NY01075769_lg misspelling in habitat

Added space after comma in habitat--Daryllafferty 01:03, 7 July 2013 (EDT)

NY01075770_lg character encoding in verbatimScientificName character encoding in habitat

Fixed. Entire .csv converted from ANSI to UTF-8 character set with corrected fields--Daryllafferty 22:22, 9 July 2013 (EDT)

NY01075773_lg misspelling in verbatimScientificName misspelling in verbatimLocality

I can't find the error. .csv file matches .txt file for these fields (though neither matches real label due to OCR errors)--Daryllafferty 00:16, 9 July 2013 (EDT)

NY01075774_lg character encoding in verbatimScientificName

No error found--Daryllafferty 22:32, 9 July 2013 (EDT)

NY01075775_lg misspelling in country

"USA" changed to "U.S.A" to match .txt file--Daryllafferty 00:18, 9 July 2013 (EDT)

NY01075776_lg character encoding in verbatimLocality

No error found--Daryllafferty 22:32, 9 July 2013 (EDT)

NY01075777_lg character encoding in country

Character encoding in silver .csv converted from ANSI to UTF-8, and characters corrected to match silver .txt --Daryllafferty 22:32, 9 July 2013 (EDT)

NY01075779_lg character encoding in verbatimCoordinates

Character encoding in silver .csv converted from ANSI to UTF-8 and verbatimCoordinates corrected to match silver .txt--Daryllafferty 15:31, 10 July 2013 (EDT)

NY01075780_lg misspelling in verbatimInstitution misspelling in verbatimLocality removed coordinates in verbatimLocality

Spelling fixed. Coordinates removed from verbatimLocality.--Daryllafferty 15:33, 10 July 2013 (EDT)

NY01075781_lg character encoding in verbatimElevation

No error found.--Daryllafferty 15:35, 10 July 2013 (EDT)

NY01075782_lg separated verbatimLocality data into two columns removed coordinates in verbatimLocality character encoding in habitat

Removed coordinates from verbatimLocality. Character Encoding already seems correct.--Daryllafferty 16:27, 10 July 2013 (EDT)

NY01075786_lg misspelling in verbatimScientificName

verbatimScientificName spelling changed to match (misspelled) silver .txt file --Daryllafferty 15:38, 10 July 2013 (EDT)

NY01075787_lg misspelling in verbatimLocality removed coordinates in verbatimLocality misspelling in verbatimCoordinates misspelling in habitat

Corrected verbatimLocality and verbatimCoordinate errors. Corrected Character Encoding.--Daryllafferty 16:34, 10 July 2013 (EDT)

NY01075788_lg misspelling in verbatimLocality removed coordinates in verbatimLocality character encoding in verbatimCoordinates

Changed character set from ANSI to UTF-8. Removed Lat/Long from verbatimLocality--Daryllafferty 18:19, 13 July 2013 (EDT)

NY01075789_lg misspelling in verbatimLocality removed coordinates in verbatimLocality character encoding in verbatimCoordinates

Removed Lat/Long from verbatimLocality. No errors found in character encoding--Daryllafferty 18:28, 13 July 2013 (EDT)

NY01075790_lg misspelling in habitat separated verbatimLocality data into three columns removed coordinates in verbatimLocality

Corrected spelling in habitat. Removed coordinates from verbatimLocality. Did not find three column problem.--Daryllafferty 18:28, 13 July 2013 (EDT)

NY01075791_lg character encoding in verbatimScientificName

Error not found. verbatimScientificName rewritten anyway.--Daryllafferty 18:41, 13 July 2013 (EDT)

NY01075792_lg misspelling in verbatimLocality

Error not found.--Daryllafferty 18:53, 13 July 2013 (EDT)

NY01075794_lg misspelling in verbatimLocality

Error not found. Possibly lack of space after hyphen in "Stark-ville"? --Daryllafferty 18:53, 13 July 2013 (EDT)

NY01075795_lg misspelling in verbatimLocality

Error not found. Possibly lack of space after hyphen in "Stark-ville"? --Daryllafferty 18:53, 13 July 2013 (EDT)

NY01075802_lg character encoding in verbatimScientificName

Error not found. --Daryllafferty 18:53, 13 July 2013 (EDT)

NY01075803_lg created new identifiedBy column created new verbatimScientificName column moved verbatimScientificName data from third row to new column

Carriage return removed from file. Extra fields (with no matching heading) truncated--Daryllafferty 18:53, 13 July 2013 (EDT)

NY01075805_lg created new verbatimScientificName column moved verbatimScientificName data from third row to new column

Carriage return removed from file. Extra fields truncated.--Daryllafferty 18:57, 13 July 2013 (EDT)

NY01075806_lg character encoding in verbatimScientificName

Error not found.--Daryllafferty 17:54, 14 July 2013 (EDT)

NY01075813_lg misspelling in verbatimLocality

Period added to verbatimLocality--Daryllafferty 17:54, 14 July 2013 (EDT)

NY01075814_lg misspelling in county misspelling in verbatimLocality removed coordinates in verbatimLocality misspelling in habitat

Corrected recordNumber, removed Lat/Long from verbatimLocality--Daryllafferty 17:54, 14 July 2013 (EDT)

NY01075817_lg moved verbatimScientificName data to scientificName entered verbatimScientificName

Copied verbatimScientificName to scientificName--Daryllafferty 18:16, 14 July 2013 (EDT)

NY01075818_lg misspelling in habitat

Coordinates removed from verbatimLocality. Habitat modified.--Daryllafferty 18:16, 14 July 2013 (EDT)

NY01075819_lg misspelling in recordedBy

recordedBy spelling corrected. Coordinates removed from verbatimLocality --Daryllafferty 18:16, 14 July 2013 (EDT)

NY01075821_lg misspelling in verbatimLocality removed coordinates in verbatimLocality added coordinates to verbatimCoordinates

Coordinates removed from verbatimLocality, added to verbatimCoordinates--Daryllafferty 18:16, 14 July 2013 (EDT)

NY01075822_lg removed coordinates in verbatimLocality

Coordinates removed from verbatimLocality--Daryllafferty 18:16, 14 July 2013 (EDT)

NY01075823_lg moved identifiedBy and dateIdentified data up one row created new verbatimScientificName column moved verbatimScientificName data from third row to new column

Extra fields truncated--Daryllafferty 18:16, 14 July 2013 (EDT)

NY01075827_lg misspelling in county misspelling in verbatimLocality

Corrected verbatimLocality, corrected county.--Daryllafferty 18:16, 14 July 2013 (EDT)

NY01075828_lg misspelling in verbatimLocality removed coordinates in verbatimLocality

Coordinates removed from verbatimLocality--Daryllafferty 18:16, 14 July 2013 (EDT)

NY01075829_lg misspelling in habitat

Coordinates removed from verbatimLocality. Habitat corrected.--Daryllafferty 18:16, 14 July 2013 (EDT)

NY01075831_lg misspelling in verbatimLocality removed coordinates in verbatimLocality

Removed coordinates from verbatimLocality--Daryllafferty 18:16, 14 July 2013 (EDT)

NY01075837_lg misspelling in county

County pasted from .txt file.--Daryllafferty 18:16, 14 July 2013 (EDT)

Silver Parsed CSV TENN Issues

TENN-L-0000001_lg character encoding in occurrenceRemarks misspelling in habitat character encoding in verbatimLocality

csv encoding changed to utf-8, fixed above (the occurrenceRemarks were truncated (not copied in their entirety). Used the gold to compare. --Dpaul 22:19, 9 September 2013 (EDT)

TENN-L-0000002_lg character encoding in verbatimScientificName misspelling in habitat

csv encoding changed from to utf-8 w/o BOM to utf-8, fixed above. --Dpaul 22:19, 9 September 2013 (EDT)

TENN-L-0000004_lg misspelling in habitat misspelling in verbatimInstitution

csv encoding changed to utf-8, fixed above --Dpaul 22:19, 9 September 2013 (EDT)

TENN-L-0000005_lg misspelling in datasetName misspelling in occurrenceRemarks character encoding in verbatimLocality

csv encoding changed from to utf-8 w/o BOM to utf-8,
no verbatim institution captured in ocr so removed from csv
fixed above --Dpaul 22:19, 9 September 2013 (EDT)

TENN-L-0000006_lg misspelling in verbatimElevation edited verbatimEventDate

csv encoding to utf-8, fixed above. --Dpaul 22:19, 9 September 2013 (EDT)

TENN-L-0000007_lg separated verbatimLocality into two columns misspellings in both verbatimLocality columns

fixed above, took comma out of verbatim locality. --Dpaul 22:35, 9 September 2013 (EDT)

TENN-L-0000009_lg character encoding in habitat character encoding in catalogNumber

fixed above --Dpaul 22:35, 9 September 2013 (EDT)

TENN-L-0000010_lg separated verbatimLocality into two columns

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000012_lg character encoding in datasetName character encoding in occurrenceRemarks

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000013_lg misspelling in occurrenceRemarks misspelling in verbatimLocality

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000014_lg misspelling in datasetName misspelling in fieldNotes character encoding in verbatimLocality separated recordedBy into two columns

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000022_lg character encoding in recordedBy

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000027_lg character encoding in verbatimScientificName

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000028_lg character encoding in verbatimScientificName

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000029_lg misspelling in recordedBy

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000032_lg character encoding in verbatimScientificName

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000033_lg separated dataSetName into two columns separated fieldNotes into two columns

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000041_lg character encoding in datasetName misspelling in verbatimLocality

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000044_lg character encoding in datasetName

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000045_lg separated verbatimLocality into two columns

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000046_lg character encoding in datasetName

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000047_lg character encoding in datasetName

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000048_lg misspelling in verbatimLocality

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000049_lg separated verbatimLocality into two columns

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000051_lg character encoding in verbatimLocality

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000052_lg character encoding in verbatimScientificName character encoding in datasetName character encoding in habitat character encoding in verbatimLocality character encoding in recordedBy

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000053_lg character encoding in recordNumber

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000054_lg character encoding in datasetName

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000056_lg edited recordedBy

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000057_lg character encoding in verbatimLocality misspelling in verbatimInstitution

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000058_lg separated dataSetName into two columns character encoding in verbatimInstitution

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000059_lg character encoding in stateProvince character encoding in verbatimScientificName character encoding in verbatimCoordinates misspelling in recordedBy

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000061_lg edited verbatimLocality misspelling in recordedBy

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000063_lg separated dataSetName into two columns character encoding in identificationRemarks

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000064_lg character encoding in verbatimScientificName

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000065_lg character encoding in verbatimScientificName

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000068_lg edited habitat character encoding in verbatimInstitution

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000072_lg separated verbatimLocality into two columns misspelling in country edited verbatimScientificName character encoding in verbatimInstitution

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000073_lg misspelling in verbatimLocality character encoding in verbatimCoordinates misspelling in recordedBy

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000074_lg character encoding in recordedBy character encoding in verbatimScientificName character encoding in verbatimLocality

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000075_lg character encoding in datasetName misspelling in verbatimScientificName separated verbatimLocality into two columns character encoding in both verbatimLocality columns character encoding in verbatimCoordinates

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000076_lg misspelling in datasetName character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in both verbatimLocality columns character encoding in recordedBy

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000077_lg character encoding in county character encoding in verbatimLocality character encoding in catalogNumber

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000079_lg character encoding in verbatimInstitution

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000080_lg character encoding in catalogNumber

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000083_lg character encoding in verbatimScientificName

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000084_lg character encoding in datasetName character encoding in verbatimScientificName character encoding in verbatimLocality

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000087_lg character encoding in recordNumber character encoding in habitat character encoding in verbatimLocality character encoding in verbatimInstitution

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000089_lg misspelling in country separated verbatimLocality into two columns misspelling in verbatimLocality misspelling in verbatimInstitution misspelling in datasetName

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000090_lg character encoding in verbatimInstitution

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000091_lg character encoding in datasetName character encoding in verbatimScientificName character encoding in catalogNumber

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000093_lg edited verbatimLocality character encoding in catalogNumber

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000095_lg character encoding in verbatimScientificName edited country character encoding in verbatimLocality

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000097_lg character encoding in verbatimScientificName

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000098_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimEventDate character encoding in verbatimCoordinates

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

TENN-L-0000099_lg separated dataSetName into two columns character encoding in stateProvince misspelling in verbatimScientificName character encoding in verbatimLocality character encoding in verbatimLatitude character encoding in catalogNumber

fixed above --Dpaul 17:36, 15 September 2013 (EDT)
committed to GitHub --Dpaul 18:06, 15 September 2013 (EDT)

Silver Parsed CSV WIS Issues

WIS-L-0011726_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates misspelling in verbatimElevation character encoding in recordedBy

no error seen in verbatimScientificName, copied with all krelb from silver ocr as Cetraria ’u.x9\a~i&{cc. (‘Cl --Dpaul 18:01, 19 July 2013 (EDT)
verbatimLatitude missing a space
verbatimElevation fixed (had 1,800 ft, but ocr had a dot as in 1.800 ft) --Dpaul 18:01, 19 July 2013 (EDT)
verbatimLongitude fixed (the ocr had a ? instead of minutes symbol, since silver, removed the minutes symbol and put the ? in) --Dpaul 18:01, 19 July 2013 (EDT)
verbatimCoordinates had missing space and same issue as above --Dpaul 18:01, 19 July 2013 (EDT)
recordedBy no error seen? --Dpaul 18:01, 19 July 2013 (EDT)
changed csv encoded to utf-8 to match ocr text file, commited to GitHub --Dpaul 18:01, 19 July 2013 (EDT)

WIS-L-0011727_lg character encoding in verbatimScientificName separated verbatimLocality into two columns misspelling in verbatimLocality character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

Looks correctly parsed to me. --Dpaul 18:01, 19 July 2013 (EDT)
I need to check this and the next 2 files to see if csv / txt encoding is same or diff. --Dpaul 18:01, 19 July 2013 (EDT)
txt encoding was utf-8, csv was "unknown 8-bit". changed encoding of csv to match txt and fixed the characters needed as a result. committed to GitHub. --Dpaul 19:10, 7 September 2013 (EDT)

WIS-L-0011728_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat

fixed habitat, other errors not seen by this editor (dp); to be certain, i copied and pasted over from the ocr text into the csv file again for certainty. --Dpaul 18:01, 19 July 2013 (EDT)

WIS-L-0011729_lg separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

comma removed from verbatimLocality (it's not present in ocr output file) --Dpaul 18:01, 19 July 2013 (EDT)
other errors not seen. copied and pasted over again from txt to csv just for certainty. --Dpaul 18:01, 19 July 2013 (EDT)
fixed encoding (csv was iso, changed to UTF-8 to match txt and then fixed characters as needed. committed to GitHub --Dpaul 19:54, 7 September 2013 (EDT)

WIS-L-0011730_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates misspelling in habitat

csv encoding was ANSI, txt was utf-8. changed csv to utf-8 and fixed encoding issues and other items noted above after changing the csv encoding. --Dpaul 18:01, 19 July 2013 (EDT)

WIS-L-0011731_lg character encoding in verbatimScientificName character encoding in identifiedBy separated verbatimLocality into two columns misspelling in associatedTaxa misspelling in verbatimElevation

csv encoding to utf8 then fixed above noted issues.
committed to GitHub --Dpaul 19:54, 7 September 2013 (EDT)

WIS-L-0011732_lg separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf8 then fixed above noted issues. Verbatim locality left as is (it does come from two different lines in the label though).
committed to GitHub --Dpaul 19:54, 7 September 2013 (EDT)

WIS-L-0011733_lg character encoding in verbatimLocality character encoding in habitat character encoding in verbatimCoordinates

csv encoding to utf8 then fixed above noted issues.
committed to GitHub --Dpaul 20:33, 7 September 2013 (EDT)

WIS-L-0011734_lg character encoding in verbatimScientificName character encoding in verbatimCoordinates character encoding in habitat character encoding in recordNumber separated verbatimLocality into two columns

csv encoding to utf8 then fixed above noted issues.
committed to GitHub --Dpaul 20:33, 7 September 2013 (EDT)

WIS-L-0011736_lg character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf8 then fixed above noted issues.
committed to GitHub --Dpaul 20:33, 7 September 2013 (EDT)

WIS-L-0012025_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf8 then fixed above noted issues.
committed to GitHub --Dpaul 20:33, 7 September 2013 (EDT)

WIS-L-0012026_lg character encoding in verbatimScientificName

no difference seen btwn text file and csv file. even encoding is same.
did note that header column names were missing from csv file. fixed & committed. --Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012027_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf-8, fixed above.--Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012028_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat misspelling in verbatimElevation

csv encoding to utf-8, fixed above.--Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012029_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat

csv encoding to utf-8, fixed above.--Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012030_lg character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat

csv encoding to utf-8, fixed above.--Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012031_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat

csv encoding to utf-8, fixed above. --Dpaul 18:52, 8 September 2013 (EDT)


WIS-L-0012032_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat

csv encoding to utf-8, fixed above. --Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012033_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates misspelling in verbatimElevation

csv encoding to utf-8, fixed above. --Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012034_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf-8, fixed above.--Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012035_lg character encoding in verbatimScientificName separated verbatimLocality into two columns misspelling in verbatimLocality character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf-8, fixed above--Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012036_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf-8, fixed above--Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012037_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf-8, fixed above--Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012039_lg character encoding in verbatimScientificName character encoding in verbatimLocality character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf-8, fixed above --Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012040_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat

csv encoding to utf-8, fixed above --Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012041_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat

csv encoding to utf-8, fixed above --Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012042_lg character encoding in datasetName character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat

csv encoding to utf-8, fixed above --Dpaul 19:34, 8 September 2013 (EDT)

WIS-L-0012043_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat separated verbatimLocality into two columns

csv encoding to utf-8, fixed above --Dpaul 18:52, 8 September 2013 (EDT)

WIS-L-0012044_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv encoding to utf-8, fixed above, quoted the verbatimScientificName --Dpaul 19:14, 8 September 2013 (EDT)

WIS-L-0012045_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv encoding to utf-8, fixed above, quoted the verbatimScientificName --Dpaul 19:14, 8 September 2013 (EDT)

WIS-L-0012046_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv encoding to utf-8, fixed above, quoted the verbatimScientificName

--Dpaul 19:14, 8 September 2013 (EDT)

WIS-L-0012047_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat

csv encoding to utf-8, fixed above --Dpaul 19:14, 8 September 2013 (EDT)

WIS-L-0012048_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat

csv encoding to utf-8, fixed above, quoted the verbatimScientificName --Dpaul 19:14, 8 September 2013 (EDT)

WIS-L-0012049_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv and txt encoding to utf-8, no split seen that's referred to above. --Dpaul 19:14, 8 September 2013 (EDT)

WIS-L-0012050_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf-8, fixed above --Dpaul 19:34, 8 September 2013 (EDT)

WIS-L-0012051_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv encoding to utf-8, fixed above --Dpaul 19:34, 8 September 2013 (EDT)

WIS-L-0012052_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

no separation seen (when open in Excel)
csv encoding to utf-8, fixed above --Dpaul 19:34, 8 September 2013 (EDT)

WIS-L-0012053_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

no separation seen (when open in Excel)
csv encoding to utf-8, fixed above --Dpaul 19:34, 8 September 2013 (EDT)

WIS-L-0012054_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

no separation seen (when open in Excel), quoted scientificName after changing encoding.
csv encoding to utf-8, fixed above --Dpaul 19:34, 8 September 2013 (EDT)

WIS-L-0012055_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

no separation seen (when open in Excel), quoted scientificName after changing encoding.
csv encoding to utf-8, fixed above --Dpaul 19:34, 8 September 2013 (EDT)

WIS-L-0012056_lg separated verbatimLocality into two columns character encoding in habitat

no separation seen (when open in Excel), quoted scientificName after changing encoding.
csv encoding to utf-8, fixed above --Dpaul 19:43, 8 September 2013 (EDT)

WIS-L-0012057_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimCoordinates

csv encoding to utf-8, fixed above --Dpaul 20:47, 9 September 2013 (EDT)

WIS-L-0012058_lg separated verbatimLocality into two columns character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf-8, fixed above --Dpaul 20:47, 9 September 2013 (EDT)

WIS-L-0012059_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv encoding to utf-8, fixed above --Dpaul 20:47, 9 September 2013 (EDT)

WIS-L-0012060_lg character encoding in verbatimScientificName character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat

csv encoding to utf-8, fixed above --Dpaul 20:47, 9 September 2013 (EDT)
no issue seen with habitat encoding. dp

WIS-L-0012061_lg character encoding in verbatimScientificName separated verbatimLocality into two columns removed coordinates in verbatimLocality character encoding in associatedTaxa

csv encoding to utf-8, fixed above --Dpaul 20:47, 9 September 2013 (EDT)

WIS-L-0012062_lg character encoding in verbatimScientificName character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates character encoding in habitat character encoding in verbatimInstitution

csv encoding to utf-8, fixed above --Dpaul 20:47, 9 September 2013 (EDT)

WIS-L-0012063_lg character encoding in verbatimScientificName character encoding in verbatimLocality removed coordinates in verbatimLocality character encoding in associatedTaxa

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012064_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012065_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in habitat

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012067_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLatitude character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012068_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012069_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012070_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012071_lg character encoding in verbatimScientificName separated verbatimLocality into two columns removed coordinates in verbatimLocality character encoding in associatedTaxa

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012073_lg character encoding in verbatimCoordinates character encoding in verbatimLatitude character encoding in verbatimLongitude

csv encoding to utf-8, fixed above

WIS-L-0012074_lg character encoding in verbatimCoordinates character encoding in habitat misspelling in verbatimLocality

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012075_lg character encoding in verbatimScientificName character encoding in verbatimCoordinates character encoding in verbatimLatitude character encoding in verbatimLongitude

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012076_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimCoordinates character encoding in verbatimLatitude character encoding in verbatimLongitude

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012077_lg character encoding in verbatimLocality character encoding in habitat

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012078_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012082_lg character encoding in verbatimScientificName character encoding in verbatimCoordinates character encoding in verbatimLatitude character encoding in verbatimEventDate character encoding in recordNumber

csv encoding to utf-8, no issue seen with verbatim event date or record number. --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012084_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012085_lg character encoding in verbatimScientificName separated verbatimLocality into two columns character encoding in verbatimLongitude character encoding in verbatimCoordinates

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)

WIS-L-0012086_lg character encoding in verbatimScientificName separated verbatimLocality into two columns

csv encoding to utf-8, fixed above --Dpaul 21:32, 9 September 2013 (EDT)
  • the words latitude and longitude as labels for fields were removed from the parsed fields so that the fields contain only the values and not the terms. this is consistent with other fields like habitat and locality. --Dpaul 21:34, 9 September 2013 (EDT)


End New Errors


Fixed Dataset Errata

Back to the Hackathon Wiki