iDigBio Bot

Comment by Lee Belbin (@Tasilee) migrated from spreadsheet: Added post scoring for consistency

Comment by Paul Morris (@chicoreus) migrated from spreadsheet: One way of simplifying the core test suite would be to identify a small set of primary fields in cases where Darwin...

Comment by Arthur Chapman (@ArthurChapman) migrated from spreadsheet: I agree with Paul ghere

Comment by Paula Zermoglio (@pzermoglio) migrated from spreadsheet: Agree too. However, you may piss some people off, eg those that prefer using YMD instead of eventDate?

Comment by Lee Belbin (@Tasilee) migrated from spreadsheet: I thought this was against our policy?

Comment by John Wieczorek (@tucotuco) migrated from spreadsheet: This has particular applicability for GBIF in publishing an Occurrence data set.

Comment by Paul Morris (@chicoreus) migrated from spreadsheet: Important for testing data in pre-aggregation phases, and for assessing data collected by researchers from various sources.

Comment by John Wieczorek (@tucotuco) migrated from spreadsheet: I believe the name of this test should be changed. OCCURRENCE_IS_NULL is vague and ambiguous, and does not match names of similar...

Comment by Paula Zermoglio (@pzermoglio) migrated from spreadsheet: This is assuming that depths are actually correct but transposed, rather than just one of them, maximum or minimum being just plainly...

Comment by Paul Morris (@chicoreus) migrated from spreadsheet: Separate into a validation MIN_DEPTH_SHALLOWERTHAN_OR_EQ_MAX and an amendment MIN_MAX_DEPTHS_TRANSPOSED, to resolve the issue. There's a validation to find problematic depths, and an...