Opened 14 years ago
Last modified 12 years ago
#64 new enhancement
Recognition dates are misleading
Reported by: | geofft | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Sometime |
Component: | Core | Version: | |
Keywords: | Cc: | ||
Size: | tiny |
Description
Several groups have recognition dates of 17 November 2003, which is when some information was imported into the previous incarnation of the database and not their actual recognition date. Quentin suggests that we simply replace those with "unknown".
Change History (5)
comment:1 Changed 14 years ago by geofft
comment:2 Changed 14 years ago by geofft
I think the right way to handle this is the commit in the trac-64 branch of git://geofft.scripts.mit.edu/asa-db.git, including running groups/remove_bad_recognition_dates.py, but I'd like code review.
comment:3 Changed 14 years ago by adehnert
NAK. Very much NAK.
My preference would be to do this at the display layer anyway, because I hate throwing away data. (Probably display "recognition date" as "entered into DB on" or something, I guess...) I can deal with this eventually.
comment:4 Changed 14 years ago by adehnert
- Component changed from Default to Core
- Size set to tiny
comment:5 Changed 12 years ago by adehnert
Hmmm... I feel like I'd be slightly happier with this as a migration.
165 groups were allegedly recognized on 17 November 2003; another 9 were on 20 November 2003, and those are also groups that I'm pretty sure all were in existence before then (they include MITSFS, SIPB, and Tech Squares). No other groups were recognized that month, and the December ones look legitimate, so I'm inclined to just say that any November 2003 recognition date should become "Unknown".
All other dates where we recognized more than 5 groups on a single day are from 2005 or later.