Shane R. Monroe
11-13-2006, 11:09 AM
Hey gang ...
Chris and I are talking about creating a 'guest editor' program for DualScreenRadio.com. The games database is growing so fast, we simply aren't able to keep up with it ourselves.
Here is where "guest editors" come into play. We already have a "report inaccuracies" system for the database, but it isn't getting used as much as I'd like. Giving ownership to certain games by the individual would give a little more pride and incentive to keep their entries up to date.
It would work like this. Let's talk about "Bob". Bob is already an avid user of the site to track his own collection, wishlist, watching titles, etc. He has 10-20 games, a couple of imports, and some of the more unusual titles for his kids (like Sprung and Ping Pals). We take a look at Bob's collection - and find that he has a lot of titles not already "owned" by other guest editors and would be a good fit with our needs. Most importantly, Bob has proven himself a valuable, stable member of the DSR society; even tempered, fair, and trustworthy.
We approach Bob and ask him if he'd like to be a guest editor for <insert game(s) here>. We tell him that he will have administrative access to our database for those game entries. This will allow him to control all the information for these games - even upload a new boxshot if a better one comes along. He will be responsible for keeping the entry up to date, as well as handle any error reports that visitors might submit. Since we can't pay anyone, Bob's recognition will be a little ownership placard on the game's DETAIL page stating that he is the information owner of these games.
Bob likes the idea, and picks 5 games from his collection he'd like to maintain. We ask Bob to limit it to 5 for now; once these entries are cleaned up, we can give him more. We add him as the editor for the games he selected and he goes to work, accepting more games if he likes the position or just maintaining the 5 we've assigned him.
I'd like to see guest editors end up "owning" like about 20 games or more over time. This will help us keep the number of guest editors down to a managable amount and clean our database up significantly.
In the beginning, we'd only be taking 1 or 2 trusted members of our community to help us pilot the process, then once we have the code ironed out, we'd bring on more.
What do you guys think about this concept?
Chris and I are talking about creating a 'guest editor' program for DualScreenRadio.com. The games database is growing so fast, we simply aren't able to keep up with it ourselves.
Here is where "guest editors" come into play. We already have a "report inaccuracies" system for the database, but it isn't getting used as much as I'd like. Giving ownership to certain games by the individual would give a little more pride and incentive to keep their entries up to date.
It would work like this. Let's talk about "Bob". Bob is already an avid user of the site to track his own collection, wishlist, watching titles, etc. He has 10-20 games, a couple of imports, and some of the more unusual titles for his kids (like Sprung and Ping Pals). We take a look at Bob's collection - and find that he has a lot of titles not already "owned" by other guest editors and would be a good fit with our needs. Most importantly, Bob has proven himself a valuable, stable member of the DSR society; even tempered, fair, and trustworthy.
We approach Bob and ask him if he'd like to be a guest editor for <insert game(s) here>. We tell him that he will have administrative access to our database for those game entries. This will allow him to control all the information for these games - even upload a new boxshot if a better one comes along. He will be responsible for keeping the entry up to date, as well as handle any error reports that visitors might submit. Since we can't pay anyone, Bob's recognition will be a little ownership placard on the game's DETAIL page stating that he is the information owner of these games.
Bob likes the idea, and picks 5 games from his collection he'd like to maintain. We ask Bob to limit it to 5 for now; once these entries are cleaned up, we can give him more. We add him as the editor for the games he selected and he goes to work, accepting more games if he likes the position or just maintaining the 5 we've assigned him.
I'd like to see guest editors end up "owning" like about 20 games or more over time. This will help us keep the number of guest editors down to a managable amount and clean our database up significantly.
In the beginning, we'd only be taking 1 or 2 trusted members of our community to help us pilot the process, then once we have the code ironed out, we'd bring on more.
What do you guys think about this concept?