 | | 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)
|
| |
| | 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: 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)
|
| |
| | Re: Online LEGO Inventory Database
|
|
(...) One problem we have at the moment is that the various sources of parts lists (LDraw, Tim Vattima's set inventories, Auczilla, Technica, etc) all contain different subsets of the full parts list and use different descriptions. We need to (...) (25 years ago, 7-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
| |
| | Re: Online LEGO Inventory Database
|
|
(...) I (...) to (...) Perhaps (...) be (...) Sounds good to me! I'm going to begin by designing the database to hold the data, and deciding on the best method to catalog the parts, or the best existing database to use for the parts. Any suggestions (...) (25 years ago, 7-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
