Leaderboard

Topic re-re-request, too late for tonight's show... I would like to see what the process of new data submission looks like from their point of view, with examples/screencaps/video... What info does or doesn't get sent? What does a CB editor see when looking at a wholly new entry? What steps do they do when processing a new entry before committing it into the master database? What does a CB editor see when looking at an updated submission? Do they only see the old/new field side-by-side, is the specific change highlighted? Updates are probably continually processed, but do they process submissions as single events, or do the look at things in batches? I know I tend to submit similar updates in a batch... do they look at batch submissions to speed up common corrections? I'd imagine for newly entered issues, they get multiple submissions with the same type of info, do they process some updates all for the same issue at once? Would also be interested to see the steps taken at the weekly level when preparing the weekly update.

The database has lots of missing and incomplete notes, as the vast majority of them should carry across all printings and variations but aren't. Best method for consistency, and for database size, would be to add a table separating Type/Number from Printing/Variation, having a single common Notes field per Type/Number, and a finely differentiated Notes field for every separate Printing/Variation.