[duncan_idaho]

Seems do-able.

I don't have the programming chops to pull that off.

Potential complications:

1) What are you using as your "consensus" core big board? NFL Mock Draft Database runs a good one that is an aggregated table based on all the pro mocks in their database. That one is slow to update, though, as rapid changes in someone's status due to a great combine or pro day or (or the reverese, or an injury, or an off-field event) still take some time to "catch up." For example, of the mock sites I use, this is the one where I'm least likely to be able to nab Ojabo. Because he's fallen from the top 10 to the teens over the past 10-14 days, but all those mocks with EARLY projections are still in the database.

I'd almost think you want to limit the mock database that's creating your consensus big board to the past 2-4 weeeks. And I don't know of one that exists publicly and works that way.

2. How do you weigh team needs vs. positional value?

3. How do you account for the "depth" of the draft? i.e. in a year like 2013 it would be easier to move around in the draft because that one was a big ol' pile or crap. But in a deep draft like this, it may be harder/teams may be more likely to stick exactly to pick value in trades.