iDigBio Bot
iDigBio Bot
Comment by Lee Belbin (@Tasilee) migrated from spreadsheet: Sorry guys but this one IS MANDATORY - we are flagging if anyone has made an annotation about the record and we...
Comment by Paula Zermoglio (@pzermoglio) migrated from spreadsheet: Given that the country was not inferred from the coordinates to begin with.
Comment by Paul Morris (@chicoreus) migrated from spreadsheet: @PZ: again think of a sequence of pre-amendment, amendment, and post-amendment. The expectation in the case you describe in the pre-amememennt phase...
Comment by Paula Zermoglio (@pzermoglio) migrated from spreadsheet: Get it. Will we then define different profiles for pre- and post-? and sth like a route-plan? I think that's what's maybe...
Comment by Lee Belbin (@Tasilee) migrated from spreadsheet: Added post scoring for consistency
Comment by Paul Morris (@chicoreus) migrated from spreadsheet: Corresponding ammendment for IDENTIFIED_DATE_INVALID (VALIDATION_DATEIDENTIFIED_INVALID)
Comment by Paula Zermoglio (@pzermoglio) migrated from spreadsheet: Data generalizations can apply to non-geographic data, maybe the description of this test could be changed to match a more general approach,...
Comment by Arthur Chapman (@ArthurChapman) migrated from spreadsheet: Agreed @PJM - but it is important to include a test for this - Definitely a Core test
Comment by Arthur Chapman (@ArthurChapman) migrated from spreadsheet: Perhaps this needs to be split inter several - e.g. LOCALITY_GENERALIZED, DATE_GENERALIZED, ?NAME_GENERALIZED - does that ever happen?
Comment by Arthur Chapman (@ArthurChapman) migrated from spreadsheet: I believe that this should be altered to a NOTIFICATION rather than a VALIDATION