At the risk of being reprimanded for flooding this thread (truly sorry, JC), I have a few more thoughts to share.
I've only accessed the beta site using Google Chrome (other browsers may provide a different user experience), but there are a couple of issues I've discovered while experimenting with the "Search" and "Filter" functions:
Issue #1: The Search Feature Lacks FlexibilityAll searches begin with the game title. It appears to be the only root node in the hierarchy. You select the game, then the platform, and finally the variation. You may then view the scoreboard for that unique combination, in batches of 100 records per page. You CANNOT do any of the following:
- Search by Player (all scores that YOU, or anybody else, has in the database)
- Search by Location (all scores achieved as Home Performances, at Funspot, etc.)
- Search by Date (all scores submitted in October of 2011)
Issue #2: The Search Filter is Limited in Scope and MemoryWhile browsing the scoreboard, you can filter the page results by entering all, or part of, a player name, location, or date. As you type, the results are continually updated. Great. The catch is that the filter only applies to the page you're currently viewing. A popular game with 250 entries will span 3 pages. If you're currently viewing page 1, and the item you're looking for is on page 3, the search filter will return zero results. You'll have to navigate to page 2 and try again. To make matters worse, the filter has no memory; when you advance to the next page, the text box is cleared, and you'll have to re-enter the filter criteria. That's not good.
As an example, let's say you're interested in seeing all DK scores that were submitted last year. The Donkey Kong/MAME/Points track contains 167 records, spread over 2 pages. On page 1, you enter "2012" in the criteria text box, and the number of displayed items shrinks from 100 to 10. At the bottom of the page, you click the "NEXT>" link, taking you to page 2. The filter is no longer active; there are 68 items on the page (the last item on any page is also the first item on the next page). You re-enter "2012" as your criteria, and the list of records is reduced to just 2. So now we know that there are 12 active DK scores in the database from Jan-Sep 2012. Granted, the extra effort isn't a huge deal, but it's unnecessary.
Ok, that's enough for today. I'm not trying to be overly critical; just pointing out a few things that could easily be improved. Who knows, there may be a number of enhancements already in the pipeline. This is beta, after all.
And there we are.