Sanity checks for the underlying data?

[christofs]

Not sure this is quite the right place for this idea, but it could be helpful to implement some sanity checks for the data presented by the web app. Just one example: the conferences have the properties "start_date" and "end_date" and a sanity check could be created by calculating the duration of the conference from this data. If the duration is less than 1 day and more than 10 days, or cannot be calculated, something might be wrong with these properties.

Doing this in this case yielded the following "interesting" items with less than 1 day duration:

• 290 | 1987-07-11 | 1979-07-13 | -2920
• 256 | 2003-08-31 | 2003-07-03 | -59
• 257 | 2004-09-05 | 2004-08-08 | -28
• 86 | 2006-04-24 | 2006-04-17 | -7
• 25 | 1997-06-13 | 1997-06-07 | -6

Larger 10:

• 404 | 1970-08-16 | 1970-09-06 | 21
• 71 | 1983-04-06 | 1983-06-08 | 63
• 341 | 2019-09-16 | 2020-09-16 | 366
• 43 | 2018-12-05 | 2019-12-09 | 369
• 36 | 2016-06-09 | 2019-06-10 | 1096
• 77 | 1983-06-06 | 1986-06-08 | 1098

[scottbot]

@christofs Sure this works. I'd love to do this in v2, though we don't have the development capacity now to make it happen. That said, I've gone in and manually corrected what you spotted, so thanks for bringing this up! (Strangely, conference 404 was accurate so far as I can tell; 21 day duration. Not sure the deal with that one.)