I realized that it would require exactly this kind of work in other sides of the app -- so I'm glad to hear that this is underway.
Having an admin way to do this, with more careful analysis, is probably the 90% of the solution.
I suppose that only if there were an instance that was taking thousands of reports would it make sense to do a simple UI for a larger team. Freebase.com does this with many of their "fuzzy data" problems using the
http://typewriter.freebaseapps.com/ platform. (And has been a huge inspiration for me, particularly their latest versions, with smart keyboard shortcuts and visual transitions.)
c
On May 16, 2010, at 11:13 AM, David Kobia wrote:
Interesting that you bring this up Chris... I'm currently working on an admin side addon for the guys at the UN that helps them identify related incidents using certain variables:
- Distance - with a slider that can be used to change radius size
- Time - with a slider that can be used to change time frame (e.g. hour, day, week, month etc)
- Category (optional)
Once the related incidents have been identified, a new single report can then be created, with a summary or new description.
I can definitely see how what you're suggesting would be useful not just for the admin side, but on the front end to crowdsource the task. The above approach is more analysis than anything, but would be complemented by the crowdsourced effort too.
On Sat, May 15, 2010 at 11:55 PM, Chris Blow
<cblow@...> wrote:
Hello,
I sketched a little idea for reconciling reports and would be interested in getting some feedback:
The idea is to expose a simple Yes/no queuing system for linking reports, to help some of the problems with duplicate reports we see in the Haiti instance.
There would need to be a table of "similar sounding" reports -- which possibly could be populated with SiLCC.
Does that make sense?
PS: not a feature request! Just an idea :)
c