Now that the VIN Database is up and running, and is stable and just about all of the data has been captured in it (we still need to finish creating and downloading LastVIN data sheets for all of the cars — we are only about 10-12% of the way done; and I still have to import non-US private database data for 1991-1993 into the Google Sheet), I have been noodling on how best to take this VIN Database resource to the next level.
I have become convinced that the best way to do this is to create a new, separate database that is dedicated specifically to the VIN Database, and contains all of its information. This database will then be able to be accessed directly through and from within the 500Eboard forum itself.
It will take a bit of coding to create a “VIN Search” page (similar to the search capability here) whereby users can input a specific VIN number, and all information and notes about that car in the VIN Database will then be presented on screen (including say, a link to the LastVIN PDF data sheet for the car). It is not technically difficult to create a “query” page once the database is created.
The current VIN Database Google Sheet would continue to be maintained, mainly as an input mechanism when new data comes up (for example, new cars come up for sale or auction). And then it is very easy to set up that the Google Sheets VIN Database is automatically sync’d once or twice a day, and newly added data is imported into the 500Eboard VIN Database residing on our server. From there it is presented on the VIN Search page here on the forum.
Separately, it would also be possible to display the sequential VIN display similarly to how it is displayed by the Google Sheet, in terms of rows of VIN listings with associated characteristics and notes, if someone wanted to do that.
Each VIN would not have a static page, but rather would be created and displayed dynamically (on the fly) based on the VIN query, using the database data as the source to display within a defined visual/web page framework.
From a technical perspective, it is not difficult to import a Google Sheet into a true database, using JSON/CSV output from Google Sheets. For the custom coding within XenForo, it would either take the form of a custom php application that uses the 500Eboard/XenForo header/footer/colors, or (probably the better way to go, but more work up front), a custom XenForo add-on app.
Globally speaking, very very few sites — even niche forums on models like the W113 Pagoda, M100 sedans/limos, and other models — have achieved the “down to the specific VIN” level of detail, notes, car and price history, and overall information that we have achieved over 20+ years with this forum and its predecessor, 500Ecstasy. This information is essentially a historical record of the cars, as well as a de facto registry of the cars.
The only other model-specific niche that even comes close to this level of information and detail — and I don’t think it actually has all of the nitty-gritty detail that we have on our cars — is the Gullwing Group (300SL Coupe and Roadster). But, of course, far fewer of these models were produced (a total of 3,258 total of both models) than 500E/E500 models.
It is very clear that the information that we have collectively compiled on the provenance of the 500E models, globally, is worth far more than the information contained in this forum. It’s hard to underestimate the value of this VIN Database information to collectors and enthusiasts, particularly in the future as more and more of these cars age out and they become scarce.
So, this integration is heavily on my mind, in terms of taking the VIN Database to the next level. Integrating it with this forum will elevate the site’s global authority and will cement — permanently — 500Eboard’s status as likely the leading model/niche-specific Mercedes forum on the internet. We’re already mostly there, but there’s a bit more way to go.
I am making no promises on when this all will happen. It’s likely, as with the changeover from vBulletin to XenForo, that it will happen over time, in fits and starts, and things will be developed over the course of a year or two. I think it was around five years from when I first purchased a license to XenForo to when I actually made the changeover in early 2019. Lots of fits and starts during that time, testing imports of data, setting up test forums to see how things worked behind the scenes, failed attempts at importing, refining processes, and so forth.
So when it does happen, in the future, it will probably happen quickly. That said, there will be a LOT of things that happened behind the scenes for many months in advance, to ensure a successful deployment.
But I think the end result will be worth it.
I have become convinced that the best way to do this is to create a new, separate database that is dedicated specifically to the VIN Database, and contains all of its information. This database will then be able to be accessed directly through and from within the 500Eboard forum itself.
It will take a bit of coding to create a “VIN Search” page (similar to the search capability here) whereby users can input a specific VIN number, and all information and notes about that car in the VIN Database will then be presented on screen (including say, a link to the LastVIN PDF data sheet for the car). It is not technically difficult to create a “query” page once the database is created.
The current VIN Database Google Sheet would continue to be maintained, mainly as an input mechanism when new data comes up (for example, new cars come up for sale or auction). And then it is very easy to set up that the Google Sheets VIN Database is automatically sync’d once or twice a day, and newly added data is imported into the 500Eboard VIN Database residing on our server. From there it is presented on the VIN Search page here on the forum.
Separately, it would also be possible to display the sequential VIN display similarly to how it is displayed by the Google Sheet, in terms of rows of VIN listings with associated characteristics and notes, if someone wanted to do that.
Each VIN would not have a static page, but rather would be created and displayed dynamically (on the fly) based on the VIN query, using the database data as the source to display within a defined visual/web page framework.
From a technical perspective, it is not difficult to import a Google Sheet into a true database, using JSON/CSV output from Google Sheets. For the custom coding within XenForo, it would either take the form of a custom php application that uses the 500Eboard/XenForo header/footer/colors, or (probably the better way to go, but more work up front), a custom XenForo add-on app.
Globally speaking, very very few sites — even niche forums on models like the W113 Pagoda, M100 sedans/limos, and other models — have achieved the “down to the specific VIN” level of detail, notes, car and price history, and overall information that we have achieved over 20+ years with this forum and its predecessor, 500Ecstasy. This information is essentially a historical record of the cars, as well as a de facto registry of the cars.
The only other model-specific niche that even comes close to this level of information and detail — and I don’t think it actually has all of the nitty-gritty detail that we have on our cars — is the Gullwing Group (300SL Coupe and Roadster). But, of course, far fewer of these models were produced (a total of 3,258 total of both models) than 500E/E500 models.
It is very clear that the information that we have collectively compiled on the provenance of the 500E models, globally, is worth far more than the information contained in this forum. It’s hard to underestimate the value of this VIN Database information to collectors and enthusiasts, particularly in the future as more and more of these cars age out and they become scarce.
So, this integration is heavily on my mind, in terms of taking the VIN Database to the next level. Integrating it with this forum will elevate the site’s global authority and will cement — permanently — 500Eboard’s status as likely the leading model/niche-specific Mercedes forum on the internet. We’re already mostly there, but there’s a bit more way to go.
I am making no promises on when this all will happen. It’s likely, as with the changeover from vBulletin to XenForo, that it will happen over time, in fits and starts, and things will be developed over the course of a year or two. I think it was around five years from when I first purchased a license to XenForo to when I actually made the changeover in early 2019. Lots of fits and starts during that time, testing imports of data, setting up test forums to see how things worked behind the scenes, failed attempts at importing, refining processes, and so forth.
So when it does happen, in the future, it will probably happen quickly. That said, there will be a LOT of things that happened behind the scenes for many months in advance, to ensure a successful deployment.
But I think the end result will be worth it.
