Main > Main Forum
Project Database Brainstorm (updated 10/31/07)
vertygo:
I'd definitely love to help out, I've got some php / mysql experience.
I do agree it takes alot of user participation, but maybe if we build they will come ;D
If it's made easy enough, like a form to fill out with the ability to just upload pics, I think alot of people will be on board.
Agent Davis:
I would recommend updating the current section on BYOAC as has been suggested. Scour the projects pages and find email information and send out email invitations to people who have created their own page to have their project showcased on the grandaddy of em all!
Cakemeister:
Examples page in the wiki
The wiki just has a list of projects of each type, with a few pictures.
I guess the OP would like something like a gallery that you could just click on?
That is doable, but it would take quite a bit of work. The reason is because each homepage would have to be visited to get a link to the project picture. These pictures tend to be subject to bit-rot, so it may be better just to upload pictures for each project. Quite an undertaking.
I could code up something to make the wikitext. That part wouldn't be difficult.
Neverending Project:
To be honest, my original idea was a brand new database. This would require active users to add their own cabs. This would ensure the data is up-to-date, and consistent from project to project. After reading some of the suggestions, I realize that ideally we could incorporate old data too, but it remains to be seen how much work it will be gathering up old data, pics, etc.
In my head, I am picturing more of an online browsing/searching tool, rather than just a pic repository or image gallery. It would have the ability to rate cabs, post comments (a la The Wall in facebook), and most importantly, allow easy access to data.
I can picture a browsing feature - you would select which fields to browse by and the results list would update for you. There would also be a search feature, where you can search for specific specs or styles.
I am thinking this site would be focused on the cabinets (projects) themselves, and let this forum remain focused on all the sharing of information, how-to's, what cab is this?, which joystick is best, etc.
Eventually, it may evolve into allowing project blogging, but I don't want to take on too much all at once. If it were hosted on this domain, it would be great to tie into the user database already, so logged in users could post comments and rate, while guests could only view.
I am glad there is interest out there. I will try to put some fake screenshots together to get some more ideas for what we would like to see. I am thinking HADB for Home Arcade Database.
So this should go live in... what, a couple of days? ;)
shock_:
Interesting stuff.
Agree 110% if it happens it should be an evolution for the cab example wiki and not some other site. Then this thread could be migrated to the Forum Discussion board!
I don't think the migration of data is that big an issue. Hell, people like Circo generate thousands of intro videos for this hobby! A bit of farmed-out data entry never killed anyone :cheers:
Before anyone gets too crazy with coding, this would be quite easy to set up using Drupal with a few modules (think: plug-ins). I'm converting a 250,000+ page site to Drupal at the moment for work, and all the features mentioned in this thread would be pretty simple to bolt together.
For those who haven't used it, Drupal is a mature open source PHP/MySQL content framework that contains a core set of features for publishing and categorising content, plus a bruzillion contributed modules to plug in and do loads of other stuff (eg. fivestar module could handle the ratings from 1 to 5).
Some bigger sites using Drupal are Sony Musicbox, The New York Observer, The Onion.
--- Quote from: Neverending Project on October 25, 2007, 11:33:20 pm ---To be honest, my original idea was a brand new database. This would require active users to add their own cabs. This would ensure the data is up-to-date, and consistent from project to project. After reading some of the suggestions, I realize that ideally we could incorporate old data too, but it remains to be seen how much work it will be gathering up old data, pics, etc.
--- End quote ---
Yup, an old cab can definitely still be a good reference - even if the data available are a bit thin. But not every field need be mandatory :) Good information architecture is crucial though.
--- Quote from: Neverending Project on October 25, 2007, 11:33:20 pm ---In my head, I am picturing more of an online browsing/searching tool, rather than just a pic repository or image gallery. It would have the ability to rate cabs, post comments (a la The Wall in facebook), and most importantly, allow easy access to data.
I can picture a browsing feature - you would select which fields to browse by and the results list would update for you. There would also be a search feature, where you can search for specific specs or styles.
--- End quote ---
Drupal...
--- Quote from: Neverending Project on October 25, 2007, 11:33:20 pm ---I am thinking this site would be focused on the cabinets (projects) themselves, and let this forum remain focused on all the sharing of information, how-to's, what cab is this?, which joystick is best, etc.
--- End quote ---
Kinda like the wiki is now, then ;) But if each record carried data (or was simply tagged) like U360 sticks, overmount/undermounting, monitor rotation, button illumination, Athlon 2100+, TurboTwist2, Taito, upright, lexan CP, etc etc, each of those could link to canned forum searches.
--- Quote from: Neverending Project on October 25, 2007, 11:33:20 pm ---Eventually, it may evolve into allowing project blogging, but I don't want to take on too much all at once. If it were hosted on this domain, it would be great to tie into the user database already, so logged in users could post comments and rate, while guests could only view.
--- End quote ---
Drupal Drupal Drupal ;D Sorry. Seriously, blogging is out of the box. Drupal uses MD5 I think - we've recently successfully ported plural thousands of username/password hashes from our old site into Drupal (we were lucky; we had our existing hashes in MD5 ... no nasty phishy-smelling email to all our users to tell them they need to sign up again!) Common sign on (i.e. how BYOAC's SMF forum and Wiki software work right now) is simpler; single sign on becomes ... interesting, I think.
I read a thread about a year ago on the SMF development site where some dude was asking the SMF developers to assist with integrating with Drupal's uesr authentication and the SMF dude was really rude and dismissive about it. Sorry, that's just a single, and ancient, anecdote. No real advice to be had.
Sorry to sound like a Drupal fanboi, but this is a bunch of work to do properly, and I know the code exists to do it already and would hate a) time to be wasted or b) the implementation to be sub-optimal :) I'm not a developer, by the way, but I work with some :P I do the user design / information architecture stuff.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version