Open GoogleCodeExporter opened 9 years ago
[deleted comment]
Reading
http://www.plosone.org/article/info%3Adoi%2F10.1371%2Fjournal.pone.0055144#pone-
0055144-g015 suggests to me that we should expose the number of records that
FAIL
Taxon identification issue
Data Resource ID
Data Resource Name
Altitude value supplied in feet
Altitude value non-numeric
Altitude out of range
Basis of record badly formed
Coordinate precision not valid
Coordinates centre of country
Supplied coordinates centre of state
Coordinates are out of range for species
Coordinates dont match supplied country
Country inferred from coordinates
Day month transposed
decimal Lat Long Calculated From Easting Northing
decimal Lat Long Calculated From Verbatim
decimal Lat Long Calculation From Easting Northing Failed
decimal Lat Long Calculation From Verbatim Failed
decimal Lat Long Converted
Depth value non-numeric
Depth out of range
Suspected outlier
First of the century
First of the month
First of the year
geodetic Datum Assumed Wgs 84
Georeferenced after occurrence date
Habitat incorrect for species
Homonym issues with supplied name
Identification date before occurrence date
inferred Duplicate Record
Invalid collection date
Image URL invalid
Invalid scientific name
Coordinates are transposed
Min and max altitude reversed
Min and max depth reversed
Name not in national checklists
Name not recognised
Latitude is negated
Longitude is negated
occ Cultivated Escapee
precision Range Mismatch
resource Taxonomic Scope Mismatch
species Outside Expert Range
Coordinates dont match supplied state
Coordinate precision and accuracy transposed
Coordinate accuracy not valid
Supplied country not recognised
Kingdom not recognised
Collection code not recognised
Institution code not recognised
Type status not recognised
unrecognized Geodetic Datum
Supplied coordinates are zero
We need to be open about issues and we could hope for recruitment to address
issues.
It would be useful to link the categories above to the record sets that would
then enabled faceting to workable lists.
Original comment by leebel...@gmail.com
on 6 Apr 2014 at 4:07
[deleted comment]
Another one...
Please consider adding #Annotations with breakdown on Issue Type (geospatial,
habitat, taxonomic, outlier, temporal) with links to associated records. It
would be good to see the profile of the annotations service rise considerably
and this may help a little.
Original comment by leebel...@gmail.com
on 27 Apr 2014 at 10:10
Suggest need to capture downloads stats from ALA4R usage - which will be
released soon.
Also need to reduce or remove 'Other' category for downloads but this requires
another issue regarding mandatory registration.
Original comment by leebel...@gmail.com
on 17 Jun 2014 at 11:18
Original issue reported on code.google.com by
leebel...@gmail.com
on 16 Jan 2014 at 12:48