|
|
 | | Re: What words describe the Lego elements?
|
| (...) From the discussion so far, I can tell that some of us may be confusing a classification system with being able to identify a Lego element. In the perfect database, the inquiry about a piece would not need to know *anything* about how the data (...) (25 years ago, 9-Feb-00, to lugnet.db.brictionary)
| | | | | 6445 Emergency Evac
|
| Set 6445 - Emergency Evac Manual Piece Count: 99 Piece Count on Box: 97 Distinct elements: 63 * indicates part does not count toward total Qty Color PartID Description 1 Black 3006 Brick 2 x 10 2 Yellow 4211 Car Base 4 x 5 1 Yellow 3788 Car Mudguard (...) (25 years ago, 7-Feb-00, to lugnet.db.inv)
| | | | | Re: Online LEGO Inventory Database
|
| (...) 'The database' should allow multiple descriptions per piece. And should have the major descriptions pre-loaded. The core element table should have an abstract key value, and a pointer to a graphic image for each part. A second table, call it (...) (25 years ago, 7-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
| | | | | Re: does anyone have...
|
| (...) I've got the box scanned for #7851: (URL) hesitant to open the box, since I'm waiting to see if anyone wants to buy/ trade for it. It sounds like the pieces are polybaged inside, though, so there's probably some kind of insert (maybe just a (...) (25 years ago, 7-Feb-00, to lugnet.trains, lugnet.general, lugnet.db.scans)
| | | | | Re: The Lepanadat Project (update 1)
|
| (...) Of course you can use the database I'm working on now for a set inventory. Creating a set inventory was also one of my goals when I started with the Lepanadat project, but it takes a lot of time, so it would probably take many, many years (...) (25 years ago, 7-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
|
