Send an answer to a topic: Lotus Type and Mk
Warning, this subject is old (3729 days without answer)
Sandie
Was this sorted in the end? Elise are still listed as Type M111...
antp
The new version - whenever it comes but not according to reports particularly imminent - may throw up a lot of these potential conflicts as it opens up [codes] across manufacturers.
Not really imminent, there is still work
And links between manufacturers, models, etc. would be made manually
i.e. first a database of makes & models, and then roles and pictures linked to these, rather than having just the text entered for each role and the list generated from that, I do not know if it is clear what I say
So there won't be conflicts in that way, we'll be able to link together models or car generations without having to specify a same code in each of them.
To come back a project codes, sometimes they can be used as reference too. For example the model codes for Renault are usually derived from project codes.
The target audience for the site are car enthusiasts. So if they usually refer to cars of a given make by project codes, we can do that too, even if the manufacturer does not
dsl
Yes it does. We don't yet have a conflict between Type codes and Chassis #s so can run 2 parallel systems in the same box. But it is probably going to start happening at some stage, and we may need to rethink tactics/protocols. The new version - whenever it comes but not according to reports particularly imminent - may throw up a lot of these potential conflicts as it opens up [codes] across manufacturers. I'd guess carry on current practice in the meantime???
tipo158
I asked about the M250 and am awaiting an answer. I suspect that it will be Type 118.
One thing to note about M-codes is that they are internal project code, not chassis/product codes in the sense of the IMCDb section.
Another thing - all of the chassis/product code entries of the form <number>/R<number> or <number>/<number> are actually <type number>/<chassis number>, that is, they identify individual cars. So they aren't chassis/product codes either. I know that I suggested 100T/1, but, as I think I noted earlier, I saw other chassis numbers for individual cars in that section and presumed that that kind of info went there.
One thing to note about M-codes is that they are internal project code, not chassis/product codes in the sense of the IMCDb section.
Another thing - all of the chassis/product code entries of the form <number>/R<number> or <number>/<number> are actually <type number>/<chassis number>, that is, they identify individual cars. So they aren't chassis/product codes either. I know that I suggested 100T/1, but, as I think I noted earlier, I saw other chassis numbers for individual cars in that section and presumed that that kind of info went there.
antp
I fixed the Mark names.
So about the M-codes, do we set the chassis code of the M250 as Type 118? Or Type M118? Or keep as M118 as currently?
I wait for the other M-codes then.
Maybe some older models or race models should have their name cleaned too.
So about the M-codes, do we set the chassis code of the M250 as Type 118? Or Type M118? Or keep as M118 as currently?
I wait for the other M-codes then.
Maybe some older models or race models should have their name cleaned too.
antp
I still have to fix these "Mark" model names, I forgot a little
I'll try to do that tomorrow.
I'll try to do that tomorrow.
tipo158
Exchanged e-mail with Lotus. The Elise and Exige are Type 111. The new Europa is Type 121. The Evora is Type 122.
Starting at some point, Lotus broke with tradition and started using the "project" number in its parts numbers. I am awaiting confirmation on whether the project number is the same thing as the old M number. The project numbers mentioned in my e-mail with Lotus are 117 (S2 Elise/Rover engine), 120 (S2 Elise/Toyota engine), 121 (Federal Elise) and 124 (Europa).
Starting at some point, Lotus broke with tradition and started using the "project" number in its parts numbers. I am awaiting confirmation on whether the project number is the same thing as the old M number. The project numbers mentioned in my e-mail with Lotus are 117 (S2 Elise/Rover engine), 120 (S2 Elise/Toyota engine), 121 (Federal Elise) and 124 (Europa).
antp
I'm not sure how to do this, but another route is to bring up the make list http://www.imcdb.org/vehicles_make-Lotus.html , => (show all), and then change the display options box from Make-and-Model to Date-Added-(new-ones-first)
That's indeed the way to find the new ones
(there isn't another, at least not provided by the site itself)
dsl
Maybe I can watch Lotus some time in the future.
Please do - more than welcome. The more the merrier. Particularly if you can check through the existing collection that we have individual entries correctly identified and coded against what they actually are. If you flag up errors on their pages, an admin will usually spot them fairly quickly and correct them.
Some of our expert watchers seem to note the number of their make and/or favourite model on the site every few days so that they know when new ones are added. I'm not sure how to do this, but another route is to bring up the make list http://www.imcdb.org/vehicles_make-Lotus.html , => (show all), and then change the display options box from Make-and-Model to Date-Added-(new-ones-first). New Lotus arrivals are probably not hourly occurrences ....
antp
"M100 Elan" will come up in a search for "Elan".
Actually, no, because the model search is by default done on the start of the name. But it is maybe not a big problem. It is difficult to say how people search the site, I do not know if they would rather do a search by typing a model name or browse it from link to link.
Then again, IMCDB does not list Caterham as a mfg
we have Caterham: http://www.imcdb.org/vehicles_make-Caterham.html
maybe not on the homepage though (as only the most common ones are there)
As Dsl said, it is sometimes better to keep a working system if the changes are not really important.
Anyway, in the next version of the site (when it will be done...) all that will be better handled, as names will be changeable more easily without much impact to the cars linked to them, and we'll be able to add navigation links between makes/models for helping the users (e.g. on the Elan listing, we could then add a link saying "if you search for the newer one, check the M100 Elan", or a link to Caterham & Kia on the main Lotus page, which is not possible currently).