[VAXman(Admin)]

Originally Posted by VAXman

The one admin page I recently put together shows this clearly. Perhaps, on Thursday, I will capture one such page and show all in this thread. I'll blank out usernames but you'll get a better understanding since the page shows requests in terms of their request history (request time-stamp).

I took a snapshot of the page which I created to show the request queue. As you can see, this is ordered from most recent request to the oldest still remaining in the queue. The yellow rows are pending requests. In other words, SAM has gone through the request queue and selected some tracks for play. Based on SAM's knowledge of what has played, this selection process is NOT linear as this snapshot shows. The oldest request (the Beardfish) in the queue has not been selected for play and there are also "holes" within the list. There is no correlation between the "requested time-stamp" and the actual play time as well. This was also a good example because 2 requesters requested the same track. SAM will permit this because this track or artist may not have played recently. Both are yellow (ie. pending). SAM has gone through the database and collects like requests into one play.

Listing artists on the request page is probably the best day to display what is in the request queue. The ONLY other way might be to display the artists as ordered in the sample snapshot. However, because only the artist is displayed, I feel it's easier to see what has already been requested when that is is collated alphabetically. Your input and opinion welcome.