 | | Re: The Bricktionary project (Was: Idea: How starting ... Lego piece naming convention?)
|
| [Followup-To set to lugnet.admin.database -- can we please corral this (important) discussion to one location? It's getting cross-posted to too many ng's] (...) I've got some LDraw-to-AucZILLA cross-reference information. Let me dig it out... (...) (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
| | | | | Re: The Bricktionary project (Was: Idea: How starting ... Lego piece naming convention?)
|
| (...) (I should have done that, discussion can be at one place) (...) That would be great (...) That is a good idea. The information I have till thus far still has included the name where it was used, so that might be possible. However, I still (...) (25 years ago, 8-Jul-99, to lugnet.admin.database)
| | | | | Bricktionary
|
| (...) How about a "known alias" category as well? Maybe include a warning category for the the piece has been mistaken for? The effort doesn't have to be strictly technical. I've submitted a couple sets to the database, and I've been at a loss over (...) (25 years ago, 31-Jul-99, to lugnet.admin.database)
| | | | | Re: Bricktionary
|
| (...) Shows me what happens with stale followup-to's... (...) Interesting ideas. Could be useful, especially for parts with no simple description. (...) Steve (25 years ago, 1-Aug-99, to lugnet.db.brictionary)
| |
