Knowledge database???
#1
Knowledge database???
I was just thinking... ( ok stop laughing ) what if we had a searchable database with all the car info, common problems for that year/trim line/engine, compatable accessories, etc...
Here is what I am thinking of. First off, instead of just having threads to search thru or one massive list having a selection menu so you can choose year/ trim level/ engine type/ etc... This way you get info relevant to your particular model fast and easy. It would be similar to when you do parts searches on on-line stores.
As far as content, here is what we currently have: http://home.attbi.com/~bill.wren/timeline.html. This is good info but there is room for improvement. What I mean by that is having other commonly asked info listed in here as well. Stuff such as OBD types, compatable scan tools, common part numbers for repairable items, suggested parts (fuel octane, t-stats, plug types, etc...) and other information that may be commonly asked again and again. This info would all be related back to the year/ trim line/ engine/ etc...
I have done web developing before but nothing like a DB. I would be more than willing to take up a project for this but I am wondering if everyone else thinks this would be worth the effort? Let me know what you think.
Here is what I am thinking of. First off, instead of just having threads to search thru or one massive list having a selection menu so you can choose year/ trim level/ engine type/ etc... This way you get info relevant to your particular model fast and easy. It would be similar to when you do parts searches on on-line stores.
As far as content, here is what we currently have: http://home.attbi.com/~bill.wren/timeline.html. This is good info but there is room for improvement. What I mean by that is having other commonly asked info listed in here as well. Stuff such as OBD types, compatable scan tools, common part numbers for repairable items, suggested parts (fuel octane, t-stats, plug types, etc...) and other information that may be commonly asked again and again. This info would all be related back to the year/ trim line/ engine/ etc...
I have done web developing before but nothing like a DB. I would be more than willing to take up a project for this but I am wondering if everyone else thinks this would be worth the effort? Let me know what you think.
#2
Senior Member
Expert Gearhead
I like the idea, however, finding someone to do the compile, programming, and implementation to said database is a daunting task. Its do-able, but that individual would need time and know-how. Both organization skills, computer (html?) skills.
Its a great idea, but logistically, its a big job I think. I have seen on a lot of websites a pull down menu that has options like "Select your car" and it gives you a list, then "select trim level desired" and it would have (in our case) LE, SE, SLE, SSE, SSEi. Then year "87-91", "92-94", "95-99"...you get the idea.
Is that what you mean Gord? can we hack a site to get that coding?
Anyone else wanna add something?
Its a great idea, but logistically, its a big job I think. I have seen on a lot of websites a pull down menu that has options like "Select your car" and it gives you a list, then "select trim level desired" and it would have (in our case) LE, SE, SLE, SSE, SSEi. Then year "87-91", "92-94", "95-99"...you get the idea.
Is that what you mean Gord? can we hack a site to get that coding?
Anyone else wanna add something?
#3
Gord and I are currently talking on Yahoo about it. That is basically what he was talking about. We are looking at the use of database, but would have to decide on a general format to be able to make the approrpiate fileds in the database, then if we wanted to add more info, the database would have to be altered along with the SQL query to get the info and then the code to post the info.
I was thinking that since the info won't really change much that just making static pages for each year would be better and easier to alter after.
That way just about anyone can edit the page after and would take less time, well anyone with access to it.
The simpler it is the less chance it will break.
I was thinking that since the info won't really change much that just making static pages for each year would be better and easier to alter after.
That way just about anyone can edit the page after and would take less time, well anyone with access to it.
The simpler it is the less chance it will break.
#6
Junior Member
Posts like a Ricer Type-R
Gord, this is good. Let some other guys do the leg work. Start with my timeline, and fill in the missing information in the form of a template. Give that blank or partial template (with what we already have filled in) to a willing member who owns that year. Let them do the research, then send the data back to you.
It would be nice to pull this off, so I can stop feeling guilty about not finishing that damn timeline. I like this idea.
It would be nice to pull this off, so I can stop feeling guilty about not finishing that damn timeline. I like this idea.
#7
Originally Posted by willwren
Gord, this is good. Let some other guys do the leg work. Start with my timeline, and fill in the missing information in the form of a template. Give that blank or partial template (with what we already have filled in) to a willing member who owns that year. Let them do the research, then send the data back to you.
It would be nice to pull this off, so I can stop feeling guilty about not finishing that damn timeline. I like this idea.
It would be nice to pull this off, so I can stop feeling guilty about not finishing that damn timeline. I like this idea.
#8
Senior Member
Expert Gearhead
That would be good....we could use a member from each model year to do some research and create the datbase.
But a format, layout and template would have to be created. Would we be able to find a "pro" who could proof-read and edit for say 87-91, then another to edit 92-94, another to do 95-1999...etc. Just to make sure the data is correct?
But a format, layout and template would have to be created. Would we be able to find a "pro" who could proof-read and edit for say 87-91, then another to edit 92-94, another to do 95-1999...etc. Just to make sure the data is correct?