To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 2285
2284  |  2286
Subject: 
Re: The Bricktionary project (Was: Idea: How starting ... Lego piece naming convention?)
Newsgroups: 
lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general
Followup-To: 
lugnet.admin.database
Date: 
Thu, 8 Jul 1999 14:16:47 GMT
Viewed: 
88 times
  
[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]

On Thu, 8 Jul 1999 12:36:17 GMT, "Sybrand Bonsma"
<bonsma@phys.chem.ethz.ch> wrote:

3. Compare the names of the different databases. A start here might be to find
the counterparts of LDraw parts in other programms/auctions. Because LDraw
uses part numbers, the list of pieces can be split up among various people
easily.

I've got some LDraw-to-AucZILLA cross-reference information.  Let me dig it
out...

4. Make an overview list of the used names. A proposed format is:
LDraw number; LDraw name; Auczilla name; TV inventory name; other name(s)
This owuld already be a good start for the Bricktionary.

Why not format the list like this (each part would have several entries):

ID     - This is a unique ID for the part.  It might be internally-created
         for the project, or it might be the LDraw Number/actual part
         number).
Number - The number or code for the part
Size   - The size information for the part
Name   - A name used to refer to the part
UsedBy - Where that name has been used.  This field would be set to LDraw,
         AucZILLA, Tim V, Margo K, maybe even Bricktionary (when a
         'preferred name' is decided upon).

This is a more flexible organization of the data, because it only requires
actual entries.  It also makes it possible to extract lists of parts names
for specific entities, by filtering on the UsedBy column.

More information about the Bricktionary project can be found at the following
page:
http://members.tripod.com/~Sybrand_Bonsma/bricktionary/bricktionary.html

Looks like a good start.  BTW, for the "List of parts in LDraw (with
pictures)", feel free to link to <http://home.att.net/~partsref>, if you
want.  It's a couple of parts-releases out of date, but I'll be fixing that
in the next few days.

Steve



Message has 2 Replies:
  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)

Message is in Reply To:
  The Bricktionary project (Was: Idea: How starting ... Lego piece naming convention?)
 
Hello everybody, In an earlier post in this thread I stated that I would start to make a list containing the various names for each LEGO part. As many parts have different names in different auctions, programms and inventories it is sometimes hard (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)

80 Messages in This Thread:































Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    
Active threads in Database

 
LUGNET Guide updates (Sat 23 Nov 2024)
19 hours ago
Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR